Jonathon Green 12 years ago • updated by Michael Aivaliotis (VIPM Product Manager) 10 years ago • 2 • 1 duplicate
There are times where I want to update code to be distributed e.g. iterate over it and do some custom changes, but I don't want these changes to persist in the source code e.g. update version/build information of a tool, add reuse VIs to a LabVIEW Project Library and mark private etc...
When using OGPB this is doable because of two reasons:
- There is a API available (see VIPM idea here)
- I have access to the distributed location of the code before it is packaged
This would allow me to make these changes (in a well known folder hierarchy - another plus) without having to unpackage the package and go in with a post-build hook.
Customer support service by UserEcho