Scripting Polymorphic VI

[tst]

Those VIs are locked (at least the last time I checked) and, more importantly, they work on C DLLs, whereas he wants .NET.

The problem here is that he is trying to do something which most people don't need to do, because the invoke node already lists all the methods with their data types. His problem is with that he doesn't want a long list of methods, but a hierarchy. Hence the detour through all the wrappers and the poly VI.

[m3rl3n]

tst,

Pretty much nail on the head there.

As it stands now, I have a process that will work.  I was just looking at a possible way to automate the whole thing so that when the .NET drivers are updated, the programmer doing the update could just run the script that would then search through the many classes of the driver and build the interop VIs for each method, then build a polymorphic that would list all of the methods in a manner that would use the menu flyout to select each method.  I have the bulk of all of that working and it works well. It's just that as it stands right now, the programmer would have to set the "seed" VI to one of the methods within each class, for each and every class.  As you said, that is what I'm trying to automate and as I"ve said as it stands now, it is workable, but if I could get that last bit...  wow, it would be perfect.

I'll keep looking.

Dan