Dependent .net assembly fails to load

[baldrik]

Hi,

I have written a .net assembly that has dependencies. I am using 2 PCs one for development and one for production in the lab, both running LV2014 SP1. I find that everything works correctly on the development machine but on the production machine -- I can instantiate the public class (via the constructor) but no public members are visible (properties or methods). There are no error messages. I installed visual studio on the production machine and built the assembly locally from identical source still no joy. 

I am using a project and all the assemblies are in the same directory under the directory containing the project file.

Using VIew>.NET Assembies in Memory I notice that a dependency does not appear to be loaded on the production machine. How do I go about fixing this? Any ideas why this is happening? Is there a log somewhere that might tell me why labview is not loading the dependency?

Any advice or Ideas greatly appreciated.

baldrik.

[baldrik]

Added text to first question

[baldrik]

I forgot to add that the dependency actually appears in the dependency list in project explorer, but is not loaded into memory.

[baldrik · Accepted solution]

I found that the depenency had its own dependency chain (via dependencywalker) and that an assembly in this chain was not installed. Not a labview problem after all.