Migrating to VS 2005

11 Dec 2006 7:46 PM

wandii

Hi,
I have written couple of projects which include several crystal reports
in VS.net 2003
(VB.Net) and company would like to move to VS 2005. What
does it take to convert to Visual Studio.Net 2005? Can the 2003 project
just
be opened up in 2005? Will that convert it. The interface for 2005 very

different from 2003. I got the VS 2005 professional edition - can 2003
and 2005
be installed on the same machine and run side by side. Please advice
what steps
should I take to do the migration to VS 2005. Thanks for the
assistance.

Regards,
Wan

11 Dec 2006 8:11 PM

BK

First off, it's quite simple to move from 2003 to 2005. The source
typically doesn't change, just the project/solutions. We've migrated
quite a few over and not run into any difficulties.

To answer your second question, you can just as easily have both 2003
and 2005 running on the same machine, I have had both for over 6 months
now. I rarely use 2003 anymore and I'm just keeping it loaded in case
I've missed a project somewhere.

Hope this helps,

11 Dec 2006 9:04 PM

Matt Fielder

Side by side installations aren't a problem at all.

As a tip, I would suggest changing the file association for .sln files to
"Microsoft Visual Studio Version Selector". That way 2003 projects will
open in 2003 and 2005 projects will open in 2005 (default is to open
everything in 2005 which you may not want). To convert a project from 2003
to 2005, select to open the project from within 2005 --- the conversion
process will kick off automatically. -- Note that the conversion can't be
undone. (short of restoring a backup of the converted project)

Show quoteHide quote

"wandii" <wan***@yahoo.com> wrote in message
news:1165866395.427602.132510@16g2000cwy.googlegroups.com...
> Hi,
> I have written couple of projects which include several crystal reports
> in VS.net 2003
> (VB.Net) and company would like to move to VS 2005. What
> does it take to convert to Visual Studio.Net 2005? Can the 2003 project
> just
> be opened up in 2005? Will that convert it. The interface for 2005 very
>
> different from 2003. I got the VS 2005 professional edition - can 2003
> and 2005
> be installed on the same machine and run side by side. Please advice
> what steps
> should I take to do the migration to VS 2005. Thanks for the
> assistance.
>
> Regards,
> Wan
>

11 Dec 2006 11:03 PM

wandii

Thank you all for your feedback.

> As a tip, I would suggest changing the file association for .sln files to
> "Microsoft Visual Studio Version Selector". That way 2003 projects will
> open in 2003 and 2005 projects will open in 2005 (default is to open
> everything in 2005 which you may not want).

Matt - Could you please give me little more information on "changing
the file association for .sln files to "Microsoft Visual Studio Version
Selector". Do I need to do this before the
conversion. Is there a setting options in VS 2003/2005.

Also I came across another thread which states that when VS 2005
converts
VS.net2003 project, it will create a "Backup" folder to store the old
VS.net2003 solution. Is this correct? Please advice. Thanks in
advance.

Regards,
Wan

12 Dec 2006 5:21 AM

Matt Fielder

The file association I'm referring to is the windows file association. To
change file associations, open windows explorer, then "tools" menu, then
"folder options", then "file types" tab. This doesn't really have anything
to do with converting projects, just what version of VS will attempt to open
a solution when opening directly from the file system instead of the
development environment (by double clicking on a .sln file for example). As
for the second question about a 'backup' folder... honestly, I've never had
to roll back a solution, so I couldn't advise intelligently about a backup
folder that might be created. I usually make a habit of keeping a copy of
something that I know could get screwed up before messing with it.

Show quoteHide quote

"wandii" <wan***@yahoo.com> wrote in message
news:1165878218.302540.147160@l12g2000cwl.googlegroups.com...
> Thank you all for your feedback.
>
>> As a tip, I would suggest changing the file association for .sln files to
>> "Microsoft Visual Studio Version Selector". That way 2003 projects will
>> open in 2003 and 2005 projects will open in 2005 (default is to open
>> everything in 2005 which you may not want).
>
> Matt - Could you please give me little more information on "changing
> the file association for .sln files to "Microsoft Visual Studio Version
> Selector". Do I need to do this before the
> conversion. Is there a setting options in VS 2003/2005.
>
> Also I came across another thread which states that when VS 2005
> converts
> VS.net2003 project, it will create a "Backup" folder to store the old
> VS.net2003 solution. Is this correct? Please advice. Thanks in
> advance.
>
> Regards,
> Wan
>

11 Dec 2006 9:21 PM

Herfried K. Wagner [MVP]

"wandii" <wan***@yahoo.com> schrieb:
> I have written couple of projects which include several crystal reports
> in VS.net 2003
> (VB.Net) and company would like to move to VS 2005. What
> does it take to convert to Visual Studio.Net 2005? Can the 2003 project
> just
> be opened up in 2005? Will that convert it. The interface for 2005 very

There were heavy changes in ASP.NET. Windows Forms applications migrate
more cleanly but the new partial class form model won't be generated
automatically for the converted forms. In addition, some of the .NET 1.*
classes are now deprecated, such as 'System.Web.Mail'.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

12 Dec 2006 3:42 AM

Shane Story

What took the place of system.web.mail?

Show quoteHide quote

"Herfried K. Wagner [MVP]" <hirf-spam-me-here@gmx.at> wrote in message
news:%23N%23eEpWHHHA.924@TK2MSFTNGP02.phx.gbl...
> "wandii" <wan***@yahoo.com> schrieb:
>> I have written couple of projects which include several crystal reports
>> in VS.net 2003
>> (VB.Net) and company would like to move to VS 2005. What
>> does it take to convert to Visual Studio.Net 2005? Can the 2003 project
>> just
>> be opened up in 2005? Will that convert it. The interface for 2005 very
>
> There were heavy changes in ASP.NET. Windows Forms applications migrate
> more cleanly but the new partial class form model won't be generated
> automatically for the converted forms. In addition, some of the .NET 1.*
> classes are now deprecated, such as 'System.Web.Mail'.
>
> --
> M S Herfried K. Wagner
> M V P <URL:http://dotnet.mvps.org/>
> V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

12 Dec 2006 12:48 PM

BK

System.Net.Mail, it's a simple transition.