With .NET 4.0, a new security model was introduced. This new security model automatically grants full trust to locally available assemblies, but not to assemblies obtained from remote sources like the Internet, network locations, or via email. In case LabVIEW tries to access such an assembly's dll file with missing trust and is thus denied access, LabVIEW will return an error: An error occurred trying to load the assembly.Please note: This error message may also occur when you attempt to load a 64-bit .NET dll into a 32-bit version of LabVIEW or vice-versa.There are two ways to grant assemblies from remote sources full trust. Either by generally allowing LabVIEW to access these through a token in a .NET configuration file, or by allowing individual assemblies manually..NET configuration fileFollow these steps to allow LabVIEW access to all .NET assembly. Please note that this approach imposes a potential security risk.
Note: When using any virtualization solution like Parallels Desktop, VMWare Fusion, or Oracle VirtualBox to run Windows inside a virtual machine, the new security model treats the shared directories (e.g. folders that begin with /psf or \\vmware-host\) as remote sources, as these are accessed through a network link. You need to grant assemblies in these directories full trust as well.
Thank you for your feedback.
You changed your response to Not Helpful
You changed your response to Helpful
Collaborate with other users in our discussion forums
A valid service agreement may be required, and support options vary by country.