IO error assembly error

This is most likely out of scope for Document X, but as I am receiving the error in DocX, I thought i'd post.

I am able to load and build from local c:\ assembly's and XML comment files. When I copy the same assembly's to a network drive. Create a new project and attempt to load, I receive a load .NET assemblies error in Doc X. MS EnterpriseLibrary is in the network drive, as it was on my local directory.

System.IO.FileLoadException: Could not load file or assembly 'Microsoft.Practices.EnterpriseLibrary.Configuration.Design, Version=3.0.0.0, Culture=neutral, PublicKeyToken=2ed8dda04fe564ab' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)
File name: 'Microsoft.Practices.EnterpriseLibrary.Configuration.Design, Version=3.0.0.0, Culture=neutral, PublicKeyToken=2ed8dda04fe564ab' ---> System.Security.Policy.PolicyException: Required permissions cannot be acquired.
at System.Security.SecurityManager.ResolvePolicy(Evidence evidence, PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset, PermissionSet& denied, Boolean checkExecutionPermission)
at System.Security.SecurityManager.ResolvePolicy(Evidence evidence, PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset, PermissionSet& denied, Int32& securitySpecialFlags, Boolean checkExecutionPermission)

Permanently deleted user 16 July 2007 10:48

This is a security exception raised by the .NET Framework as Document! X attempts to load the assembly for documentation - raised because the dependancy is on a network drive.

You could change the Zone Security (in windows Adminsitrative Tools, '.NET Framework x.x Configuration') to allow assemblies to be fully loaded from a network path, but be aware that this will affect all applications, not just Document! X and is probably not security best practice. The best solution would be to copy the dependancies to a local path if possible.

IO error assembly error

1 comment