NI TestStand
DotNet Dependency Not Found in Packed Library
Solved!
I'm calling a VI inside a packed library from within a sequence. When view the VI w/in the sequence, I get a failure to load error (below).
For some reason, TestStand's develop environment won't load the VI.
So, here's the confusing part. The packed library and VI are fine. I can use it in a LabVIEW application and it'll be fine.
In my primary application, I embed an instance of TestStand in LabVIEW. When the sequence is called from the compiled LabVIEW application, it runs the VI fine.
So, I end up in c:\user\[username\appdata\temp\TestStand and look at the log (attached).
I'm getting pages upon pages of "VI_Broken" messages (of course when I open the packed libraries, they are fine).
{
mode: "VI_BROKEN";
callSite: "CheckVIRefsForMissingDependencies";
timestamp: "2026-01-27T08:26:37.789795";
vi: { name: "Utilities (single VIs).lvlibp:Screen Copy via Dot Net.vi"; path: "C:\repos\TED\Software\FATS\Builds\Libraries\FATS Classes and Libraries\Utilities (single VIs).lvlibp\Utilities\Screen Copy via Dot Net.vi";}
callchain: [];
callers: [];
dependencyIdent: { name: "System.Drawing:4.0.0.0:neutral:b03f5f7f11d50a3a"; path: "System.Drawing";};
}
To me, all the dependencies I see in "dependencyIdent:" are dotNet calls (which I do quite a few dot net calls). Seeing things like System.Drawing, System.Data, System.Windows.Forms. I should be on dotNet 4..
It is almost as if, when run from the LabVIEW executable, my application instance finds dotnet fine and TestStand inherits that config, but when loading it in the TestStand editor, TestStand can't find dotnet. Am I on the right track?
I played around with my search directories, (but think i'm just chasing rabbits out of desperation).
I don't really have anything exotic in my adaptor settings (just that I don't want to use the Development System Engine because this will ultimately go on a system w/o one).
I'm running 2025Q3 on each.
TestStand:
LabVIEW
I guess in someways, it don't matter. The application runs, and this is ultimately a development environment issue I'm having. But I'd like to fix it (and it worked fine on my old computer), and it's starting to be an interesting problem. I get the feeling I'm either missing something simple/stupid or I'm about to learn about how something works under the hood.
Any ideas?
Thanks!
-josh
@joshua.l.guthrie2.civ wrote:
[...]
I guess in someways, it don't matter. The application runs, and this is ultimately a development environment issue I'm having. But I'd like to fix it (and it worked fine on my old computer), and it's starting to be an interesting problem. I get the feeling I'm either missing something simple/stupid or I'm about to learn about how something works under the hood.
Any ideas?
Thanks!
-josh
Intresting problem indeed! Are you saying that the exact same configuration (LabVIEW TestStand Version, Code Version) worked on the old computer?
@Parker123456789 wrote:
2024 still supported ".NET Framework". TestStand 2025 only supports .NET 8.
This gets a little fuzzy with your usage of dependency from LabVIEW. what version of LabVIEW are you using now. Is the LabVIEW adapter using LV Development or Runtime?
As I understand it..
When using runtime, then the .net version of the dll needs to match TS.
When using development, then you might be able to use .NET Framework. but you'll need to ensure the LabVIEW.ini has .net framework still enabled.
All in all, if you ensure that the dotnet dependency is build with/for .NET 8, then that should solve it. Depending on what it is, the migration could end up being a bit of an adventure..
Sorry for the delay getting back. Just dug out of our Snow'a'cane. This looks like this will end up being the issue. All my dotNet calls are 4.0. I started my application development in LabVIEW 2023. Right now, I'm on 2025Q3
Note, I'm not using the development engine at all for either LabVIEW or TestStand. All my debugging is on the compiled version.
Sounds like I may need to bite the bullet and replace my 4.0 calls with dotNet8 calls. Am I reading between the lines of what you're saying correctly?
