Last post Jul 31, 2005 08:24 PM by bpwill
Jul 31, 2005 08:24 PM|bpwill|LINK
Regarding VS 2003 warning: project location is not fully trusted by the .net runtime. I posted concerning this problem a few weeks ago. I have made a thourough search of this forum and did find posts about this problem dating back almost a year. I tried
implementing suggestions found, but have not been able to correct it. Most of the suggestions involved deleting the entire project and starting from scratch. Since I already have created my site locally, and have it running fine, this is not a step I want
to take. I just want to recompile my project in Release mode in order to publish it. I'm using XP, SP2, VS 2003, SQL 2000. Visual Source Safe is not installed.
However, I was able to set up a new project performing the same steps I had taken with my current project and open it in VS 2003 by using information in one of the posts I read. Before extracting the files in the ZIP, I right clicked, selected properties,
and clicked on Unblock. It turns out that this is a security issue with XP SP2. The new solution opened without problems. Now I'm wishing I had tried to open the my current project with VS 2003 before building the site...
When clicking on Help for this error, I'm directed to do the following:
To give a file share FullTrust permission
Note Make sure to add the asterisk at the end of the path.
I have followed these steps to no avail. Step 5 is where I think I might be going wrong - I've tried several things here.
You supposedly can also use comething called caspol.exe like so:
caspol -m -ag 1.2 -url urlname FullTrust
When I try to run this using the command line or just Run, I get a command not recognized error.
I've also Googled it, and looked at the MS knowlege base. I'm hoping not to have to spend a a couple of hundred bucks for a MS support case. If there is someone else that has been in this predicament, I would really appreciate your help.