12-05-2025 10:26 AM - edited 12-05-2025 10:45 AM
Hello NI Community,
I am encountering an issue after upgrading my development environment from TestStand 2021 to TestStand 2025 Q3.
I have an existing sequence that uses an Action step with the .NET Adapter to call a method within a .NET framework component. This step ran without issue in TestStand 2021. Upon running the same sequence in TestStand 2025 Q3, the step now fails with the following error:
Error Message: Exception has been thrown by the target of an invocation. Could not load file or assembly 'normidna.nlp'. The module cannot be loaded because only single file assemblies are supported. (0x8013101E)
I have attached two screenshots of the Action step settings:
One from the working TestStand 2021 sequence.
One from the failing TestStand 2025 Q3 sequence.
These screenshots confirm that the configured .NET assembly, class, method, and target framework version are identical in both environments.
My primary concern is finding a scalable solution for migration. As our test systems contains potentially hundreds of steps using similar legacy components, manually replacing or rewriting every affected step is not practical.
What is the root cause of this issue? and What is a practical way to solve it? Hopefully there is a simple setting that can be applied globally for backward compatability!.
Thank you
Solved! Go to Solution.
12-07-2025 11:18 PM
TS2025 is no longer supporting .net framework ...