Problem explained.
There's some kind of caching of assemblies that happens - probably
unintentional. I had changed the declaration of the object but never
restarted VEE. It's important to note that I did "unload" the object (or so
I thought) by unchecking it in the .NET references dialog. Otherwise
replacing the dll is impossible. This wasn't good enough. VEE had to be
restarted.
-SHAWN-
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
There's some kind of caching of assemblies that happens - probably
unintentional. I had changed the declaration of the object but never
restarted VEE. It's important to note that I did "unload" the object (or so
I thought) by unchecking it in the .NET references dialog. Otherwise
replacing the dll is impossible. This wasn't good enough. VEE had to be
restarted.
-SHAWN-
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".