07-08-2018 07:40 PM
When I work with some class made on Visual Studio in a external environment (LabVIEW/Unity), the methods that i created are not visible so I can't use them.
I used to work without any problem a few months ago, I don't know what happened.
Could anybody help me with this?
Solved! Go to Solution.
07-08-2018 09:02 PM - edited 07-08-2018 09:02 PM
Check it isn't related to LabVIEW / Framework compatibility. LabVIEW versions earlier than 2013 only supported CLR 2.0 unless forced to otherwise via a config file change (which might be why it stopped working if you are working on another machine etc.).
Also check what's loaded into memory: http://zone.ni.com/reference/en-XX/help/371361P-01/lvdialog/assemblies_in_memory/
07-09-2018 05:43 AM
Did you change the method or the entire object class to be static? In that case you won't need an object instantiation but simply use the LabVIEW property or method node set to the right calls to invoke the static method or attribute call.
07-12-2018 10:40 PM
I use LabVIEW 2015 and Visual Studio 2015 Professional/Visual Studio 2017 Community and I have tried changing the version of .NET Framework,
I used to do my classes on Visual and using them in LabVIEW without any problem, but suddenly the methods were not visible, i thought it was a LabVIEW problem
But then working with Unity, my classes methods didn't appear
07-12-2018 10:45 PM - edited 07-12-2018 10:50 PM
Another option you could try is to create another project in your Visual Studio solution (say a Console-based one) that uses your 'suspect' project as a dependency and then try to access the same class properties and methods.
Maybe give us some example code to work with and we can provide some better suggestions. If you provide the actual assembly (.dll) file we can also probe that to see if there is anything strange going on.
10-07-2018 10:53 AM
Someway there was some .NET libraries missing, so I searched to download again.