Setting FullTrust for CSLA

Blacksheep posted on Thursday, March 29, 2007

I am new to CSLA and VS2005 but very interesting in its benefits. I am trying to get the 2.1 framework installed and compiled.

When I open the clsacs solution I get the following message "The project location is not trusted: {full path where project exists}   Running the application may result in security exceptions when it attempts to perform actions which require full trust.   Click OK to ignore and continue." I seems to compile fine, but I get similar messages for several projects when attempting to open the Project Tracker sample application.

I am not familar with setting FullTrust permissions to applications. I have Rocky's install document, but it doesn't tell me how to set up the FullTrust. I haven't been able to find anything that makes it clear to me how to go about doing this. Can anyone help me or point me to good documentation?

I am interested in initially getting the CLSA and the Project Tracker application working, but also what are the best practices for this when deploying my own applications into production environments.

Q Johnson replied on Thursday, March 29, 2007

I believe the last time I got this behavior I had just downloaded a new version of the framework.

Courtesy of all the paranoia about files from other computers, there is now a need to "Unblock" the file so that its contents are given due respect.

If this is what caused your problem, your fix is pretty easy.  First, blow away the CSLA folder you currently have and make a new empty one.  Then, using Windoze Explorer, find the .zip file you used to populate it last time.  Right click on it and choose Properties.  You'll see the Unblock button at the bottom of dialog.  After unblocking, you should be able to unzip the contents as you did before, but you shouldn't see any more warnings about it being untrusted when you reference the project folder in a VS solution.

Of course, if this ISN'T what caused your problem, you just wasted five minutes.  Oh well.

Hope this helps.

 

 

Blacksheep replied on Tuesday, April 03, 2007

Thanks! Unblocking the .zip file was the solution. Funny I had never had this type of problem befoe with programs from a .zip file.

ajj3085 replied on Tuesday, April 03, 2007

Its a new feature of IE.  See Rocky's blog on the topic.

Curelom replied on Friday, March 30, 2007

You should be able to find your solution here http://www.acthompson.net/DotNet/setting_a_trusted_location.htm

The issue is that the directory you have the project in is not trusted by the .net framework.  The link above shows how to set it as trusted.

ajj3085 replied on Friday, March 30, 2007

I think checking out the zip file would be worth attempting though as well, because that would cause the same problems even on the local disk, which already has full trust.