At Clemson, we began using .NET with version 2001. Then probably 2 years ago we made a push for converting those apps to version 2003 (i.e., simply opened our 2001 solution with version 2003 software and selected "convert"). That seemed to go very smoothly with no code changes needed.
The team I now manage mainly handles PeopleSoft but we do some .NET to complement PeopleSoft. I know that I have not been pushing for my group to upgrade our .NET 2003 apps to version 2005 nor am I aware of a push among my colleagues.
I guess my two questions are ....
1. Are you as a developer or manager seeing a push within your company to keep relatively current on .NET software versions? That is, say a commitment to convert to that new version within at least 1.5-2yrs from its general availability?
2. For those of you who have converted to .NET 2005, have you found it too to be a straight-forward software conversion from 2003 or are any code re-writes involved?
Thanks for any information you can provide.
I'm a bleeding edge type person so you'll almost always hear "upgrade upgrade upgrade" from me. Remember, you're not just upgrading to VS2005. You're also getting .NET 2.0 which itself is very impressive.
It's the upgrade to .NET 2.0 that may cause you to have to fix a couple of bugs. There are tons of articles on the internet detailing the differences between the two, but I will say that I've converted all of my projects over. I don't even have VS2003 installed any more. And chances are, if you don't go ahead and attempt to upgrade now, it'll be more difficult to upgrade when the next version of Visual Studio comes out.
Sure, you might have to stay late a day or two for everything to compile and work right once you convert, but I think it's well worth the effort. In the end, you'll be more productive
Thanks! I appreciate the info. I have some folks who are just now learning .NET 2003 so I guess I should have them go ahead and "start" with .NET 2005 instead.
thanks.
I agree. VS 2005 is soooo much better than 2003. Have them start out with the good stuff. There is no need to start with the old legacy VS 2003.
As Alex stated, projects update fairly readily.
Copyright (c) 2008 GSP Developers Walling Info Systems | Terms Of Use | Privacy Statement