You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which version of Visual Studio are you building with (if any)?
N/A
Which version of .NET are you building with?
4.6.1
If the problem occurs when installing your packages built with WiX, what is the version of Windows the package is running on?
N/A
Describe the problem and the steps to reproduce it.
The problem is that in the public implementation of CloseApplication with TerminateProcess, a process cannot be closed with 0. We have a couple of customers that don't want their processes to return an error if forcibly closed. The processes do not implement Restart Manager and are not Windows services, but they basically treat them like a service.
Describe the behavior you expected and how it differed from the actual behavior.
We want processes to be able to exit with 0. It seems the only issue is the table definition. The corresponding custom action code will work fine with 0 (defaults to it, in fact), but the UtilCompiler only sets the terminate process flag (0x20) if a value is set, which cannot be zero since minValue is 1.
The text was updated successfully, but these errors were encountered:
3.10.2
N/A
4.6.1
N/A
The problem is that in the public implementation of
CloseApplication
withTerminateProcess
, a process cannot be closed with 0. We have a couple of customers that don't want their processes to return an error if forcibly closed. The processes do not implement Restart Manager and are not Windows services, but they basically treat them like a service.We want processes to be able to exit with 0. It seems the only issue is the table definition. The corresponding custom action code will work fine with 0 (defaults to it, in fact), but the
UtilCompiler
only sets the terminate process flag (0x20
) if a value is set, which cannot be zero sinceminValue
is 1.The text was updated successfully, but these errors were encountered: