.NET-Error when invoke "tiepie_hw_init" from TIEPIE_HW_API

[CDietz]

Hi,

I'm using the follow software products:

• NI LabVIEW 2025 Q3 (64-bit)
• TiePie WinUSB driver 10.0.2 Windows 10 / 11, 64 bit (https://www.tiepie.com/en/download)
• TiePie .NET framework package "TiePie.Hardware" 1.4.0 (https://www.nuget.org/packages/TiePie.Hardware)

When I try to initialize the API with invoke node "tiepie_hw_init", I receive the follow .NET error:

"Invoke Node
Exception has been thrown by the target of an invocation.
The type initializer for 'TiePie.Hardware.API' threw an exception.
Stack Trace:
at TiePie.Hardware.API.tiepie_hw_init()
at InvokeStub_API.tiepie_hw_init(Object, Object, IntPtr*)
at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)
in TiePie.Hardware_DotNet_Init&Close.vi"

Details are shown in the attachment. Has anybody a tip, what's the reason of this? Thank you in advance

Christian

[Quiztus2]

since tiepie_hw_init is black you should click on it. Then choose from the method list appropriately.

[CDietz]

The method was selected correctly (see attachment). The method in the Invoke node was also executed, but returned the described error.

[Quiztus2]

The comment in your code does mention .net framework, not code. Are you sure your dll is .net core?

If both are available choose freamwork, since core support is not good.

[CDietz]

Thank you for response. "Select Class >> .NET Core" is the only way to load the "TiePie.Hardware" assembly.

I tried to load the "TiePie.Hardware" assembly via "Select Class >> .NET Framework", but it returnes an unspecified error (see attachment).

[Quiztus2]

according to

https://www.nuget.org/packages/TiePie.Hardware#readme-body-tab

there is a .net 5 framework version of the lib. Either download it from nuget via e.g. visual studio and locate where nuget has put those or ask the manufacturer to send you appropriate files.

[Quiztus2]

I realized .NET version naming is not easy to understand. I am not sure if a tiepie .Net Framework version exists. If not you have to wait for proper core support in labview. I guess this takes at least 2 more years from now.