Solving Visual Studio’s trust issues
// April 8th, 2009 // No Comments » // .Net, Security, Troublesolving, Visual Studio
I use Subversion for all my code. I also like to keep my checked out code on a mapped network share since it has backup and is accessible from outside my main dev machine. With this setup you will sooner or later (probably sooner) run into the problem with Visual Studio not trusting the network share, and subsequently hitting you in the face and kicking you in the groin. To make our beloved studio behave more decent, I executed the following line of goodness into a Visual Studio Command Prompt:
caspol -machine -addgroup 1 -url file://h:/* FullTrust -name DevShare
This will put the mapped drive “h:” in the “Full Trust” group. Just replace the drive name (and perhaps choose another name than “DevShare”) with your specifics, and you should be good to go! Hopefully this will help someone. If not, you could check out the following post on StackOverflow.
