Visual Studio 2005 Installation Tidbits

My main Windows XP installation at home is due for a reinstall because of excessive installations of alpha and beta versions. But, I decided to extend the life of this two year old beast, because reinstalling all your apps, reactivating Windows XP and Office 2003 and several other applications is a lot of work.

So I first started with deinstalling the SQL Server 2005 Standard Edition CTP version I had installed. I read somewhere that the tool to uninstall beta and CTP builds of VS 2005 and .NET Framework 2.0 does not fully support deinstalling SQL Server 2005 CTPs. After the SQL Server 2005 deinstall I ran the tool. This worked without problems.

I found some .NET 2.0 related stuff didn't get removed, so I removed them manually:

  • Guidance Automation Toolkit (uninstall did not fully work)
  • Composite UI Application Block
  • WinFX SDK
  • WinFX Visual Studio Extensions

This is what I installed (in order):

  1. SQL Server 2005 Developer Edition with Analysis Services, Integration Services and Reporting Services.
  2. SourceSafe 2005
  3. Visual Studio 2005 Team Suite (Trial Version)
  4. Team Foundation Client
  5. Office Visio for Enterprise Architects

I had a couple of problems during this process:

  1. At the first attempt to install SQL Server 2005 I used a service account instead of the local system account for the SQL services. The installation of the database engine failed. I temporarily shut down my Kerio Personal Firewall and used the local system account for the second attempt. This time the engine installed without errors.
  2. SourceSafe installed without problem.
  3. I could not select a partition to install VS 2005 on, because setup complained that Visual Studio 2005 Premier Partner Edition was already installed on the C: partition. A little investigation showed that this is the IDE for SQL Server Analysis Services, Integration Services and Reporting Services. This IDE wasn't a trial version, but after the installation of Team Suite these SQL Server developer products were integrated in the Team Suite Trial Edition. I wonder if everything becomes disabled if the 180 day trial period runs out.
    During startup VS 2005 complained about a left-over package from the Guidance Automation Toolkit. You can tell VS to skip loading it when it complains, but then it reappears when you reset your settings. So I removes some registry keys to stop it from appearing ever again.
  4. I had trouble locating the "Tools | Connect to Team Foundation Server" menu-item in Team Suite that I was familiar with from Beta 2 (*). It turns out that you have to install Team Foundation Client from the Team Foundation Server installation medium to get the Team Explorer functionality ( I think it is lousy that the Team Suite and role-based Team Editions don't have this functionality out-of-the-box. The Team part in their name is really confusing, because Team Explorer can also be installed on top of the Professional and Standard edition of Visual Studio 2005. This gives them the same team functionality.
  5. Office Visio for Enterprise Architects installed without problem. But this English version hijacked my Dutch version of Visio 2003.  Both Visio Start menu items start the Enterprise Architects version.

A thing I might try in the future is to let Windows Installer repair the SQL Server installation. I wonder if this will turn the VS 2005 IDE back to the original non-trial state. I will probably have to reinstall VS 2005 anyway if my employer is kind enough to provide me with the non-trial version of Team Suite or manages to transition my partner based MSDN Universal Subscription to one of the role-based Team Editions.

All is well that ends well. Everything is running fine now, so I am glad that I didn't reformat my hard drive just yet.

(*) When attempting to locate the "Connect to Team Foundation Server" menu item, I noticed that my user settings and my recent project list from Beta 2 were still present in the RTM version. I ran the undocumented devenv.exe /ResetUserdata from a Visual Studio 2005 Command Prompt to clean those out.

Leave a Reply

Your email address will not be published. Required fields are marked *