Maciej,
After looking at the TestExec.ini file that your colleague emailed us, we've found that the reason he was running into this problem on his machine is because the Reserve Loaded VIs for Execution option located in the LabVIEW Adapter Configuration dialog was un-checked.
As the help for the Reserve Loaded VIs for Execution option states:
"When a VI is reserved for execution, any references the VI creates during
execution remain valid until the VI is unreserved."
Because this option was un-checked on your colleagues machine, the .NET references were becoming invalid. This option is checked by default and stored in the TestExec.ini file which is why re-creating the TestExec.ini file corrected the behavior.
Hope this helps explain the behavior.
Message Edited by Manooch_H on 10-29-2009 11:33 AM
Manooch H.
National Instruments
