Hello everyone. I have two identical Labview projects, one is practically a copy of the other, I have copied each vi with some small modifications but everything is relatively the same. In both projects I use the same .lvlib which is in the location C:\Program Files (x86)\National Instruments\LabVIEW 2020\vi.lib\xxxxx\yyyy.lvlib. I drag this library directly into my project. This is a Veristand Custom Device project but I think this is not relevant to my problem. When I do the "built" of the configuration release of the project (all the built configuration is also identical in both projects) a library is created in National Instruments\NI VeriStand 2020\Custom Devices\(ProjName)|Windows\ called "ProjName Configuration" . When this file is created, when opening the system explorer initialization vi from this created configuration folder it has the arrow broken while in the project the arrow is not broken. In the original Project this does not happen, I can build and no arrow breaks. The reason for the broken arrow has to do with the library (it marks all the vis that I use from this library): ROOT CAUSE: Dependency is broken. When I enter the I saw that has the broken arrow it says the following: The library specified for this node cannot be found or cannot be loaded. Right-click the Call Library Function node and select Configure, then choose the correct library name or path. This only happens in the new project but not in the original. Does anyone know what I'm doing wrong??? Thank you so much!!

LabVIEW

Problems with .lvlib when creating a project

I'm really not sure of the best way to check this, but as you may know, your LabVIEW Projects (.lvproj files) are actually XML files containing all sorts of meta-data. this includes dependency paths, etc. so it may be part of your problem. I THINK they regenerate if they get erased or corrupted, but I would still back anything up before you touch them.

I would try a file compare tool like you can find online. I use a plugin for the free Notepad++.

Since you are using VeriStand, this could be even more complicated. I am not familiar with that product.

It might be a good idea to post both of your projects here too. There are gurus here that really understand everything going on behind the scenes of LabVIEW Projects. Failing that, you may need to contact NI customer support.

LabVIEW Pro Dev & Measurement Studio Pro (VS Pro) 2019