Conflicting library versions when deploying a VI to a PXI target

[raphschru]

Hi fellow developers,

Using LabVIEW 2025 Q3 (64-bit) with the RT Module.

When running/deploying my VI to my PXI target, I systematically get conflict dialogs about libraries on the target not matching their version in the project:

It seems the conflicting items all are NI libraries:
XDNodeRunTimeDep.lvlib
NI_FileType.lvlib
LabVIEWSMTPClient.lvlib
NI_MAPro.lvlib
NI_LVConfig.lvlib
NI_Data Type.lvlib
NI_PackedLibraryUtility.lvlib
NI_SystemLogging.lvlib
NI_Gmath.lvlib
NI_Matrix.lvlib

Questions:
1. Why does it happen on NI libraries? I obviously did not modify them, whereas my own libraries/classes are frequently modified and they do not seem to have this issue.

2. Why does it cause a conflict? Can't LabVIEW always overwrite the version on the target with the one from the project? Nothing is running on the target except my VI.

According to this discussion:

https://forums.ni.com/t5/LabVIEW/The-version-of-this-library-downloaded-on-the-target-does-not/td-p/...

I could just hit "Apply" and not bother, but it happens systematically.

Any idea of what is happening?

Crosspost on the #rt Discord.

Regards,

Raphaël.

[joerg.hampel]

Could it possibly be related to this deployment issue about unclear error messages?

[raphschru]

Hi Joerg,

That may be it, I frequently run my VIs on "My Computer" first for testing, then on the actual PXI target. I also have some VI Scripting code in "My Computer" that may reference or generate part of the RT code.

I know the workaround of using only one target per project, but I feel this is just too restrictive!

LabVIEW allows to create multi-target projects, which is really convenient for testing the code, so I expect to be able to use this possibility.

I wonder how such a big issue is still unresolved?

How can I test my RT code on the PC? I am not talking about unit tests, just executing the RT code on the PC to partly debug it.

Having 2 projects side by side feels silly...

Regards,

Raphaël.