Re: Cant replace the executable for auto upgradation when its executing
Re: Cant replace the executable for auto upgradation when its executing
- Subject: Re: Cant replace the executable for auto upgradation when its executing
- From: Bill Coderre <email@hidden>
- Date: Tue, 17 Aug 2010 13:49:07 -0700
On Aug 17, 2010, at 1:31 PM, Bill Cheeseman wrote:
> On Aug 17, 2010, at 2:39 PM, Bill Coderre wrote:
>> There are two common solutions:
>> 1) If it's an application, present an error to the user. This IS the standard behavior, but is not in Installer.app at this time. I know it sounds lame, but it's really the best choice, because the user might have unsaved changes, etc, etc.
>
> I just got the "Quit Application" preinstall action in PackageMaker 3.0.4 to work (by using the application's bundle identifier; using it's name didn't work, with or without the .app extension). What happens is that, as the installation operation reaches the end, the applications quit (or are killed). So at least PackageMaker can do this much. Are you saying that we shouldn't take advantage of this feature because it's dangerous?
It is safe to rely on this action, assuming the application is safe to kill. If you wrote the app in question, you already know. (And if you're wrong, you can fix it quickly.)
What I was meaning to say, before, is this: "If you don't feel confident in killing the app, it's AOK to put up an error message instead."
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden