I created an nipkg file to handle installing an executable and running some custom pre/post-install actions (i'm registering it as a service via nssm). Any time I install or uninstall the package, it prompts to reboot. Nothing about what I am doing should require a reboot. Is there something I can do to convince NI Package Manager that a reboot is not necessary?
Extra wrinkle: the main point of using an NI Package at all is that our company also leverages Systemlink for remote systems management. I created a package so I could easily deploy it out to remote systems. But I don't want to force those remote systems to reboot any time I want to update this package. So whatever solution would also need to work in the context of remote installation via the Systemlink Client.
The systemlink web UI gave me the option to deselect "reboot if necessary", but that apparently is not sufficient. It prevents the reboot, but it doesn't actually fully install the package. In my case, my package should just copy an exe into Program Files and then run a post-install.bat script; but when it runs the install, the executable file is given some arbitrary GUID name. (I believe this is relying on the Windows PendingFileRenameOperations registry key; on reboot, the file will be renamed back to the original exe name....but again, I don't want to have to do that!)
Is it possible to prevent reboot (and also the PendingFileRenameOperations stuff) on package install/uninstall? Is there some setting in the package build specification itself that I should be setting?
