Search the Community

Hello LAVA, I'm making a .NET interop assembly from a few similar VIs which have a cluster as input, some of them have 3 DBL inside the cluster, some have two DBL.. Using some magic, the compiler creates a .NET class for each cluster found. And then, when using that dll we have to Construct a cluster object which we can set the values and then use the object reference as input to the method... After the first attempt I realized I had different clusters with the same name "Parameters" among my VIs, but the DLL will need different names for each of them. This makes sense so no big deal let's give them a meaningful name. Here's the bug, even if I give different names to all my controls, when the compiler finds a second "3 dbl" cluster it will not create another "3 dbl" class, resulting to the impossibility to construct that class when using the dll. If I try to use the same "3 dbl" class for my two methods, the wrong named one will crash for the name difference... The only workaround I found so far is to make the second cluster "3 sgl" instead so the compiler sees a different type and creates its class. I think it's not ideal to workaround like that so I will try to avoid clusters in these cases because they are simple unarrayed clusters so I can just take 3 inputs on the VI. Anyone familiar with this? Cheers