VI with DLL-call not executable in TestStand when using Runtime-adapter

[OnlyOne]

Hello,

i am using the latest versions of TestStand and LabVIEW.
In LabVIEW, i created a VI that calls a .NET 4.8 DLL.

Inside this DLL, there's a function that contains a Form which i am displaying using this.ShowDialog.

If I set the TestStand adapter to Development, everything works as expected.

But when I switch the adapter to Runtime, the VI suddenly becomes un-runnable.

If i remove the DLL-call in the VI then the VIs is executable with the Runtime-adaper.
The problem is with the use of the DLL

What can be the problem?

Thanks for help

[Oli_Wachno]

Guess the DLL is not in the GAC?

Path resolution is different in RTE compared to the Development Environment 

[OnlyOne]

What is the path of the GAC?

(I tried to copy the DLL into C:\Windows\System32 and C:\Windows\SysWOW64 with no success.)

Why is it a different path? In Labview i selected the position of the DLL with the Browse-button and thought that is hardcoded after this.

[Oli_Wachno · Accepted solution]

Assemblies have to be installed/ registered in the GAC

https://learn.microsoft.com/de-de/dotnet/framework/app-domains/install-assembly-into-gac

---

@OnlyOne wrote:

Why is it a different path? In Labview i selected the position of the DLL with the Browse-button and thought that is hardcoded after this.

---

Design decisions 😉

where is the DLL located referring to the VI? Is it within the SearchDirectories?

[OnlyOne]

The DLL is in the darechpath in TestStand and Labview.

The DLL is in a subdirectory of the VI.

\mystep\myfile.vi

\mystep\support\myfile.dll

Thx for the tip with the GAC. I come back a soon as i test it.

[Oli_Wachno]

https://www.ni.com/docs/de-DE/bundle/labview/page/loading-net-assemblies.html?srsltid=AfmBOoqvZBs8pB...

might also be of interest