.NET dll doesn't show classes

[rajneesh]

Hi,

As part of specifying the module for an action, I specify a .NET dll in "Step Setting for Action", but NetStand doesn't show me the classes present in the dll.

This dll is made on in Visual studio 2005 and depends on other dll and .libs.

The dependant dlls are present in the same directory as the .NET dll.

The .NET dll is made out by using dependent static libraries.

Another fact is size of this dll exceeds 1MB (in case teststand4.0 evaluation version has a limitation on size of dll module).

Kindly suggest how this problem can be rectified so that I can see the classes in dll and use their functions.

Regards,

-Rajneesh.

[nickb]

Hi Rajneesh!

Neither the size of the dll nor its dependance on other dlls should cause problems with seeing the available classes in TestStand.  One thing that might cause an inability to see available classes in TestStand would be if your classes were declared as private.  An interesting test would be to see if you could add the dll as a reference in a new C# or VB .NET project, and see if you have access to the classes in Visual Studio.  Check these two things, and let me know what you find out!

NickB

[rajneesh]

Hi Nick

Thanks for your reply.

Well, I guess the problem was with the .libs on which my dll depended.

Actually, when I built my dll, I provide it with the static libraries that it requires and hence as an outcome, the dll has those libraries built in it (The run time dependent dll's were of course provided externally).

I believe test stand wants those libs as well (through labWindow/CVI adapter configuration; configure auto-loading of support libraries needed for linking).

Any idea why testStand needs static libs (when they are already part of the dll).

Regards,

-Rajneesh.

[nickb]

Hi Rajneesh!

That is interesting behavior that you are describing.  I am curious what language you are programming in, and whether you are talking about a C dll, or a .NET assembly.  Also, if you are using the .NET adapter, it should not matter what changes you make to the CVI adapter settings.  If you could post a small example sequence that shows the behavior that you are seeing, I would be happy to take a look at it!

NickB