By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,166 Members | 1,575 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,166 IT Pros & Developers. It's quick & easy.

Moving VS.Net 2002 project to VS.Net 2003.

P: n/a
Hi,
I'm in the middle of a project cycle using VS.Net 2002. I'd like to
purchase VS.Net 2003 and make the jump to it but first I want to know how
much of a hassle it is loading my VS.Net 2002 project in 2003. The project
isn't under source control so that should make it easier. But if I need to
make a lot of modifications to the code so it'll run on 2003 I might just
wait a few months till the next project. Thanks for sharing any experiences
you may have opening your older projects in VS.Net 2003! Ken.
Nov 20 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
I didn't have any trouble with any of my class library projects, didn't need
to write any code to make the project 2003 compatible. As far as I can tell
the only differences between VS 2002 and VS 2003 are in the project files. I
did have trouble converting one of my web projects, haven't figured out why
yet but typically web projects are much more fragile because of the
relationship between IIS and the virtual directory the project is mapped to.

HTH

Dan

"Ken Dopierala Jr." <kd*********@wi.rr.com> wrote in message
news:e6**************@TK2MSFTNGP09.phx.gbl...
Hi,
I'm in the middle of a project cycle using VS.Net 2002. I'd like to
purchase VS.Net 2003 and make the jump to it but first I want to know how
much of a hassle it is loading my VS.Net 2002 project in 2003. The project isn't under source control so that should make it easier. But if I need to make a lot of modifications to the code so it'll run on 2003 I might just
wait a few months till the next project. Thanks for sharing any experiences you may have opening your older projects in VS.Net 2003! Ken.

Nov 20 '05 #2

P: n/a
Hello Ken!
Once you install vs.net 2003 you can still use vs.net
2002. When you open a old project with vs.net 2003 it
will upgrade it to 2003 , so it it advisable to keep a
backup copy. The only issue i had was after upgrading a
project that uses CrystalReportViewer i had to modify the
reference path of the project to the new version.

Kind Regards
Jorge
-----Original Message-----
Hi,
I'm in the middle of a project cycle using VS.Net 2002. I'd like topurchase VS.Net 2003 and make the jump to it but first I want to know howmuch of a hassle it is loading my VS.Net 2002 project in 2003. The projectisn't under source control so that should make it easier. But if I need tomake a lot of modifications to the code so it'll run on 2003 I might justwait a few months till the next project. Thanks for sharing any experiencesyou may have opening your older projects in VS.Net 2003! Ken.

.

Nov 20 '05 #3

P: n/a
Okay, that is what I was hoping! Thanks! Ken.

"alien2_51" <da********@n.o.s.p.a.m.monacocoach.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
I didn't have any trouble with any of my class library projects, didn't need to write any code to make the project 2003 compatible. As far as I can tell the only differences between VS 2002 and VS 2003 are in the project files. I did have trouble converting one of my web projects, haven't figured out why yet but typically web projects are much more fragile because of the
relationship between IIS and the virtual directory the project is mapped to.
HTH

Dan

"Ken Dopierala Jr." <kd*********@wi.rr.com> wrote in message
news:e6**************@TK2MSFTNGP09.phx.gbl...
Hi,
I'm in the middle of a project cycle using VS.Net 2002. I'd like to
purchase VS.Net 2003 and make the jump to it but first I want to know how much of a hassle it is loading my VS.Net 2002 project in 2003. The

project
isn't under source control so that should make it easier. But if I need

to
make a lot of modifications to the code so it'll run on 2003 I might just wait a few months till the next project. Thanks for sharing any

experiences
you may have opening your older projects in VS.Net 2003! Ken.


Nov 20 '05 #4

P: n/a
Thanks for the answer. I was hoping it was going to be relatively
straight-forward. Ken.

"Jorge Cavalheiro" <jm**@dinefer.pt> wrote in message
news:02****************************@phx.gbl...
Hello Ken!
Once you install vs.net 2003 you can still use vs.net
2002. When you open a old project with vs.net 2003 it
will upgrade it to 2003 , so it it advisable to keep a
backup copy. The only issue i had was after upgrading a
project that uses CrystalReportViewer i had to modify the
reference path of the project to the new version.

Kind Regards
Jorge
-----Original Message-----
Hi,
I'm in the middle of a project cycle using VS.Net

2002. I'd like to
purchase VS.Net 2003 and make the jump to it but first I

want to know how
much of a hassle it is loading my VS.Net 2002 project in

2003. The project
isn't under source control so that should make it

easier. But if I need to
make a lot of modifications to the code so it'll run on

2003 I might just
wait a few months till the next project. Thanks for

sharing any experiences
you may have opening your older projects in VS.Net

2003! Ken.


.

Nov 20 '05 #5

P: n/a
Hello,

"Ken Dopierala Jr." <kd*********@wi.rr.com> schrieb:
I'm in the middle of a project cycle using VS.Net 2002.
I'd like to purchase VS.Net 2003 and make the jump to
it but first I want to know how much of a hassle it is
loading my VS.Net 2002 project in 2003. The project
isn't under source control so that should make it easier.
But if I need to make a lot of modifications to the code so
it'll run on 2003 I might just wait a few months till the
next project.


The project will be updated to VS.NET 2003 automatically, but it cannot be
opened in version 2002 any more. AFAIK VS.NET 2002 and 2003 an be installed
on the same machine.

--
Herfried K. Wagner
MVP VB Classic, VB.NET
http://www.mvps.org/dotnet

Nov 20 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.