How can I handle global variables from different DLLs created based on VIs that access those variables

Question

My goal is to break apart an entirely LabView created application so I can still use parts of it (builded as Shared DLLs upon on some VIs) in my new .Net application. My problem is that some others VIs (that I am not intending using) are changing those global variables (in the natural data flow of the application).  I could , of course, send the values of those global variables as parameters, but I don't know how should I pass those data types (and their size)... There are some clusters there...
Any help is well appreciated

Answer 1

vulpe wrote:
My goal is to break apart an
entirely LabView created application so I can still use parts of it
(builded as Shared DLLs upon on some VIs) in my new .Net application.
My problem is that some others VIs (that I am not intending using) are
changing those global variables (in the natural data flow of the
application).  I could , of course, send the values of those
global variables as parameters, but I don't know how should I pass
those data types (and their size)... There are some clusters there...
Any help is well appreciated
Your
problem is of course the use of globals. That is almost always a bad
idea and asking for troubles once your application gets bigger.
Avoiding race conditions and undesired influences between different
parts of your application will take up more and more of your
development time as your project grows.
You should look into Functional Globals (LV2 style globals) and shift
registers for data storage and queues for passing information between
different parts of your applciation. Using these techniques
consequently, will require you to spend some more time initially but
will allow you to grow your application without increasing the
complexity of managing such things exponentially.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions