Visual studio 2003 and 2005

[Aaron]

will running visual studio 2003 and visual studio 2005 alongside cause any
problems?

[Gerry O'Brien [MVP]]

One of the issues you will run into is that VS 2005 will take associations
away from 2003. i.e. if you double click a .sln file or any other VS
associated file, document invocation will default to 2005.

--
Gerry O'Brien
Visual Developer .NET MVP
Visual Basic
"Aaron" <ku*****@yahoo.com> wrote in message
news:OQ*************@tk2msftngp13.phx.gbl...

will running visual studio 2003 and visual studio 2005 alongside cause any
problems?

[Gerry O'Brien [MVP]]

One of the issues you will run into is that VS 2005 will take associations
away from 2003. i.e. if you double click a .sln file or any other VS
associated file, document invocation will default to 2005.

--
Gerry O'Brien
Visual Developer .NET MVP
Visual Basic
"Aaron" <ku*****@yahoo.com> wrote in message
news:OQ*************@tk2msftngp13.phx.gbl...

will running visual studio 2003 and visual studio 2005 alongside cause any
problems?

[Schfooge]

" Gerry O'Brien [MVP]" <gk******@hotmail.com> wrote in message
news:ez**************@TK2MSFTNGP11.phx.gbl...

One of the issues you will run into is that VS 2005 will take associations
away from 2003. i.e. if you double click a .sln file or any other VS
associated file, document invocation will default to 2005.

--
Gerry O'Brien
Visual Developer .NET MVP
Visual Basic

It's possible this might occur the other way. If for some reason you
install 2005 first - or if you reinstall 2003 after you install 2005. The
last one installed will steal the file associations for itself.

[Schfooge]

" Gerry O'Brien [MVP]" <gk******@hotmail.com> wrote in message
news:ez**************@TK2MSFTNGP11.phx.gbl...

One of the issues you will run into is that VS 2005 will take associations
away from 2003. i.e. if you double click a .sln file or any other VS
associated file, document invocation will default to 2005.

--
Gerry O'Brien
Visual Developer .NET MVP
Visual Basic

It's possible this might occur the other way. If for some reason you
install 2005 first - or if you reinstall 2003 after you install 2005. The
last one installed will steal the file associations for itself.

[Mark Orlando]

I loaded the VS 2005 Preview on my PC and had problems when I went back to
VS 2003 and tried to run some -- not all -- but some projects in which
noting changed in the code but I got funky errors and the code would not
run. Help was all hosed then in VS 2003 as well.

I removed VS 2005 and VS 2003, rebooted and then reinstalled VS 2003 and was
good to go. I'll use VS 2005 on a seperate box and not on my main PC.

"Aaron" <ku*****@yahoo.com> wrote in message
news:OQ*************@tk2msftngp13.phx.gbl...

will running visual studio 2003 and visual studio 2005 alongside cause any
problems?

[Mark Orlando]

I loaded the VS 2005 Preview on my PC and had problems when I went back to
VS 2003 and tried to run some -- not all -- but some projects in which
noting changed in the code but I got funky errors and the code would not
run. Help was all hosed then in VS 2003 as well.

I removed VS 2005 and VS 2003, rebooted and then reinstalled VS 2003 and was
good to go. I'll use VS 2005 on a seperate box and not on my main PC.

"Aaron" <ku*****@yahoo.com> wrote in message
news:OQ*************@tk2msftngp13.phx.gbl...

will running visual studio 2003 and visual studio 2005 alongside cause any
problems?