Visual Studio 2005 Issue

[lbauer]

Thanks for the information.

Some caveats:

Users should use caution when making changes to their registries.
Also, we want to remind users that we do not officially support Vault 3.5.x on Windows 7.

[Beth]

Our developers are looking for a nicer way of dealing with this than messing with the registry, but we can't guarantee that even with this that older versions will work well with Windows 7.

The latest version is being tested on Windows 7 and doesn't have this issue. For other users running into this, I'd recommend contacting our sales department at sgstore at sourcegear.com to get a quote for upgrading. If you carry current maintenance, the upgrade is free.

[JohnMo]

After working through all of the registry and DLL registration suggestions and still having the SSMS problem, I discovered that starting SSMS using "Run as administrator" solved the problem. I'm not sure why it's necessary because my login account is assigned to the Administrators group, but it works.

[lbauer]

Thanks for the update.

[Stacey]

I was having a similar issue to everyone here with Windows 7. SSMS wasn't working due to the invalid com interface. I had tried the various registry hacks and registering specifically the actxprxy dlls. Even tried completely uninstalling SSMS.

Finally after days of searching I found this:

http://www.davidmoore.info/2009/08/19/s ... er-errors/

Re-registering the ieproxy was the one that finally fixed it up for me.

[Stacey]

Keep in mind that this just repaired some of my problems in Windows 7, it didn't fix the windows explorer error nor does the visual studio -> source gear integration work.

Installing 4.1.4 doesn't fix that either.

Not sure what it takes to get version 4 functional on Windows 7, if it can be done at all. Unfortunately we're stuck on version 4 due to the 3.5 framework requirement of version 5.

[lbauer]

Unfortunately we're stuck on version 4 due to the 3.5 framework requirement of version 5.

What limitation are you running into?

[Stacey]

Unfortunately we're stuck on version 4 due to the 3.5 framework requirement of version 5.

What limitation are you running into?

Windows Server 2003 64-bit Itanium doesn't support the .NET 3.5 Framework, so we aren't able to upgrade to version 5. And our best/only real option to run .NET 3.5 is our 3 year old HP Itanium server and it doesn't support upgrading to Windows 2008.

I'm still stuck with trying to run Vault & SQL Server 2005 simultaneously on Windows 7 as the Vault installs have corrupted my SQL Server 2005 client tools. I'm trying a service pack from MSFT now, but I'm losing patience with the Vault installs.

[Beth]

Are you just trying to run the client on Windows 7 or are you trying to run the server and the client on Windows 7?