Teststand--> labview and .net

[caspar]

Hi,

i've got a problem when calling, from teststand, a Labview Vi which has a .net interface as part of its diagram.

*The Vi runs with no problems when it is run directly from the labview environment,

but when the same VI is called via Teststand

[Minh Pham]

QUOTE (caspar @ Nov 25 2008, 07:56 AM)

Hi,

i've got a problem when calling, from teststand, a Labview Vi which has a .net interface as part of its diagram.

*The Vi runs with no problems when it is run directly from the labview environment,

but when the same VI is called via Teststand

It could be number 3 in this known issues list:

http://digital.ni.com/public.nsf/allkb/FDC...62573D90058DD1F

otherwise, Seems like a conflict in Application Domains, please have a look at this. Hope this helps

http://zone.ni.com/devzone/cda/epd/p/id/6064

[caspar]

QUOTE (Minh Pham @ Nov 24 2008, 11:31 PM)

It could be number 3 in this known issues list:

http://digital.ni.com/public.nsf/allkb/FDC...62573D90058DD1F

otherwise, Seems like a conflict in Application Domains, please have a look at this. Hope this helps

http://zone.ni.com/devzone/cda/epd/p/id/6064

Thanks for that, i'm actually using 8.6, does the same issue exist with the location of dependancies ?

i've looked at the issues with the Appdomains, and i understand the rational hear, but i am just creating my .net references in labview,

so am i right in thinnking i shount get an issue with this??

[Rolf Kalbermatter]

QUOTE (caspar @ Nov 25 2008, 05:11 AM)

Thanks for that, i'm actually using 8.6, does the same issue exist with the location of dependancies ?

Quite likely. This behaviour in 8.5 was not a bug that got introduced but instead a change to the behaviour to make the .Net Interface in LabVIEW behave the way Microsoft meant .Net to be used. In earlier versions LabVIEW tried to be smart and locate dependant .Net components itself but I'm sure that opened a whole can of worms that was remedied by simply relying on the .Net behaviour itself.

Rolf Kalbermatter