Can we have the old installer back?

[laager]

Running 4.4.1. When doing updates, the new installer isn't as simple as the previous installer. One could simply run the update and FlashFXP would automatically restart and be ready for use. This made for a quick and painless update process.

The new installer just isn't as convenient.

[X3]

I have noticed that only the last installer for build 2003 did that, as in refused to kill the runing process, though it did restart ffxp, all previous behaved just the same as old installer use to.

Can you goto about box, details tab and click copy to clipboard and paste that info here.

Cross your fingers this will be looked at.

[laager]

FlashFXP version: 4.4.1 (build 2003)
Operating System: Windows 7 x64 Service Pack 1
Installation type: All User - Common data folder

Program folder [Access: Read / Write]
C:\Program Files (x86)\FlashFXP 4\

Data folder [Access: Read / Write]
C:\ProgramData\FlashFXP\4\

Temp folder [Access: Read / Write]
C:\Users\XXXXXX~1\AppData\Local\Temp\

[bigstar]

There is a problem yes, but the problem is not with the new installer.

The problem appears to be with the code that launches the update installer and closes FlashFXP, I have made some changes to address this issue for the next build however since this problem is within FlashFXP you will not be able to see the fix until after you update from the fixed build.

I was not aware of this issue until you reported it, thank you for letting us know.

[X3]

Up to build 2000 I never noticed anything its worked flawlessly, closing and updating etc.

But yes, it seems it is failing to close ffxp at least for me.

[bigstar]

I believe the problem was introduced in build 1999 or 2000.

[X3]

Ok build 2004 to 2005 live-update had this problem still.

[bigstar]

okay thanks for the heads up, I must of missed something else, I will dig deeper into this issue and see what I can find.

[laager]

Previously the last user interaction on an update was this:



ffxp was closed, updated and restarted.

Now, it fails to close ffxp:



..and even after that requires further interaction:



Exactly the same problem on 2004 to 2005.

[bigstar]

I have done several tests and I have concluded that there were 3 issues.

* The first issue was fixed in build 2000 where if the shellexecute command that launches the installer with elevation failed with an ERROR_CANCELLED (user said no to the elevation prompt, or didn't have the admin password) it would try to launch the installer without elevation. My intent was to prevent closing FlashFXP if the user canceled.

* The second issue was caused by a mistake in my code where I failed to properly initialize the result value, depending on the specific flow it was possible for the result to remain undefined and this prevented FlashFXP from closing and this was fixed in build 2003.

* The third issue is a rat race, the installer performs a check to detect FlashFXP running before FlashFXP is able to exit.

I added a delay to the check within InstallAware calling the sleep() API, however I forgot that when you call an API in InstallAware all API calls are executed in a secondary thread and as far as I could tell had little or no effect. Since the detection routine is done via a custom DLL that I wrote to handle the detection I have taken the steps within the DLL to perform the detection and if true, wait a second and try again, this should give enough time to prevent the check from triggering during an auto update. (will be added to build 2006)

If any dialog is shown during a silent auto update then any of the remaining dialogs are also shown (installation progress, installation finished) and because they are shown the behavior of the auto update also changes and the option to launch FlashFXP becomes unchecked and the installer doesn't automatically close.

I will release this new build shortly.

[X3]

Thanks, its odd it just decided to break, I though these things were do it once and forget, though clearly I have no idea what Im talking about... hehe

[X3]

v4 Build 2005 to 2007 liveupdate was back to normal "smoothness" already.

[X3]

This seems fixed, I have now gone past two updates where everything is smooth as butter. builds 2005 to 2007 and builds 2007 to 2009.

Pending feedback from OP this should be marked as resolved.