Home All Groups Group Topic Archive Search About

Opening projects from VS 2003 in VS 2005

Author
29 Jun 2006 9:07 PM
Nathan Sokalski
I recently upgraded from Visual Studio .NET 2003 to Visual Studio .NET 2005.
I have several projects that I created in Visual Studio .NET 2003, but when
I try to open them in Visual Studio .NET 2005 it tries to force me to
convert them. for some of these it would be fine, but some of them run on
servers that do not support .NET 2.0 yet, I simply want to edit the code
remotely but not convert anything. How can I prevent Visual Studio .NET 2005
from forcing me to convert the files? Thanks.
--
Nathan Sokalski
njsokal***@hotmail.com
http://www.nathansokalski.com/

Author
29 Jun 2006 10:04 PM
Dave Sexton
Hi Nathan,

I recommend you upgrade the servers promptly to support 2.0, but I
understand if you don't have the authority.  Also, you say you upgraded to
2005 but Visual Studio .NET supports side-by-side installation.  If you
still have 2003 just use 2003.

VS.NET 2005 is converting the project files to the new format supported by
VS.NET 2005.  I don't think you can stop this process, however I don't
believe that it's changing any of your code.

Try building as you normally would to ensure that you haven't used any
breaking changes from 1.1 to 2.0.  If it builds you can use an app.config
file to redirect the framework version that your program uses from the 2.0
assemblies to the 1.1 assemblies.  I have not tested this method.

ASP.NET:
http://msdn2.microsoft.com/en-us/library/bfyb45k1.aspx

WinForms:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconassemblyversionredirection.asp

HTH

Show quote
"Nathan Sokalski" <njsokal***@hotmail.com> wrote in message
news:OwxxCA8mGHA.708@TK2MSFTNGP02.phx.gbl...
>I recently upgraded from Visual Studio .NET 2003 to Visual Studio .NET
>2005. I have several projects that I created in Visual Studio .NET 2003,
>but when I try to open them in Visual Studio .NET 2005 it tries to force me
>to convert them. for some of these it would be fine, but some of them run
>on servers that do not support .NET 2.0 yet, I simply want to edit the code
>remotely but not convert anything. How can I prevent Visual Studio .NET
>2005 from forcing me to convert the files? Thanks.
> --
> Nathan Sokalski
> njsokal***@hotmail.com
> http://www.nathansokalski.com/
>
Author
29 Jun 2006 10:22 PM
Brendan Green
Just open the *file* that you want to edit, rather than the
solution/project.

Show quote
"Nathan Sokalski" <njsokal***@hotmail.com> wrote in message
news:OwxxCA8mGHA.708@TK2MSFTNGP02.phx.gbl...
>I recently upgraded from Visual Studio .NET 2003 to Visual Studio .NET
>2005. I have several projects that I created in Visual Studio .NET 2003,
>but when I try to open them in Visual Studio .NET 2005 it tries to force me
>to convert them. for some of these it would be fine, but some of them run
>on servers that do not support .NET 2.0 yet, I simply want to edit the code
>remotely but not convert anything. How can I prevent Visual Studio .NET
>2005 from forcing me to convert the files? Thanks.
> --
> Nathan Sokalski
> njsokal***@hotmail.com
> http://www.nathansokalski.com/
>
Author
3 Jul 2006 4:19 PM
Mini-Tools Timm
"Nathan Sokalski" wrote:

> I recently upgraded from Visual Studio .NET 2003 to Visual Studio .NET 2005.
> I have several projects that I created in Visual Studio .NET 2003, but when
> I try to open them in Visual Studio .NET 2005 it tries to force me to
> convert them. for some of these it would be fine, but some of them run on
> servers that do not support .NET 2.0 yet, I simply want to edit the code
> remotely but not convert anything. How can I prevent Visual Studio .NET 2005
> from forcing me to convert the files? Thanks.

The easiest way is to select the Visual Studio project in Explorer, right
click, select "Open With" from the popup menu, then select "Microsoft Visual
Studio 2003" from the submenu.  This will open the project in VS 2003.  Then
in the future, you can simply double-click on the project, as the Visual
Studio Project Selector will know that you want to edit this project in VS
2003.  (If you rename or move the file, you will have to repeat the process.)

--
Timm Martin
Mini-Tools
..NET Components and Windows Software
http://www.mini-tools.com

AddThis Social Bookmark Button