Comment We've been preparing for the 'migration' too. (Score 1) 164
I work for a company in a similar situation.. with a project that has about 150k lines of c# code.
If you have many (or any) ASP.NET applications, I suggest using the (NEW, in beta) ms-supported "Web Application" plug-in. This works the same way as VS.NET 2003, and will make NO changes to your existing code base - making the migration as simple as just resolving some naming conflicts with the new classes introduced in 2.0. This plug-in is here
For us, we actually switched to using a complete code-based web application (no aspx or ascx files at all), which has turned out to be the EASIEST transition - we can compile our code in both 2003 and 2005 with no problems (until we start taking advantage of the 2.0 features, of course).
The only real problem would be when switching to the new 'Web Site' ASP.NET model, which is just ridiculous as doing the conversion just messes up all of your existing code and it's pretty much guaranteed not to work without manually fixing it up.
Hope this helps!
If you have many (or any) ASP.NET applications, I suggest using the (NEW, in beta) ms-supported "Web Application" plug-in. This works the same way as VS.NET 2003, and will make NO changes to your existing code base - making the migration as simple as just resolving some naming conflicts with the new classes introduced in 2.0. This plug-in is here
For us, we actually switched to using a complete code-based web application (no aspx or ascx files at all), which has turned out to be the EASIEST transition - we can compile our code in both 2003 and 2005 with no problems (until we start taking advantage of the 2.0 features, of course).
The only real problem would be when switching to the new 'Web Site' ASP.NET model, which is just ridiculous as doing the conversion just messes up all of your existing code and it's pretty much guaranteed not to work without manually fixing it up.
Hope this helps!
