Not allowed to load assembly from network location

May 2024 ยท 2 minute read

I've recently set up a new Windows Server 2012 R2 environment and installed Visual Studio 2012.

Now I'm having a problem with multiple .NET 4.5 project's I migrated from my old server, a Windows Server 2008 machine. This never occurred on the old server.

When trying to load an assembly from a network location, I run into the following issue:

An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information.

I've looked at some other questions, but none of them provide a working solution.

This is what I've tried so far:

All without success.

Is there another solution to solve this problem?

2 Answers

Adding the loadFromRemoteSources switch to machine.config solved the problem.

MSDN

The loadFromRemoteSources element specifies whether assemblies from remote sources should be granted full trust.

Example

<configuration> <runtime> <loadFromRemoteSources enabled="true"/> </runtime> </configuration> 

You can find machine.config here:

32-bit

%windir%\Microsoft.NET\Framework\[version]\config\machine.config 

64-bit

%windir%\Microsoft.NET\Framework64\[version]\config\machine.config 
7

I had the same problem, when trying to load a DLL on a local drive which came from a ZIP from the internet. The solution was to unlock the ZIP in its file properties. Finally, extracting the DLL again and now it loads without the error. No need to change the machine.config.

4

ncG1vNJzZmirpJawrLvVnqmfpJ%2Bse6S7zGiorp2jqbawutJoaXFrY25%2BcoKOp6atZZGhubDDxJ1kraddobyisIyaqqydnZe5unnFq6amZZ6awbi70aRkpaeTlsGqu80%3D