Hi G_L_I,
TestStand is currently in the process of moving from using .NET framework to .NET Core in different parts of the application. As part of this change, in TS 2024 Q4, we have moved the .NET adapter to support executing .NET 8 code modules. The adapter can still load and execute any assemblies targeted to .NET Framework provided:
1. The code in the assembly or it's dependencies don't use .NET APIs that have been deprecated or changed in .NET Core. Basically the .NET 8 CLR should be able execute the code module without errors.
2. The way .NET Core locates and loads dependencies has changed. It no longer supports finding and loading assemblies from the GAC.
The issue you hit is because of #2. I tested with the NI-DAQ example you have mentioned and the reason the assembly doesn't load is because it has a dependency on NiLMClientDLL.dll which is only present in the GAC. The .NET 8 runtime can't locate this assembly and hence the error.
As a workaround i tried copying said dll next to NationalInstruments.Common.dll and then it loaded fine in TestStand, without having to re-target the code to .NET 8. Moving ahead, you will want to consider building your .NET code modules targeted to .NET Core so that their dependencies are pulled in correctly and the .NET CLR can locate them (in the simplest case, the top level assembly and it's dependencies are located in the same folder).
Let me know if this helps.
Regards,
Tinu