[Temp] != %TEMP% WHY?

[al_g]

In some recent NIPM update the definition of the temp directory changed. It used to be the same as the Windows temp directory, but now it creates a directory inside of temp AND removes the files after installation. I had a bat file that would copy the files out of the Temp directory and it suddenly stopped working because of this new "feature" and figuring it out with the automatic cleanup added to the challenge. Ugh!

[CL_eisenwr]

What version of NIPM had you been using? [Temp] has had that behavior for several years. You can use %NIPkgMgrTempUnique% in a custom execute to resolve the unique folder path.

[Scott_Richardson]

Alan -

NI Package Manager deprecated documenting "Temp" as an installation target root and created "NIPkgMgrTemp" (%TEMP%\NIPackageManager\) and "NIPkgMgrTempUnique" (%TEMP%\NIPackageManager\<unique value>\) in version 19.5, however, packages built using nipkg.exe still honor the "Temp" and should resolve to NIPkgMgrTemp, the non-unique directory.

FWIW, the NIPM documentation states the following for custom executes:

To run an executable, you must first install the package that includes the executable. You can confi...

So NIPM does not support postall custom executes accessing package installed file in the temp directory. Here is some more information on Behavior of Executables Scheduled as Postall in the help.

Questions:

1. What builder application and version are you using previously when it worked and now when it fails?
2. What version of NIPM is installed when the package is installed, both previously and now?

Not sure if related, I do know that NI Package Builder 20.6 changed its behavior when resolving resolving the "[Temp]" alias for custom executes from NIPkgMgrTemp to NIPkgMgrTempUnique due to Bug 941042.