LabVIEW
Project Expects nonexistant, uncalled VI
Hey Y'all,
I've been struggling with this issue for a little bit now, and have finally decided to do something about it. Every time I load up this specific LabVIEW Project, claims it can't find a specific VI. This VI does not exist at the path, so it would make sense to raise this error, however, it isn't used anywhere in the code. After clicking "Ignore Item" it finished loading correctly and there are no errors in the project. This problem doesn't really stop me from coding, but instead is just a slight annoyance that I'd like to get rid of. After the first time booting it up and clicking Ignore Item, all subsequent loads of the project won't search for the file, however since I use Git, every time I pull new code/switch branches, it pops up again. It also pops up if I clear the Compiled Cache. This VI used to be a property node accessor for a class, but I decided it didn't make sense for that class to have the accessor and moved it to another class. Therefore, there is a VI named Write Encryption.vi that belongs to another class and is in a different spot. Any help would be greatly appreciated. Thanks!
What about diagram disable structures?
You can use the standard LabVIEW search to look for them like so:
You will want to make sure every file in your project is included in your search. This might be mostly done by opening your main VI and choosing to search it and all subVIs, but you would miss any VI in there that isn't a dependency of your main VI, so you might need to add in anything missing manually.
Also, have you tried just opening up your project file in a text editor to see if there's a reference to that path anywhere in it? LVPROJ files are just XML so it's no problem to do in a text editor. You'll probably want to only search the last couple elements of the path since a lot of files are stored via relative paths so you couldn't want to miss it by searching for the complete path.
@EthanHenry wrote:
I'll take a look at the dds, but as for the project file in a text editor, I didn't see the Write Encryption.vi referenced anywhere.
That's very possible. The reference is generally stored in the VI not in the project. You can add them to the project to have another explicit reference in your project view. If you don't do that it will be listed in the Dependencies section automatically as soon as the VI that references it gets loaded. With VIs in Diagram Disable structures or Conditional Disable structures things can sometimes get a little weird as LabVIEW considers them as dependency even though it does not really load them.
And yes the project option to see Why is this VI in Dependencies definitely works for me. I use that quite often when inheriting projects where the previous programmer thought that it is absolutely unnecessary to add any but the top level VIs to the project tree. Together with the option to show unreferenced VIs in the project tree. That is quite handy to find cruft that has accumulated over time during project development.
