Project Dependency Conflicts Detected

[Terry_S]

Every vi in every project I open shows a dependency conflict (see attached).  However if I click the close button the vi opens, the project tree drops open, shows the conflict in the tree and then disappears.  I can go to the project menu and the resolve conflicts is grayed out.

Anyone have any idea how to resolve this?

Thanks in advance

Terry

[jjohn1]

It looks like you have a local copy of one of the LabVIEW analysis libraries.  It is normally found under the LabVIEW vi.lib folders.

You might try moving the folder containing the conflicting VIs somewhere else where LabVIEW cannot find it.  I suspect LabVIEW will then find the original libraries in vi.lib when you load your project.

[Darren]

Judging from your screenshot, it looks like you have a copy of one of the core LabVIEW libraries (NI_AALBase.lvlib) in your project folder. This is a vi.lib file that you shouldn't have your own copy of. Did you maybe create a Source Distribution and select the option to include all vi.lib files as well?

To get rid of the conflicts, you'll need to look in your code (I'd start with that Distribution folder) and remove any copies of vi.lib code that you have.

[Terry_S]

I have removed all the distribution folders and renamed the main project folder that is show in the confict message.  The message still keeps showing when opening a vi and the location is still showing the location that nolonger exists.  At this point I have saved the vi and closed it.  I also saved the project and closed it.  I closed Labview and re-opened it.  Opened the project and then opened the vi.  The message still appears.

[jjohn1]

You might try opening the VI without the project and manually selecting the required VIs from vi.lib.

[Darren]

You can also expand Dependencies in the project, which should list the conflicting/missing library. You can then right-click the item and choose Find > Callers, which will tell you which project items are causing it to appear in Dependencies. You can open those VIs, make sure they're pointing to the correct library, and re-save them. Repeat this process until the conflicting/missing library disappears from Dependencies.

[Terry_S]

I have tried opening the vi outside of the project there are no confict message.  When I view the heirarchy of the vi's everthing appears to be loading from the Labview folders.

Also there are no conficts present in the project when opeing from the project.