Grant FullTrust permissions to VS .NET Projects on Network (Intranet) share

[Jay A. Moritz]

I'm having a huge problem setting up a shared folder on my network with some
VB Projects that I want other developers on the network to include in the
solutions they are developing. I have used the .NET Configuration tool
(Runtime Security Policy/Machine/All_Code/LocalIntranet_Zone) to add a new
code group for a URL with FullTrust permissions (followed instructions from
http://msdn.microsoft.com/library/d...tskgrantingpermissionstofoldersassemblies.asp),
but when anyone adds the project to a solution, they still get the Security
error about the source being on a network drive and not fully trusted.

Can I not trust Projects on a network drive?

Jay Moritz
Predictable Outcomes

 

[Nicole Calinoiu]

Did you add the new code group on each developer's machine? If so, are they
adding the projects using the same form of the path that you used for the
membership condition? If so, what's the path you used, and what result do
you get when you evaluate the permissions
(http://support.microsoft.com/kb/815170/EN-US/) of assemblies in the
project's bin directory?

 

[Jay A. Moritz]

Nicole,

I'm currently just testing on one machine (If I get one to work, I can
copy the XML and get them all to work). To map to the network share I used
file://server/share/* just like it says to in the instructions.

This looks like my problem... When I evaluate the permissions for the
assemblies in the bin folder the code group that grants permissions to the
assembly is Machine/All_Code/IntErnet_Zone/Internet_Same_Site_Access. The
assmeblies are not even registering as being Intranet, could this be becuse
the network is a workgroup and not a domain? (Domain controler server is not
getting delivered till next week)

Jay Moritz

P.S. I tried setting permissions for the share in the Internet_Zone node,
but the assemblies still get only Internet_Same_Site_Access

 

[Nicole Calinoiu]

The problem may lie with your choice of URL. Instead of using a file:
protocol URL, try using just the UNC path (e.g.: \\server\share\*), and make
sure you're using the same UNC path when opening the project in VStudio.
Also, if you're using the server IP address, try switching to using the
server name instead.

BTW, the fact that you're not on a domain should have no effect on
discrimination between intranet and internet membership.

HTH,
Nicole