"GM" <gmdevREMOVE@starband.net> wrote in message
news:%23g4tzG4PEHA.2420@TK2MSFTNGP10.phx.gbl...
> Is there a place that documents the recommended order for installing
> development tools such as VS.NET and SQL Server?
>
> Thanks!
>
>

"Peter van der Goes" <p_vandergoes@toadstool.u> wrote in message
news:eHukyd$PEHA.3016@tk2msftngp13.phx.gbl...
>
> "GM" <gmdevREMOVE@starband.net> wrote in message
> news:%23g4tzG4PEHA.2420@TK2MSFTNGP10.phx.gbl...
> > Is there a place that documents the recommended order for installing
> > development tools such as VS.NET and SQL Server?
> >
> > Thanks!
> >
> >
> I'm not aware of any document(s) that could be considered an authoritative
> source for installation order, but I can tell you that there are no
> sensitivities associated with the two products you mention, IME.
> Unlike the situation with IIS and Visual Studio .NET (where you must
install
> IIS first, or go through special procedures to map VS.NET to IIS), You can
> install SQL Server before Visual Studio .NET or after, and Visual Studio's
> Server Explorer will find your SQL Server instance with no problems. I
have
> installed Visual Studio .NET 2003 on a PC with an instance of SQL Server
> 2000 already installed, then installed a second instance of SQL Server
after
> VS.NET and had no product interaction issues.
>
> --
> Peter [MVP Visual Developer]
> Jack of all trades, master of none.
>
>

"GM" <gmdevREMOVE@starband.net> wrote in message news:<ekHB15CQEHA.3348@TK2MSFTNGP09.phx.gbl>...
> Thanks for your help, Peter. Much appreciated!
> -g
> "Peter van der Goes" <p_vandergoes@toadstool.u> wrote in message
> news:eHukyd$PEHA.3016@tk2msftngp13.phx.gbl...
> >
> > "GM" <gmdevREMOVE@starband.net> wrote in message
> > news:%23g4tzG4PEHA.2420@TK2MSFTNGP10.phx.gbl...
> > > Is there a place that documents the recommended order for installing
> > > development tools such as VS.NET and SQL Server?
> > >
> > > Thanks!
> > >
> > >
> > I'm not aware of any document(s) that could be considered an authoritative
> > source for installation order, but I can tell you that there are no
> > sensitivities associated with the two products you mention, IME.
> > Unlike the situation with IIS and Visual Studio .NET (where you must
> install
> > IIS first, or go through special procedures to map VS.NET to IIS), You can
> > install SQL Server before Visual Studio .NET or after, and Visual Studio's
> > Server Explorer will find your SQL Server instance with no problems. I
> have
> > installed Visual Studio .NET 2003 on a PC with an instance of SQL Server
> > 2000 already installed, then installed a second instance of SQL Server
> after
> > VS.NET and had no product interaction issues.
> >
> > --
> > Peter [MVP Visual Developer]
> > Jack of all trades, master of none.
> >