views:

615

answers:

8

Pretty much what the title says really.

We have some code that is .NET 1.1 based and no real desire to up-convert it. However, we are looking to add developers to the team and they will need copies of Visual Studio.

My understanding is that they will need VS 2003 - as this is the only IDE that supports .NET 1.1 but I am wondering if we are still able to purchase it!

+7  A: 

You can build 1.1 projects in Visual Studio 2005:

http://www.hanselman.com/blog/BuildingNET11ProjectsUsingVisualStudio2005.aspx

The MSBuild Everett Environment (MSBEE) has been announced, and soon this will be a (reasonably) supported scenario and we'll all be able to build both 1.1 and 2.0 versions of .NET code on Visual Studio 2005.

Also read this post about this issue:

http://blogs.msdn.com/clichten/archive/2005/11/08/490541.aspx

And also:

MSBuild Extras – Toolkit for .NET 1.1 “MSBee” is an addition to MSBuild that allows developers to build managed applications using Visual Studio 2005 projects that target .NET 1.1.

Espo
Wish I could accept two answers, because although Robs answer is perfect for my situation, I think this one is valid too.Have modded up appropriately.
Martin
A: 

Supported: Yes
Available: Not through normal channels. You might still find a boxed copy on Amazon or somewhere.

Joel Coehoorn
A: 

.NET 1.1 code can be imported in VS 2005, as .NET 2.0 is backward compatible with .NET 1.1.

You'll probably have to convert the project, but it should still run in VS 2005.

Philippe
A: 

I believe that vs2003 looses support in october

George Mauer
+5  A: 

Visual Studio 2003 is still available to download for MSDN subscribers.

The EULA for Visual Studio includes a 'downgrade' clause, which appears, IMNAL, to allow you to buy Visual Studio 2008 and then install 2003 under the same license.

DOWNGRADE. You may install and use this version and an earlier version of the software at the same time. This agreement applies to your use of the earlier version. If the earlier version includes different components, any terms for those components in the agreement that comes with the earlier version apply to your use of them. Microsoft is not obligated to supply earlier versions to you.

Rob Walker
+1  A: 

Mainstream support for VS2003 ends in October of this year:

http://support.microsoft.com/lifecycle/search/?sort=PN&alpha=Visual+Studio

Extended support (whatever that means) is still available for quite some time.

Jon Sagara
Mainstream support for the framework (1.1) ends at the same time
Jim Harte
Differences between mainstream vs extended support are explained here: http://support.microsoft.com/gp/lifepolicy
Jim Harte
A: 

In addition to Espo's link, look into MSBee, an enhancements kit for MSBuild to better support .NET Framework 1.1.

It seems you can even use .NET 1.1 with Visual Studio 2008, though, so you should have no problem.

That said, I'd be interested in hearing what made you choose against upgrading.

Sören Kuklau
The decision not to upgrade is because of lack of (programmer) resources. It works, and only needs minimal support so we don't want to touch it at this point.
Martin
A: 

want to buy Visual Studio .NET 2003. Can you please give me some idea?

Ujjaval