I just recently updated to the latest DQMH version, and that had me use the validation option. It worked surprisingly well, and that got me thinking if it might be possible to use that feature for my custom Modules. My idea is to just have modules that I integrate into multiple different softwares, all created from the same source (a modul template). And once I make a change to the template that I want to implement everywhere (bug fixes and other improvements), I would like to do that the simplest way possible. So is the validiation tool a possible and/or good use for that, or am I simply better off to go to every software and load in the changed Template and make the necessary changes? If any of you has other ideas to implement something along those lines, please share your input. I would love to hear alternative approaches, to essentially create some sort of standard.Thank you for your input ^^

DQMH Consortium Toolkits Discussions

Can DQMH validation be used to update my custom modules?

This is an older presentation where I talked about different ways to manage your reusable code. In the link below I discuss submodules in Git, VIPM packages, and PPLs. As Darren, my preferred method is VIPM packages.

https://dqmh.org/how-to-organize-your-large-labview-project-using-libraries/

Thanks for your trust in DQMH, it is nice to see people using DQMH to standardize their LabVIEW software.

Happy wiring,

Fab

For an opportunity to learn from experienced developers / entrepeneurs (Steve, Joerg, and Brian amongst them):
Check out DSH Pragmatic Software Development Workshop!

DQMH Lead Architect * DQMH Trusted Advisor * Certified LabVIEW Architect * Certified LabVIEW Embedded Developer * Certified Professional Instructor * LabVIEW Champion * Code Janitor

Have you been nice to future you?