...to get you to read the instructions!
In the past, the following error message "the project location is not trusted" has not caused many problems. There's been a little utility called the .NET Framework 2.0 Configuration mmc snap-in (gotta love Microsoft and the names that the marketing department come up with). However, someone made a decision to not include this tool in Vista. It was obviously proving far too useful and having a positive impact on people's productivity, so out it came </rant>
After some careful Googling around the Internet, caspol.exe was found to do a similar job. However I couldn't get it to work. I tried for about 5-10 minutes before eventually asking for help. Was pointed in the direction of the instructions, told I was doing it wrong, and then the problem was solved. How is it that someone who knows nothing about .NET, Code Access Security Policies and the technical differences between XP and Vista can point out that I've not included as many parameters as I needed to at the command line!?
For future reference though, the link is here (and it's a very picky program)!