11-16-2006 08:51 PM
11-17-2006 07:43 AM
11-17-2006 04:40 PM - edited 11-17-2006 04:40 PM
Message Edited by Jon M on 11-17-2006 04:41 PM
Message Edited by Jon M on 11-17-2006 04:41 PM
11-20-2006 12:39 PM
04-29-2008 01:13 PM
Has anything changed in TestStand since this posting? I am storing a .Net reference in a Station Global variable of type "Reference" using the .Net adaptor. If the DotNET adaptor is able to store a reference in a Station Global, it must be possible to also store a .Net reference from a custom operator interface using the TestStand API? Or, is the adaptor using a private API that is not available to us mere mortals? 🙂
I am successful at storing a .Net reference from one sequence, so that other sequences can make method calls later on that same object later on in the lifecycle of my application. That all works just fine....
The problem is that I am creating the .Net object from within a startup sequence, and it takes a fair amount of time for the sequence to load, execute, then instantiate the object. If I could instantiate the object from within my custom operator interface at initial startup, then save the reference to the object in the Station Globals, my sequences that execute later can use the object.... Am I being perfectly obtuse?
04-29-2008 03:10 PM
04-29-2008 05:36 PM
02-23-2018 11:06 AM
Were you able to get to a resolution on this?
02-26-2018 07:57 AM
What exactly are you trying to do? Some things have changed over the years. For example, newer versions of TestStand and LabVIEW do support passing .NET objects between TestStand and LabVIEW (as long as they are serializable or derived from MarshalByRefObject).
-Doug
02-26-2018 08:05 AM
I'm looking to run an initialization sequence execution which would initialize .NET objects and store them into station globals. However, once that initialization sequence execution is done then the objects are gone. I would be interested in storing them in my UI (though not the best design pattern) so at execution of the next flow I can populate those back without having to go through the initialization again.