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

Upgrade Advice

P: n/a
Hi Newsgroup,

I'm currently using VS Ver 7.0.9466 with an OS of Server 2000 (domain
controller) Ver 5.0.2195 (Build 2195) SP4.

I have MSDN Universal and would like to upgrade my development environment
ot Server 2003 and VS 2003

Do I need to start from scratch, or will can I use Server 2003 as a simple
upgrade to my existing OS?
Do I need to remove VS 7 to upgrade to VS 2003?

Thanks.
Jul 21 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
I don't know the answer on the OS but you do not need to remove VS 7 1.0 to
install VS.NET 1.1. They coexist fine.

http://www.knowdotnet.com

"Dave Harney" <da********@wi.rr.com> wrote in message
news:uh**************@tk2msftngp13.phx.gbl...
Hi Newsgroup,

I'm currently using VS Ver 7.0.9466 with an OS of Server 2000 (domain
controller) Ver 5.0.2195 (Build 2195) SP4.

I have MSDN Universal and would like to upgrade my development environment
ot Server 2003 and VS 2003

Do I need to start from scratch, or will can I use Server 2003 as a simple
upgrade to my existing OS?
Do I need to remove VS 7 to upgrade to VS 2003?

Thanks.

Jul 21 '05 #2

P: n/a
Hi, Dave

This is really a more appropriate topic for
microsoft.public.windows.server.migration. This is not an MSDN managed
newsgroup, but the technet folks are there.

Dotnet should not be impacted by an upgrade. The migration should happen
seamlessly. It doesn't always, for any number of reasons. Most often this
is due to an idiosyncratic configuration. It doesn't matter if the upgrade
works 99% of the time if your system happens to be in the other 1%. If I
were doing it, I would use this as an opportunity to clean up the system
with a fresh install. If you decide to upgrade, back everything up and go
for it. The only thing you lose if it fails it time

Thank you for choosing the MSDN Managed Newsgroups,

John Eikanger
Microsoft Developer Support

This posting is provided “AS IS” with no warranties, and confers no rights.
--------------------
| Reply-To: "Dave Harney" <da********@wi.rr.com>
| From: "Dave Harney" <da********@wi.rr.com>
| Subject: Upgrade Advice
| Date: Wed, 21 Jan 2004 09:27:42 -0600
| X-Tomcat-NG: microsoft.public.dotnet.general
|
| Hi Newsgroup,
|
| I'm currently using VS Ver 7.0.9466 with an OS of Server 2000 (domain
| controller) Ver 5.0.2195 (Build 2195) SP4.
|
| I have MSDN Universal and would like to upgrade my development environment
| ot Server 2003 and VS 2003
|
| Do I need to start from scratch, or will can I use Server 2003 as a simple
| upgrade to my existing OS?
| Do I need to remove VS 7 to upgrade to VS 2003?
|
| Thanks.
|
|
|

Jul 21 '05 #3

P: n/a
One machine I upgraded and another I did from scratch. The upgrade had
several problems that were only resolved with a service call to MS (they did
a very good job). The fresh install when without a hitch. I may decide to
redo the other machine in time - but it will be a really big task due to
other software issues.

""John Eikanger [MSFT]"" <jo****@online.microsoft.com> wrote in message
news:%2****************@cpmsftngxa07.phx.gbl...
Hi, Dave

This is really a more appropriate topic for
microsoft.public.windows.server.migration. This is not an MSDN managed
newsgroup, but the technet folks are there.

Dotnet should not be impacted by an upgrade. The migration should happen
seamlessly. It doesn't always, for any number of reasons. Most often this is due to an idiosyncratic configuration. It doesn't matter if the upgrade works 99% of the time if your system happens to be in the other 1%. If I
were doing it, I would use this as an opportunity to clean up the system
with a fresh install. If you decide to upgrade, back everything up and go
for it. The only thing you lose if it fails it time

Thank you for choosing the MSDN Managed Newsgroups,

John Eikanger
Microsoft Developer Support

This posting is provided "AS IS" with no warranties, and confers no rights. --------------------
| Reply-To: "Dave Harney" <da********@wi.rr.com>
| From: "Dave Harney" <da********@wi.rr.com>
| Subject: Upgrade Advice
| Date: Wed, 21 Jan 2004 09:27:42 -0600
| X-Tomcat-NG: microsoft.public.dotnet.general
|
| Hi Newsgroup,
|
| I'm currently using VS Ver 7.0.9466 with an OS of Server 2000 (domain
| controller) Ver 5.0.2195 (Build 2195) SP4.
|
| I have MSDN Universal and would like to upgrade my development environment | ot Server 2003 and VS 2003
|
| Do I need to start from scratch, or will can I use Server 2003 as a simple | upgrade to my existing OS?
| Do I need to remove VS 7 to upgrade to VS 2003?
|
| Thanks.
|
|
|

Jul 21 '05 #4

P: n/a
Hi, Dave

Glad to hear that you are up and running.

Thank you for choosing the MSDN Managed Newsgroups,

John Eikanger
Microsoft Developer Support

This posting is provided “AS IS” with no warranties, and confers no rights.
--------------------
| From: "Dave Harney" <da********@wi.rr.com>
| References: <uh**************@tk2msftngp13.phx.gbl>
<#T**************@cpmsftngxa07.phx.gbl>
| Subject: Re: Upgrade Advice
| Date: Tue, 27 Jan 2004 14:05:52 -0600
| Lines: 59
| X-Tomcat-NG: microsoft.public.dotnet.general
|
| One machine I upgraded and another I did from scratch. The upgrade had
| several problems that were only resolved with a service call to MS (they
did
| a very good job). The fresh install when without a hitch. I may decide
to
| redo the other machine in time - but it will be a really big task due to
| other software issues.
|
| ""John Eikanger [MSFT]"" <jo****@online.microsoft.com> wrote in message
| news:%2****************@cpmsftngxa07.phx.gbl...
| > Hi, Dave
| >
| > This is really a more appropriate topic for
| > microsoft.public.windows.server.migration. This is not an MSDN managed
| > newsgroup, but the technet folks are there.
| >
| > Dotnet should not be impacted by an upgrade. The migration should
happen
| > seamlessly. It doesn't always, for any number of reasons. Most often
| this
| > is due to an idiosyncratic configuration. It doesn't matter if the
| upgrade
| > works 99% of the time if your system happens to be in the other 1%. If
I
| > were doing it, I would use this as an opportunity to clean up the system
| > with a fresh install. If you decide to upgrade, back everything up and
go
| > for it. The only thing you lose if it fails it time
| >
| > Thank you for choosing the MSDN Managed Newsgroups,
| >
| > John Eikanger
| > Microsoft Developer Support
| >
| > This posting is provided "AS IS" with no warranties, and confers no
| rights.
| > --------------------
| > | Reply-To: "Dave Harney" <da********@wi.rr.com>
| > | From: "Dave Harney" <da********@wi.rr.com>
| > | Subject: Upgrade Advice
| > | Date: Wed, 21 Jan 2004 09:27:42 -0600
| > | X-Tomcat-NG: microsoft.public.dotnet.general
| > |
| > | Hi Newsgroup,
| > |
| > | I'm currently using VS Ver 7.0.9466 with an OS of Server 2000 (domain
| > | controller) Ver 5.0.2195 (Build 2195) SP4.
| > |
| > | I have MSDN Universal and would like to upgrade my development
| environment
| > | ot Server 2003 and VS 2003
| > |
| > | Do I need to start from scratch, or will can I use Server 2003 as a
| simple
| > | upgrade to my existing OS?
| > | Do I need to remove VS 7 to upgrade to VS 2003?
| > |
| > | Thanks.
| > |
| > |
| > |
| >
|
|
|

Jul 21 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.