views:

58

answers:

2

Hi, I was previously working in VS 2008 (.net framework 3.5). I have now shifted to VS 2003. I know its not in demand as compared to other .net versions. Please let me know how to keep upgrade with VS 2008/10 (while working on 2003) so that the shift from lower to higher versions is smooth enough.

Suggest me the best possible solution as its would be helpful in my career in future.

Let me know if you need any other input from my side.

Thanks

A: 

Why have you downgraded so much? If it's because of the .NET version (you still need 1.1/2 instead of 3.0/3.5) then you can still use Visual Studio 2008 and just target your applications to a prior version of .NET.

.NET and Visual Studio are completely separate products (i.e. you don't need Visual Studio to create .NET apps.)

I think you need to explain your situation (and reasons for downgrading by two editions) for anyone to be able to provide more useful advice.

Andy Shellam
Pretty sure this is incorrect, VS 2008 won't multi-target to 1.1, you're locked into 2003 if you're stuck on .Net 1.1. Read ScottGu's reasoning for that here: http://weblogs.asp.net/scottgu/archive/2007/06/20/vs-2008-multi-targeting-support.aspx
Nick Craver
@Andy: i have not downgraded but company had a project made in VS2003 in which i need to work. btw i am aware that .net and vs are 2 separate products.
Romil Nagrani
@Nick: I know that VS 2008 won't support 1.1. How to get out of LOCKED situation from 2003 so that i can get better opportunities to work in 2008/10, as i am not going to be in 2003 for my entire life!?
Romil Nagrani
@Romil - When you open a project in 2008/2010, it has an upgrade wizard, you may have to fix things that worked because 1.1 didn't enforce them but 2.0+ did. However, if you're going to make that jump...don't do it a month before VS 2010 ships, wait and jump to 4.0. Just make sure whatever you deploy on also supports the framework you're moving to.
Nick Craver
@Nick: thanks for that!. but its not about how to handle 2003 projects in 08 or 10. its about how to cope with guys working in 08 or 10 so that i can match upto market level and the work of 2003 doesn't lack me behind in terms of knowledge of 08 or 10.. thanks
Romil Nagrani
The big question is why don't you upgrade the .NET 1.1 code to .NET 3.x or 4 ? The effort should be minimal.
Timores
@Timores: I dont wish to upgrade the code as i have said in my last comment. Coding could be done in any version of .net, what i wish to know that how to know everything about 2008/10 so that i could work in these 2 versions comfortably.(b'coz i am working in 2003 i am not to able to work in 2008 as other guys work on day-to-day basis)
Romil Nagrani
@Romil - **READ** lots and lots and lots. Here's a good compiled list of informative blogs: http://stackoverflow.com/questions/5119/what-are-the-best-rss-feeds-for-programmers-developers
Nick Craver
@Nick: Thanks for the link!. great URLs, must say...
Romil Nagrani
A: 

The following table stands:

VS.NET (also known as VS2002) - .NET 1.0
VS2003 - .NET 1.1
VS2005 - .NET 2.0
VS2008 - .NET 2.0, 3.0, 3.5 (SP1)
VS2010 - .NET 2.0, 3.0, 3.5 (SP1), 4.0

There was major shift from 1.x towards 2.0 where a lot of new concepts were introduced like the provider model, generics, ...
3.0 introduced us to WCF, WPF, WF, ... 3.5 introduced language enhancements in C# and Linq.

Most applications should be able to be upgraded to higher versions though but they'll keep on using older concepts so if you want to upgrade you'll have to do some refactoring. Like a simple example: if you used ArrayLists you can refactor these to use List.

For your career: I guess you also do some coding for fun in the evening so there you can make use of the freely available Express editions: http://www.microsoft.com/express/downloads/.

Grz, Kris.

XIII
thanks for your comments
Romil Nagrani