473,326 Members | 2,114 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,326 software developers and data experts.

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

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

Nov 20 '05 #1
7 900
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

<noid> wrote in message
news:86******************************@news.teranew s.com...
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

Nov 20 '05 #2
"james" <jjames700ReMoVeMe at earthlink dot net> wrote in
news:#x**************@TK2MSFTNGP10.phx.gbl:
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

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

<noid> wrote in message
news:86******************************@news.teranew s.com...
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



Nov 20 '05 #3
"james" <jjames700ReMoVeMe at earthlink dot net> wrote in
news:#x**************@TK2MSFTNGP10.phx.gbl:
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
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

<noid> wrote in message
news:86******************************@news.teranew s.com...
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



Nov 20 '05 #4
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
<noid> wrote in message
news:d4******************************@news.teranew s.com...
"james" <jjames700ReMoVeMe at earthlink dot net> wrote in
news:#x**************@TK2MSFTNGP10.phx.gbl:
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


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

<noid> wrote in message
news:86******************************@news.teranew s.com...
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


Nov 20 '05 #5

"Jon Davis" <jo*@REMOVE.ME.PLEASE.jondavis.net> wrote in message
news:ec**************@TK2MSFTNGP10.phx.gbl...
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.


LOL, legacy .NET code? That just sounds funny.
Nov 20 '05 #6
:^)

"Da~One" <da***@whothat.com> wrote in message
news:uS**************@TK2MSFTNGP11.phx.gbl...

"Jon Davis" <jo*@REMOVE.ME.PLEASE.jondavis.net> wrote in message
news:ec**************@TK2MSFTNGP10.phx.gbl...
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.


LOL, legacy .NET code? That just sounds funny.

Nov 20 '05 #7
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...
"Jon Davis" <jo*@REMOVE.ME.PLEASE.jondavis.net> wrote in message
news:ec**************@TK2MSFTNGP10.phx.gbl...
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
<noid> wrote in message
news:d4******************************@news.teranew s.com...
"james" <jjames700ReMoVeMe at earthlink dot net> wrote in
news:#x**************@TK2MSFTNGP10.phx.gbl:
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


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

<noid> wrote in message
news:86******************************@news.teranew s.com...
> 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
>


Nov 20 '05 #8

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

0
by: Alec Solter | last post by:
Using .NET IDE 2003 I created a simple form that includes a button with image. When trying to run this project on old .NET IDE 2002 it is throws the following exception: ...
8
by: noid droid | last post by:
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...
2
by: James R. Atherton | last post by:
I borrowed some code (Listed below) in VB.NET 2002, and it works great. I upgraded to 2003 and although this snippet still works, the (.AddressList(0).Address) portion of it has a squiggly line...
0
by: Troy Donavan | last post by:
A VB Web application that worked in VS2002 was upgraded to VS2005 and on build generates the following error message on build: Request for the permission of type...
1
by: Dave Harry | last post by:
I've had trouble with VB 2003 not doing things quite right, help won't compile, etc, things are being a general pain the the bum. I've downloaded the VB Express 2005 and trying my code there...
0
by: Rod | last post by:
I've got Crystal Reports XI Release 2, for development with Visual Studio ..NET 2005. I've taken a VS .NET 2003 WinForms application that I wrote in C#, and upgraded it to VS .NET 2005. It has...
0
by: DolphinDB | last post by:
Tired of spending countless mintues downsampling your data? Look no further! In this article, you’ll learn how to efficiently downsample 6.48 billion high-frequency records to 61 million...
0
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
1
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
0
by: Vimpel783 | last post by:
Hello! Guys, I found this code on the Internet, but I need to modify it a little. It works well, the problem is this: Data is sent from only one cell, in this case B5, but it is necessary that data...
0
by: jfyes | last post by:
As a hardware engineer, after seeing that CEIWEI recently released a new tool for Modbus RTU Over TCP/UDP filtering and monitoring, I actively went to its official website to take a look. It turned...
0
by: ArrayDB | last post by:
The error message I've encountered is; ERROR:root:Error generating model response: exception: access violation writing 0x0000000000005140, which seems to be indicative of an access violation...
1
by: Defcon1945 | last post by:
I'm trying to learn Python using Pycharm but import shutil doesn't work
1
by: Shællîpôpï 09 | last post by:
If u are using a keypad phone, how do u turn on JavaScript, to access features like WhatsApp, Facebook, Instagram....
0
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 3 Apr 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome former...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.