Allow us to change the "Upgrade Code" in an installer

[crelf]

I remember this in previous (pre-8.2) versions of LabVIEW - not sure why it was removed.  I have a use case to use projects as templates (like when someone wants to write a plugin for a utility I've written, I want to be able to send them a zip containing a project, methods, etc).  The project includes installer settings (so their files go into the right place under my util's plugins folder, but when they build and try to install their plugin, they get an error if another plugin bult using the same template has already been installed.  This is because the "Upgrade Code" (stored in the lvproj file) is the same (it tells Windows that the two products are the same, so subsequent installs are seen as upgrades or replacements, not new installs.

My memory tells me that I used to be able to hit a "Generate" button somewhere which would give me build a new code - all I'm asking for is that back (I can add a step in my work instruction to hit that button before you build).

I don't currently have a workaround for this (other than having engineers manually edit the lvproj file) - if anyone has a better idea, I'd love to hear it for the interim!

[TCPlomp]

Your memory is right, but it was in LabVIEW 7 and earlier.

[Mads]

If you duplicate the build (right-click on it in the project and select duplicate) and use the new one it will have a new code.

[crelf]

Thanks Mads - but that's still pretty awful.  I'd prefer my engineers not to have to duplicate a build, then delete the original build, especially as this is a project template.  That said, if it's the only way I can do it at the moment, then it's an acceptable work around I guess.

[altenbach]

If you look in the "version information" section of the build specification in LabVIEW 2011, there is a field for the "upgrade code" and a [generate] button right next to it.

This idea has been implement already, and should no longer be marked as new.

[crelf]

Indeed.