AndyC
Posts: 11
Joined: Sat Jan 06, 2007 12:51 am

Couple of bugs (features)

I use signcode to digitally sign an exectuable using an .spc and .pvk file.
This is password protected, but the checkbox for "Digital signature has password" is grayed out. It requires manually typing in the password on every build.

I have two applications that actively run, a main executable and system tray app. I use the Auto Update to check for new updates from within the main program.
If a new release is detected, the updater downloads and installs the new version (not a patch), and identifies the main program as running and let's the user automatically shut it down for the update. However, the system tray app is not identified until later, and a different dialog appears showing the [pid] of the sys tray app requiring the user to manually close.
Essentially, the installer only seems to be able to automatically shut down one app in the package. If you install a new build from the desktop with only the sys tray app running, it will automatically close it as expected.

Thanks.
gigi
Posts: 2103
Joined: Tue Apr 11, 2006 9:55 am
Contact: Website

Hi,

The checkbox "The digital certificate has password" is disabled because the SignCode tool is used to sign the files. This tool will determine if the PVK file is protected by a password and, if so, it will display a dialog in which the password will be entered. Thus, the state of the checkbox is irrelevant in this case.

On the other hand, SignTool receives the password as a command line argument and AI will prompt you for a password if the respective checkbox is selected. Hence, the state of the checkbox is important only when using PFX certificates.

http://www.advancedinstaller.com/user-g ... ature.html

On what OS you encounter this behavior? Windows Vista? Here is a how you can add support for Vista Restart Manager to your application:
http://www.advancedinstaller.com/user-g ... nager.html

Best Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
AndyC
Posts: 11
Joined: Sat Jan 06, 2007 12:51 am

Ok, point one understood.

For the second, the Installer gracefully prompts the user if the application is running (on Vista) and will shut it down. However it does not do that for any other running applications that are part of the same package. I understand the Restart Manager dcumentation, but if the built installer can successfully prompt and shutdown either of these running applications (main app or sys tray), depending on circumstances, is it not an installer problem that it cannot do both?

Thanks.
gigi
Posts: 2103
Joined: Tue Apr 11, 2006 9:55 am
Contact: Website

Hi,

Please tell me if you use AutoCloseApplication feature with AutoUpdater (because AutoCloseApplication from AutoUpdater does not have any connection with "Restart Manager"). "Restart Manager" is fully controlled by Windows Installer. Also please make sure that your package contains the MsiRMfilesInUse dialog.

Note that using the "Restart Manager" your application does all the job. Must call a Windows Vista API function "RegisterApplicationRestart" to register it with "Restart Manager" and also your application must handle the following Windows message: WM_QUERYENDSESSION.

However if your application does not handle those messages then "Restart Manager" try to close your application by sending the WM_COLSE Windows message to your application main frame Window. This second approach is not very strong (the application may not be closed) and will not be restarted automatically.

Best Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com

Return to “Common Problems”