|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Untrusted Source Code location and Framework SecurityFramework 1.1 sp1. Our source code resides on a network share, primarily because it gets backed up every night. Our VSS is on another network share. in any case I had no problems with untrusted source locations until recently... I installed Visual Studio 2005 along with the .Net Framework 2.0 SDK. I still need to be able to run 2003 to support our existing applications and it doesn't seem to be a problem except for the security errors regarding the location of my source code. Specifically: "The project location is not fully trusted by the .NET runtime......" I have searched the web and tried everything I can get my hands on and none of it seems to work. I am hoping that someone can provide me with a suggestion to get this to go away. Sincerely, Tim Frawley Tim, Give this a try at your VS 2005 command prompt
You can use CASPOL to configure this: caspol -m -ag 1.2 -url "file://computername/share/*" FullTrust This gives full trust the the share specify, along with all subdirectories. I would be sure to restart VS 2005 after this is in place. This worked for me for I had exactly the same problem. -Eric Show quote "Tim Frawley" wrote: > I have been using Visual Studio 2003 for several years with the .Net > Framework 1.1 sp1. Our source code resides on a network share, > primarily because it gets backed up every night. Our VSS is on another > network share. in any case I had no problems with untrusted source > locations until recently... > > I installed Visual Studio 2005 along with the .Net Framework 2.0 SDK. > I still need to be able to run 2003 to support our existing > applications and it doesn't seem to be a problem except for the > security errors regarding the location of my source code. > Specifically: > > "The project location is not fully trusted by the .NET runtime......" > > I have searched the web and tried everything I can get my hands on and > none of it seems to work. I am hoping that someone can provide me with > a suggestion to get this to go away. > > Sincerely, > > Tim Frawley > > Eric,
Thanks for the reply. Visual Studio 2005 doesn't seem to have a problem. It's Visual Studio 2003 that has the security issues now. I am not sure where to fix this. In the .Net Framework 1.1 Configuration or the 2.0? Still no joy. Tim On your dev machine, go to "start", "programs", "microsoft visual studio .net
2003","visual studio .net tools", "visual studio .net 2003 command prompt" then paste in this line at prompt: caspol -m -ag 1.2 -url "file://computername/share/*" FullTrust change the computername and share to your own. restart your 2003 project from the share and see if you are still getting a security trust problem. Show quote "Tim Frawley" wrote: > > Eric, > > Thanks for the reply. Visual Studio 2005 doesn't seem to have a > problem. It's Visual Studio 2003 that has the security issues now. I > am not sure where to fix this. In the .Net Framework 1.1 Configuration > or the 2.0? > > Still no joy. > > Tim > > T,
Ah, thanks for the help. I tried that and noted that this created a child node in the LocalIntranet_Zone in .NET Configuration 1.1 management console. It worked but then I couldn't execute the assemblies from our intranet site. After thinking about it this is what I did. I went to the Runtime Security Policy and reset all. I then created two child nodes under the LocalIntranet_Zone one called Source with a reference to my network share and the other called Intranet with a reference to our intranet web site. Everything appears to be functioning normally now! Thanks Eric and T. I probably wouldn't have figured this out without your help. Sincerely, Tim Frawley at least it pointed you in the right direction. .NET security is complex, and
has caused me many sleepless nights. Too bad we live in a world where modern day development is so riddled with security issues. I remember the days when....never mind ;-) -Eric (AKA "T") Show quote "Tim Frawley" wrote: > I have been using Visual Studio 2003 for several years with the .Net > Framework 1.1 sp1. Our source code resides on a network share, > primarily because it gets backed up every night. Our VSS is on another > network share. in any case I had no problems with untrusted source > locations until recently... > > I installed Visual Studio 2005 along with the .Net Framework 2.0 SDK. > I still need to be able to run 2003 to support our existing > applications and it doesn't seem to be a problem except for the > security errors regarding the location of my source code. > Specifically: > > "The project location is not fully trusted by the .NET runtime......" > > I have searched the web and tried everything I can get my hands on and > none of it seems to work. I am hoping that someone can provide me with > a suggestion to get this to go away. > > Sincerely, > > Tim Frawley > >  |
|||||||||||||||||||||||
Other interesting topics