01-11-2013 09:49 AM
Ah I see your use-case. I doubt this can be easily fixed by a new API VI though:\, but will probably need changes to the source code behind the provider framework. I will add this to the list of things we investigate for 2014.
01-11-2013 09:58 AM
Sumedha wrote:
Ah I see your use-case. I doubt this can be easily fixed by a new API VI though:\, but will probably need changes to the source code behind the provider framework. I will add this to the list of things we investigate for 2014.
Thank you!
I'm currently refactoring to push more functionality into the VI Server domain, and can report back on how it goes.
01-11-2013 10:32 AM
Another side comment about using VI server in the project provider. You may already know this, but any time you see problems with calling VI Server properties or methods in the provider context, you might have success by opening the reference in the Main Application Instance. This may not work for every property/method if they need to be in the certain context, but it might help and definitely worth looking into as a workaround.
And of course, even if the workaround does work, you should still report the bad properties/methods to us so we can fix them in the provider context.
01-11-2013 12:11 PM
David_L wrote:
Another side comment about using VI server in the project provider. You may already know this, but any time you see problems with calling VI Server properties or methods in the provider context, you might have success by opening the reference in the Main Application Instance.
Great tip -- "liked".