• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 232
  • Last Modified:

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?
0
25112
Asked:
25112
  • 5
  • 3
  • 3
5 Solutions
 
25112Author Commented:

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?
0
 
Éric MoreauSenior .Net ConsultantCommented:
>>Should he just have VS2010 to open all these projects

VS2010 cannot open a VS2003 without first converting it. VS2010 cannot target framework 1.1.

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.

Converting all the projects to VS2010 would be nice but at the same time it is extra work that you might not be able to do right now.
0
 
slightwv (䄆 Netminder) Commented:
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!
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
25112Author Commented:
>>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?
0
 
Éric MoreauSenior .Net ConsultantCommented:
>>you can work VS2008 solution  through vs2010 ide and save it as 2008 solution after editing from vs2010?

yes and still target framework 3.5. you won't be able to open the vs2010 .sln from vs2008 (you need to keep 2 distincts .sln)

>>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?

if you upgrade from VS2003 to vs2010, there are a lot of classes that have changed. so it implies modification in code
0
 
25112Author Commented:
>>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?
0
 
slightwv (䄆 Netminder) Commented:
It's not the VS version per say.  It is the .Net version used in the project.

Like I said, from .Net 1.1 to 4.0, the port was a nightmare and that was a relatively small app.
0
 
Éric MoreauSenior .Net ConsultantCommented:
>>OK.. but for 2005->2010 and 2008->2010, it should be seamless and no questions asked, right?

it a lot easier. I would say 99% no brainer.
0
 
25112Author Commented:
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..
0
 
slightwv (䄆 Netminder) Commented:
Take a look at:
http://msdn.microsoft.com/en-us/magazine/ff956194.aspx

Excerpt:
And most of the warnings you see will concern obsolete members. While you can still use obsolete members, you should know that they likely won’t be supported in the next-higher version of the .NET Framework. If you see obsolete members and you’re targeting the 2.0 framework, you will likely not be able to use that member when you decide to target a 3.x or the 4 framework.
0
 
25112Author Commented:
fit the bill.. thanks
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 5
  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now