LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

What does it mean that Invoke Node Method is not available in run-time engine

I'm building application that select different .NET assemblies located in the same root folder. It is very likely that wrong :NET assembly is selected automatically. So it is very important to tell Labview witch .NET assembly to use !!!

 

I'm using also TestStand, there I have .NET adapter and absolute path to assembly CAN BE defined ok. I found private .NET.LoadAssembly method but when I display help I see something very strange... It says it is not available in the run time engine?!? What does it meas? If this means that I can use this method only in the application developement, this is very big fail in Labview. Why then should I use it? Labivew must have something else, some other methods to programatically select .NET assemblies??!!?

AndrazS_0-1667542402247.png

 

0 Kudos
Message 1 of 3
(923 Views)

This means that the method cannot be executed in a compiled executable.

If you run your application in the development environment, it's ok.

Paolo
-------------------
LV 7.1, 2011, 2017, 2019, 2021
Message 2 of 3
(912 Views)

Did you notice the dirty brown color of the node? That means that it is a node that is not officially released by NI but only exists for private uses with NI tools. This also answers your question why you should use it: You shouldn’t!

 

These nodes are there (and without special ini token not accessible in the LabVIEW menu) because they were either an experiment that may or may not get eventually an official feature or because some NI tool needed a specific method to do something. These nodes may crash, eat your harddrive or do anything else you don’t like, if called in other ways than what NI has tested it for. Use of it is entirely at your own fisk and if you try to get technical support for it because something doesn’t work, support will claim this method doesn’t exist and from their point of view they are right. They don’t know about it and are not supposed to know about it.

 

As to loading .Net assemblies by specific path, that is a feature the .Net framework actively tries to make as impossible as possible. Several of the original methods from the 2.x framework time to do that will cause prominent warnings that this method is obsolete and one should try to avoid it.

Rolf Kalbermatter
My Blog
Message 3 of 3
(895 Views)