Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / New Users / April 2005

Tip: Looking for answers? Try searching our database.

using Code Groups

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
GaryT_Utah - 20 Apr 2005 04:50 GMT
Using Mscorcfg.msc, I created code group "MyTrustedCode":
  Runtime Security Policy
        Machine
              Code Groups
                    All_Code
                       LocalIntranet_Zone
                               MyTrustedCode
MyTrustedCode type is URL, the permission set is "FullTrust", and I checked
"This policy level will only have the permissions from the permission set..."
      the URL is specified as:
                   file://MY-PC/G$/My_Files/*
                            where MY-PC is the full computer name and G$ is
the share  
                            name of a local drive and My_Files is the name
of a folder
                            under the root of G$

My question is why do I continue to get the warning that "The project
location is not fully trusted...." when I open projects in the My_Files
folder?
                               

 
Richard Blewett [DevelopMentor] - 20 Apr 2005 07:37 GMT
My guess is that the assembly doesn't match the membership condition for some reason. Use "Evaluate Assembly" off the context menu of the "Runtime Security Policy" node of mscorcfg and see what code groups mscorcfg think your assembly matches

Regards

Richard Blewett - DevelopMentor
http://www.dotnetconsult.co.uk/weblog
http://www.dotnetconsult.co.uk

  Using Mscorcfg.msc, I created code group "MyTrustedCode":
Runtime Security Policy
Machine
Code Groups
All_Code
LocalIntranet_Zone
MyTrustedCode
MyTrustedCode type is URL, the permission set is "FullTrust", and I checked
"This policy level will only have the permissions from the permission set..."
the URL is specified as:
file://MY-PC/G$/My_Files/*
where MY-PC is the full computer name and G$ is
the share
name of a local drive and My_Files is the name
of a folder
under the root of G$

My question is why do I continue to get the warning that "The project
location is not fully trusted...." when I open projects in the My_Files
folder?
GaryT_Utah - 23 Apr 2005 17:45 GMT
Thank you.  The "Evaluate Assembly" option reveals that mscorcfg does not see
the code group I created under Machine/Code
Groups/All_Code/LocalIntranet_Zone as applicable.  My first attempt was made
following steps outlined in an MSDN VB and Visual C# Reference article.  I
plan to retrace my steps and create a new code group under My_Computer_Zone.  

With your help, My_Computer_Zone seems to be a better choice.  I wonder if
LocalIntranet_Zone would apply to a web service?

Richard, thanks again for your timely and helpful advice.

> My guess is that the assembly doesn't match the membership condition for some reason. Use "Evaluate Assembly" off the context menu of the "Runtime Security Policy" node of mscorcfg and see what code groups mscorcfg think your assembly matches
>
[quoted text clipped - 24 lines]
>  location is not fully trusted...." when I open projects in the My_Files
>  folder?

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.