.net controller does not create all functions

[Paul_Knight_Lockheed_Mart]

I have a .Net assembly, which I have attached that when I run the Create .NET Controller all I get is two functions.  They are the Initialize and Close.  I don't get any of the other public functions in the .fp file.

Using a .Net Viewer like .Net Reflector I can see all the public functions that are suppose to be in the dll.  The .dll is a 64-bit assembly and I am running LabWindows 2013 SP2.  I am trying to develop a 64-bit application and need this dll to talk to the instrument.

Thanks,

Paul

[Gloorious_Leader]

Hi Paul,

Basically, for unsupported types or for private/protected entities, the functions will not be generated in the instrument.

I hope that helps to get you started.

[Paul_Knight_Lockheed_Mart]

Steven,

So basically nothing can be done.

Paul

[Gloorious_Leader]

Paul,

Looking at the attached DLL, it appears that all the classes are in the default namespace. If they can be added to a new or different namespace, you should be able to create a .NET Controller in LabWindows™/CVI™. Beyond that, there is nothing I'm aware of that can be done.

[Paul_Knight_Lockheed_Mart]

Steven,

I have talked to the vendor, they are unwilling to recompile the dll since it works for everybody else and not LabWindows.

Paul

[Gloorious_Leader]

I've been asking around on how to approach this. It would theoretically be possible to write a .NET wrapper which exposes your needed functions in a named namespace. You could then create a .NET Controller for that wrapper.

[Paul_Knight_Lockheed_Mart]

Yes I can see how someone could do that using C#.  I will give it a shot.