I've seen a couple of similar threads to this going around, but none of them seem to have been adequately addressed.
I work for the CS department of an educational institution where each student's "My Documents" folder is redirected to a network share. Their profiles are deleted after they log off, so we encourage them to use this share to store projects and
whatnot instead of saving to the local machine. Our classic problem with this has been the CAS policy's distrust of network shares. In VS 2008 and earlier, running caspol would allow us to set up a trust relationship:
E.G: caspol.exe -m -pp off -ag 1.2 -url file://\\UNC\path\* FullTrust
However, when we upgraded to VS2010, this command no longer worked. I notice that the caspol tool has been included in both .NET framework 2 and .NET framework 4 distributions, but after trying both we still cannot save files to network locations and saving
to drives mapped to "non-trusted" locations still behaves a little weirdly.
I have read the documentation that states that CAS is deprecated, but I'm wondering if there was any structure left in place to enforce trust relationships and how one might circumvent that, since I am obviously still unable to save to these locations.
Any help on this issue would be much appreciated.
View Complete Post