After installing Vista RC1 the problems I had installing VSS were resolved so for a while I was quite happy working with VSS on Vista. Today though I’ve just stumbled across the following problem:
Assume that you have a network share containing a VSS database which you use to store your development team work, and that you’ve provided the right security privileges in that share so that everyone in your team can access and modify it.
Also lets assume that you’ re working on a project that requires running Visual Studio as administrator (elevated mode in UAC).
In this case you are not running Visual Studio with your account anymore and of course you can no longer access the network share containing the VSS Database, and thus cannot work with source control over your project.
What’s oxymoron is that if you want to work around this problem you must allow everybody access to the particular share, thus lessen the security on the share in order to tighten security on your local machine.
I believe that this is not something that was done intentionally but something that was not considered when implementing UAC and something that will be resolved in the final built but never the less it’s something that gets on my nerves.
 Of course you can always have 2 Visual Studios to work with, one running in UAC elevated mode to run your project and another in normal mode to edit it (this will run as your account thus having access to VSS Database share.