.NET 4.0 security restrictions being applied to Assemblies?

Unity Engine
1

Hello,

I recently had an HOTween user encounter this error after placing HOTween’s Assembly in his project:

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.

Thing is, this error should be strictly related to the more recent .NET 4.0 security restrictions (which avoid DLLs compiled on other computers to run on yours, unless you specifically allow it), but as far as I know Unity has nothing to do with .NET 4.0. Anyone knows what might be the cause, and how this could be solved (possibly from the original assembly compiler’s side)?

Thanks

2

Potentially the dev started the project from VisualStudio through UnityVS?

3

@dreamora: I was hoping you were right, but it seems that Nezabyte (the user having this issue) is having it with MonoDevelop.