On upgrade previous version custom action running - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

sjblack@gmail.com
Posts: 36
Joined: Mon May 23, 2011 11:50 am

On upgrade previous version custom action running

Hi There,

I have a installer (version 1 say) with a .NET custom action that is set to run on install (and uninstall). If i upgrade the installer (with version 2 say) the unistall custom action of the version 1 is run, followed by the install custom action of version 2 all normal? Then for some reason the Install custom action from version 1 is run again in the "RollbackCleanup. Removing backup files" action. This fails due to the files bound to in the custom action of version 1 already being uninstalled.

I have baked my noodle on this one! Any help would be appreciated.

Thanks

Sj
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: On upgrade previous version custom action running

Hi,

I'm not sure why you are encountering this behavior.

Can you please send us the two .AIP (project files) and a verbose log of the installation so we can investigate them?

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
sjblack@gmail.com
Posts: 36
Joined: Mon May 23, 2011 11:50 am

On upgrade previous version custom action running

Hi There,

Due to our company regulations i can't send the real projects/logs across i can however whip up a couple of test projects though if needed. I have found a work around to the problem which may suggest the root cause for the problem. To fix the problem i have changed the name of the assembly containing the class used by the custom action in the latest version of the software. It looks like the assembly loaded that runs the version 1 uninstall during the upgrade is remaining cached somehow and is being used for the install. i am guessing by renaming the assembly i am forcing whatever wrapper AI has loading the .NET assembly to reload the newer version therefore it is not trying to bind to older versions of referenced assemblies, hope that helps.

Thanks

Sj

Return to “Common Problems”