<div>
Don't you register these dlls when you deploy your app ? Did you use tlbimp.exe to generate the .Net wrapper of your native C++ dll ?
</div>


Don't you register these dlls when you deploy your app ? Did you use tlbimp.exe to generate the .Net wrapper of your native C++ dll ?

<div>
<div class="content wysiwyg-content">
I am having a problem with a third party dll when installing my applications on some other machines. &nbsp;Note that it works fine on some machines and not on others. &nbsp;My application references a dll called UNIVOPT_CSLOADER.dll which is a .NET wrapper for the C++ dll, CSUNIVOPT. &nbsp;When it fails it throws this error message: &nbsp;The type initializer for &quot;CSUNIVOPT&quot; threw an exception. &nbsp;Looking at the stack trace this happens when I first try to call a function from this dll.<br />
<br />
The dll in my application, UNIVOPT_CSLOADER, resides in my applications directory and the other dlls are in my System32 dir. &nbsp;These other dlls also reside in the C:\MBRM dir, the install directory for this product, but I have renamed them and run the application to confirm that it is calling the ones in the System32 dir.<br />
<br />
If I move this application into the C:\MBRM directory it runs fine, but if I try and move all the dlls into from the MBRM dir into my apps dir I have the same problem. &nbsp;<br />
<br />
Why would the same dll's try to load their dependant dlls from different places on different machines?
</div>
</div>


I am having a problem with a third party dll when installing my applications on some other machines.  Note that it works fine on some machines and not on others.  My application references a dll called UNIVOPT_CSLOADER.dll which is a .NET wrapper for the C++ dll, CSUNIVOPT.  When it fails it throws this error message:  The type initializer for "CSUNIVOPT" threw an exception.  Looking at the stack trace this happens when I first try to call a function from this dll.

The dll in my application, UNIVOPT_CSLOADER, resides in my applications directory and the other dlls are in my System32 dir.  These other dlls also reside in the C:\MBRM dir, the install directory for this product, but I have renamed them and run the application to confirm that it is calling the ones in the System32 dir.

If I move this application into the C:\MBRM directory it runs fine, but if I try and move all the dlls into from the MBRM dir into my apps dir I have the same problem.  

Why would the same dll's try to load their dependant dlls from different places on different machines?

Dll throws Error on non dev machine

The .NET Framework is not specific to any one programming language; rather, it includes a library of functions that allows developers to rapidly build applications. Several supported languages include C#, VB.NET, C++ or ASP.NET.

.NET Programming

Microsoft Visual C++ (often abbreviated as MSVC or VC++) is an integrated development environment (IDE) product from Microsoft for the C, C++, and C++/CLI programming languages. It features tools for developing and debugging C++ code, especially code written for the Microsoft Windows API, the DirectX API, and the Microsoft .NET Framework. Many applications require redistributable Visual C++ packages to function correctly and are often installed independently of applications, allowing multiple applications to make use of the package while only having to install it once

Visual C++.NET

C# is an object-oriented programming language created in conjunction with Microsoft’s .NET framework. Compilation is usually done into the Microsoft Intermediate Language (MSIL), which is then JIT-compiled to native code (and cached) during execution in the Common Language Runtime (CLR).