This post may simply be a product of my own ignorance, but hopefully it can help someone else out there in a similar situation.
So recently I was tasked with setting up a Vista Business 64-bit laptop for a developer in our office. The needed applications are as follows:
SQL 2005 – full reporting and management tools
SQL 2008 – full reporting and management tools
VS Pro 2005
VS Pro 2008
VSTS 2005
VSTS 2005 add-on for database developers
Cisco VPN Client to connect to PIX
Office Suite
Adobe Fireworks CS4
I was told that the VSTS 2005 would not install on 64 bit Vista. Well that right there made me want to do it. I wasn’t about to let a new machine with 8GB of RAM go to waste by putting a 32-bit OS on it. I started by installing the following applications in this order(they can be picky, so please be sure to do in this order):
Vista SP1
Vista SP2
SQL 2005
SQL 2008
VS Pro 2005
VS 2005 Team Explorer – (may not have been necessary, but it didn’t hurt anything and I didn’t try the process without)
VS Pro 2008
VSTS 2005
VSTS 2005 SP1 Update for Vista – *
VSTS add-on for database developers
* – This is critical. Without this, the VSS cannot connect to TFS server and Team Suite will not work.
Now, first off, UAC is a pain. Unless you have modified your local security policy to run all administrators with elevated privelages, and turned off UAC, you will likely have VS 2005(any version) and SQL 2005 fail to install. The error given can be anything from XP SP2 is not installed to permissions issues. To avoid this, do two things. I think you only need to do one or the other, but I did both, just to be safe.
Copy the contents of the install disks to the hard drive before running setup
Right-click and run setup as administrator
You should have no issues now with the initial installers going though. At this point, I was confused, as the developer had copied over a project and all the related files to his C: drive and was attempting to launch it, but it kept giving an error
Unable to connect to server.
Then it prompts me to remove source control data or temporarily work offline.
Neither of these were viable options. The strangest part was that I could goto Tools>Connect to TFS and see the projects on the server.
After speaking with someone on the MSDN forums, I realized that the issue was that there was no local path specified for source control to download files to. If you go to the Source Control node in the Team Exploere window, find the path for the solution and open it, it will prompt you for a location to download the source files to locally and proceed to download them and open your solution. The problem all along was that we were trying to access the solution that was copied over thinking it would find the TFS server and not actually downloading the source from TFS.
Like I said, possibly my own ignorance, but it was annoying enough that hopefully I save someone else the headache. Let me know if you have any questions or issues and I will do my best to answer them. I will try to post my solution for getting the Cisco Pix VPN to work on Vista x64 here in the next week.