>>>>Hi,
>>>>
>>>>You should be able to place the project where ever you wish (you can set the default location in 'Tools/Projects and Solutions')
>>>>The only time I've seen the error you mention is when the location is specifed using a UNC path (or possibly a mapped drive) - presumably that's not the case with your C drive? Maybe there's some other CAS policy set?
>>>>
>>>>Regards,
>>>>Viv
>>>>
>>>The files were marked as read-only. Once I unmarked them, it worked.
>>
>>Interesting. Which files exactly were marker R/O? - I just tested by marking the entire bin folder as R/O and didn't get any errors opening the project - but I did, obviously, get errors on build. This was on a project under source control so most files were R/O anyway.
>
>Yes, that's the case - the project was from Source Safe and I got errors on build. I didn't check what files exactly were read-only, may be all of them, but I applied not read-only to all folders and files and subfolders.

R/O on the bin folder would certainly explain the build errors - but not the 'Trusted Path' warning. Oh well - as long as it's gone......