Installing Vault Client rendered Visual Studio inoperative

cdaniel · Post by **cdaniel** » Mon Jun 07, 2004 10:05 pm

Yesterday I installed the Vault client & server on this machine and checked a bunch of projects into the repository - no problems. I did not enable Visual Studio IDE integration.

Today I went to do some work on a large C# project and find that it is totally unusable - Visual Studio source control integration (with Source Safe) appears to be seriously broken now - I'm not even able to open the project any more. Projects that I didn't check into Vault work perfectly.

Any ideas? I was NOT expecting anything like this

cdaniel · Post by **cdaniel** » Mon Jun 07, 2004 10:59 pm

Not a solution, but progress: whatever Vault messed up, it has to do with the crypto providers. VS.NET is now unable to sign any C# assembly - it gets an "access denied" error, listing the DLL that's being built, but that error is, I believe, nonsense. I believe it's nonsense because I've compeltely wiped the development directory and re-created everything from Source Safe. What could Vault installation have possibly screwed up so that VS.NET is unable to sign assemblies?

(Indeed, removing the AssemblyKeyFile attribute from the assembly so that VS.NET doesn't try to sign the assembly causes the compile to succeed).

Post by **jeremy_sg** » Tue Jun 08, 2004 5:56 am

The access denied error is caused by not having the right permissions to the c:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys

The Vault Server install is the only install that touches that directory's settings. The client install shouldn't touch it at all. It's possible that the install messed up the security settings for that directory.

cdaniel · Post by **cdaniel** » Tue Jun 08, 2004 7:36 am

That was it alright. The server install apparently modified the security for this directory and took away some rights that VS needs.

Thanks for the tip!