[quoted text, click to view] On Thu, 20 Jul 2006 13:54:58 -0400, Bob Delaney wrote:
> Further to my post above on installing VS 2005. I thank Andrew and Peter for
> their suggestions on installing VS 2003 and 2005. I really don't need them
> side by side on this machine, and I will delete VS 2003 before running setup
> on VS 2005. Ditto for .Net Framework 1.1. I really don't need to have it
> installed on this machine, and unless someone tells me a compelling reason
> why not, I will uninstall it before running Setup for VS 2005 with .Net
> Framework 2.0.
> This post asks two additional things:
> 1. I have, through my MSDN subscription, SQL Server 2005 Pro Developer's
> Version, and have downloaded SQL Server Express. Should SQL Server ideally
> be installed before or after VS 2005, and briefly, why?
> 2. Any other tips for a smooth install of VS 2005?
I've had some problems with the help system when installing SQL Server 2005
Enterprise and VS 2005 on the same system - but now that I know the
solution (which is to go into the Combined Help Collection Manager and
enable the ones that aren't enabled) it's not a huge deal.
It's still probably a bit cleaner to just go with the SQL Express that the
other poster mentioned comes with the VS 2005 installation... Particularly
if you're going to be developing any ASP.NET pages. I tried to get the VS
2005 ASP.NET Configuration (under the "Website" menu in VS) to work with
SQL Server 2005 Enterprise and gave up after a while and just installed the
SQL Server Express that comes with VS (that I'd previously de-selected
during installation, since I had the full SQL 2005 Enterprise available)
Well.. Sorry for taking so long to reply... You may have done it already!
;) But.. After something probably over a dozen times installing VS 2005
(mostly Team Developer but also Pro and Team Architect) I haven't had any
other problems.
Cheers
