Excluding instr.lib folder from Project.Save For Previous routine

[NikitaProrekhin]

Hi,

I would like to automate downgrading process for few LabVIEW projects from LV17 to LV14. I use Project.Save for Previous method and it works fine for simple projects. It ignores everything that lives in vi.lib (KB).

I have a project that refers to toolkits located in instr.lib (Agilent PSU, NI-DMM, NI-DCPower). Saving this project for previous version converts toolkits from instr.lib  and stores them to my destination folder as part of a process. Agilent driver and  niModInst (part of NI-DCPower and NI-DMM) are converted, while NI-DCPower and NI-DMM are untouched and not copied.

This process greatly changes my destination folder hierarchy and alters references to these VIs in my destination converted project.

I don't want to save these external toolkits for previous version, because I already have them in a different LV version installed. They are toolkits  and not project specific files.

Have you ever tried to setup Save for Previous function so it really ignores instr.lib? Or maybe, is there a way to setup third-party toolkits in instr.lib so they act like NI-DMM and NI-DCPower? Like "I don't support saving for previous, please be kind and install me for a different LV version by yourself"? 

Thanks,

Nikita.

[SEgeler]

Hi Nikita,

ignoring additional folders for "Save for Previous" (as it is done with vi.lib) is under evaluation at NI, but there is nothing I could promise. NI toolkits are excluded from the "Save for Previous" list because we create them using a special flag which we did not create a public API for yet. See my sentence above, please. Under evaluation.

Sorry if I add to your :frusty: level.

Greetings

Stefan

[NikitaProrekhin]

Hi Stefan,

That is good to hear that this functionality is under evaluation. Without having this available, it is really hard to automate downgrading processes for LV projects.

My colleagues and  I would like to use LV2017 for development. But we can't. We need to support LV2014. So we are "married" to LV 2014 for the nearest future and can't really enjoy responsiveness of LV2017.

If only we were able to exclude few dependencies during Project.Save For Previous... :dreamy:...

[SFK]

Hello everyone,

I have had the same troubles in the past, especially with the annoying side-effect that saving back a project creates wild relative paths under the target directory for resembling the orignial instr.lib path to the original LV version.

So I am positively surprised as I have just learned from an NI Germany AE that this behavious is nowadays conceived as a bug (Bug Number 1343500) and that the behaviour of LabVIEW will be changed in LabVIEW 2021...

Best regards,

Sebastian