vs.net 2003 to 2005

[aimlion11yahoo]

We are 80% done with a major application using .NET 1.1, vs.net 2003 and SQL Server 2000. I have just learned there is a plan to upgrade to vs.net 2005 and Sql Server 2005 before continuing with the project. Although upgrade will not benefit the project in any way, someone decided this was a good idea. Has anyone who has been through such an upgrade share their experiences with me. A quick check on Google revealed a number of issues, and even if we do it correctly, it looks like it is going to set the project back--AND WE HAVE A DEADLINE!

Would like to hear your experiences.

 

[techsmith]

We're planning something similar over the next 6 months and I don't want to re-write everything all at once.

My plan is to re-write where required and put everything else in v1.1 libraries. Then I will work out a schedule for upgrading the remaining code without putting the deadline at risk.

From the postings that I've read, as long as both versions of the framework are installed, the application will work. I suppose it's a bit like upgrading to .Net from VB6, where you might leave a lot of code as COM objects.

Hope everything goes smoothly for you.

 

[chrissie1]

Upgrading is not that difficult. It will do it by itself without a problem. It even makes a backup. The only real issue you have is that it doesn't trasnform the forms into a partial class design. And allthough the old ones still work they tend to be buggy. I don't know why they didn't do that because it could have been so easy.

Some classes changed namespace. But nothing really spectacular. The biggest change is in the new features.

Christiaan Baes
Belgium

"My new site" - Me