After closing project file, unable to build installer unless I rebuild executable

[Kenny_K]

I am currently using LabVIEW 20.0.1f1 (32-bit).

I have a project file that seems to "lose" the memory of where the last built EXE is located if I close the project file.

If after I close the project file, I try to open the project file again, and build the installer, I get the following message:

If I right click on the EXE build spec and select "Explore", I get an error that the EXE cannot be found OR if I previously build an application in another project, file explorer will open in the last EXE for the other project (completely different path than the path specified in the build spec).

If I build the EXE (auto version will increment properly), then build the installer (without closing the project), the installer builds correctly with the correct EXE.

I have several other projects that do not exhibit this behavior.   Any idea on why the project file seems to get "lost" when I close out of the project (and back to the getting started page)?

[altenbach]

Very confusing.

• When you close the project file, do you also save it?
• Do you have any post-build actions and what do they do?

[Kenny_K]

The project is saved before closing.   If I didnt click save, I believe that the auto increment version number would be lost as well.

All of my projects have a Post-Build Action.vi in them (for the application build, not the installer build).

Here is the contents of the EXE Post-Build Action

But, if this were to fail, then the build would have failed (I have had that happen when I cant contact our database to upload the new software version).

However, in the issue mentioned in the original post, the Post-Build Action.vi completes as expected, and I get a valid .exe.

The EXE build spec is using the [VersionNumber] tag, and the Installer is using the [ProductVersion] tag, so add the Rev # to the generated folder automatically. We use this on all our build specs, so not sure it matters, but thought I would mention it.

[pauldavey]

This occurs when you use source control. I think the solution is to include the destination folder (auto-update) of your built application into the project.