Link to home
Start Free TrialLog in
Avatar of 25112
25112

asked on

using latest versiion to handle older solutions in .NET

in production code, are you comfortable using only one version to handle all the older code? any disadvantages to it?
Avatar of 25112
25112

ASKER


here is a scenario:

a developer is called for maintainence in any of these projects, and is going to get a new PC..

VS 2003 - 18
VS 2005 - 11
VS 2008 - 9
VS 2010 – 3

option 1:
Should he just have VS2010 to open all these projects, and maintain, and use the tool
http://www.emmet-gray.com/Articles/ProjectConverter.htm
to convert it back to put in sourcesafe?

or
option 2:
should we have all developers use only vs2010 to convert all the projects to 2010, soit will be simple - only one version per developer
and no need to convert..

could you suggest pro/cons among the above 2 options? any other options for effectively handling multiple versions?
ASKER CERTIFIED SOLUTION
Avatar of Éric Moreau
Éric Moreau
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Not to mention the headaches of porting 1.1 code to 3.5/4.0.

I lived through one of those and there was a LOT of obsolete/deprecated code!
Avatar of 25112

ASKER

>>VS2010 cannot open a VS2003 without first converting it.

thanks for letting know that.

>>VS2010 can target Framework 2.0, 3.0, 3.5 and 4.0 so the same IDE can be used to maintain all projects written for VS2005 and up without having to convert them.
you can work VS2008 solution  through vs2010 ide and save it as 2008 solution after editing from vs2010?

>>it is extra work that you might not be able to do right now.
it won't be just point at the older framework and just working off it? i thought the upgrades will be seamless because no code will be updated?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of 25112

ASKER

>>if you upgrade from VS2003 to vs2010, there are a lot of classes that have changed.

OK.. but for 2005->2010 and 2008->2010, it should be seamless and no questions asked, right?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of 25112

ASKER

thanks..

could you provide me a msdn link stating the issues for .net 1.1 to 4.0 upgrade having issues.. it will  help to document it..

http://msdn.microsoft.com/en-us/library/ms185327.aspx
does not mention about it..

in http://msdn.microsoft.com/en-us/library/95x0y0wt.aspx, i see that "Visual Studio 2005 converts your Web application from using ASP.NET version 1.x to using ASP.NET version 2.0.".. so i thought v2 can convert v1, surely v4, but i am glad to be pointed in the right direction..
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of 25112

ASKER

fit the bill.. thanks