Read version number of the DQMH VI package programmatically?

[joerg.hampel]

I think the subject says it all:

Is there a way to determine the version number of a VI package (here: the Delacor QMH) - as it would appear in VI Package Manager - programmatically from my LabVIEW application?

So we're using 3.1.0.18 at the moment, and I would like that to show up in different places (GUI, readme, ...).

[FabiolaDelaCueva · Accepted solution]

Hi Joerg,

All of the DQMH VIs get the following text at the end of their VI Description:

"Based on Delacor QMH Project Template" followed by the DQMH version.

You could get the version information by using the VI Description property node and then some regular expression code.

I created the following quick and dirty code and put it in the DQMH Module.lvlib:Module Name--constant.vi just as an example:

Save the image above on your code and you should be able to drag the snippet into any DQMH generated VI and have it report the version.

This would of course only give you the version used to create the package not the current version currently installed. 

Regards,

Fab

[joerg.hampel]

We already do that very same thing with some of our own library VIs. Perfect, that's all I need.

Thanks, Fab!

[Taggart]

Old question, I know. But I have a variation, how can I programmatically determine what version of DQMH is installed? Do I have to query the VIPM API somehow or is there another way?

[drjdpowell]

VIPM keeps copies of installed packages in folders (named by LabVIEW version) somewhere under the Program Data folder.  If you have a look you will find it.  

I've used this in a pre-build vi that records all installed packages in the EXE's build log.  

[Taggart]

I figured out how to pull it out of the VIPM API - although that requires a license. 

Digging through the files might be more widely applicable.

[Taggart]

---

@Taggart wrote:

I figured out how to pull it out of the VIPM API - although that requires a license. 

Digging through the files might be more widely applicable.

---

And might be more performant as well.

[joerg.hampel]

For DQMH, I posted a related feature request long ago:  https://forums.ni.com/t5/Delacor-Toolkits-Documents/DQMH-Feature-Requests/tac-p/3808494/highlight/tr...