I upgraded to .NET 2003, now I have 2 IDEs on my system

  • Thread starter Thread starter noid droid
  • Start date Start date
N

noid droid

Hi.

A couple of months ago, I ordered the Visual Studio .NET upgrade from
Microsoft and installed it. Today, I just realized that I have both the
2002 and 2003 IDEs on my system.

Did I do something wrong upgrading? I thought that the 2002 IDE would be
upgraded and essentially become the 2003 IDE. I didn't realize that I'd
have both IDEs on my system.

I veryified they are both different IDEs in Help -> About.

Also, I don't have Microsoft Application Center Test or Visual Studio
Analyzer in 2003 like I do in 2002.

Any comments? Should I get rid of 2002 IDE? Do I need to keep both? What
about Application Center Test or Analyzer?

Noid
 
That is by design. The Upgrade does not install over VS.NET 2002.
That way you can have both versions on your system at the same time.
Which, should not cause any problems. Unless, you use the same
folders to store your projects. I made a different default folder path
for VS.NET2003 so that it would not try to Upgrade my 2002 projects,
if I accidently opened one by mistake.
If you have plenty of room, I don't see any reason to get rid of 2002.
I find I use both.
james
Click to expand...

Hmmm, I did not know that. Since the 2003 checks for the existence of
2002, I assumed it would overwrite it.

So, if I need to use Applicaton Center Test or Analyzer, do I have to use
them from 2002? Or can I incorporate them into VS 2003?

Thanks for your reply.

noid
 
That is by design. The Upgrade does not install over VS.NET 2002. That way
you can have both versions on your system at the same time. Which, should
not cause any problems. Unless, you use the same folders to store your
projects. I made a different default folder path for VS.NET2003 so that it
would not try to Upgrade my 2002 projects, if I accidently opened one by
mistake.
If you have plenty of room, I don't see any reason to get rid of 2002. I
find I use both.
james
 
That is by design. The Upgrade does not install over VS.NET 2002.
That way you can have both versions on your system at the same time.
Which, should not cause any problems. Unless, you use the same
folders to store your projects. I made a different default folder path
for VS.NET2003 so that it would not try to Upgrade my 2002 projects,
if I accidently opened one by mistake.
If you have plenty of room, I don't see any reason to get rid of 2002.
I find I use both.
james
Click to expand...

By the way, is it *possible* to uninstall 2002 if I wanted to. If there
is no reason to uninstall 2002, I probably won't. I just want to know if
I'm going to screw stuff up if I unintall 2002.

However, what benefit would there be to leaving 2002 assuming I have no
2002 projects laying around that I can't open in 2003? Isn't that just
taking up added HD space and cluttering my system?

noid
 
2002 is for .NET Framework 1.0. 2003 is for .NET Framework 1.1. So if you
have legacy .NET code (v1.0) lying around and don't want to compile for
v1.1, use VS.NET 2002.

You can uninstall v2002, it should be in your Add/Remove Progams list. If
you uninstall v2002, reinstall/repair v2003 to reinstate your file
associations.

Jon
 
Jon Davis said:
2002 is for .NET Framework 1.0. 2003 is for .NET Framework 1.1. So if you
have legacy .NET code (v1.0) lying around and don't want to compile for
v1.1, use VS.NET 2002.
Click to expand...

LOL, legacy .NET code? That just sounds funny.
 
can't you select for which version you want to build in 2003?
i think you can compile for 1.1, 1.0 and 1.0 compact

working with 2002 now but at my previous work i had a 2003...
 
Back
Top