Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In the very near future I’ll be migrating some web applications from VS2003 projects to VS2005 projects.
What should I watch out for?
Anyone done this in the past and have it go bad?
How much time should I expect it will take to migrate a project?
I know this is more than one question, but please provide your experiences with anything relating to migrating projects from VS2003 to VS2005.
Thank-you
EDIT
The types of projects I will be migrating are Web Applications written in Visual Basic.
I really would go straight to VS2008. You can ‘throttle back’ your project so that it ‘only’ uses .NET 2.0, if that’s a requirement.
As far as what to watch out for – ASP.NET 1.1 and ASP.NET 2.0 are very different creatures, I’ve discovered. ASP.NET 1.1 let you put objects on a web page much the way you would drop buttons, labels and text boxes on a desktop forms application. This is no longer true in 2.0. I had a LOT of self-education coming to me when I started working on my current project in that I really had to learn how to lay out presentation-layer stuff with ASP tags (divs, style sheets, etc). The code-behind was still the same – handled better in fact. This all depends on what kind of web projects you’re migrating and how they were written in the first place.