Hi All,

I have developed a* un-managed BA* for the BURN. For handling Powe-Off
scenarios, I am checking for "*BOOTSTRAPPER_RESUME_TYPE_INTERRUPTED*" in the
"*pCommand->resumeType*" structure and if found, I am giving complete
control to BURN engine by calling detect, plan and apply with default action
that I have received from engine.

This scenario works in normal installation and after REBOOT, BURN does
resume the installation where it has left it before power off.

But, during UPGRADE scenarios, I powered off the machine (by disconnecting
power from main switch) while installing NEW BURN package over the OLD
(already installed) BURN package. When I powered on the machine, I was
expecting that NEW BURN package installation will launch. But, instead, BURN
launched OLD BURN package for the installation !!

Can anyone please help me to understand, how BURN manages POWER OFF
scenarios and what I am doing wrong, which is making BURN to launch OLD
package ?

*NOTE : POWER-OFF = Disconnecting the power from main switch*

Thank you in advance !!! Waiting for your answer/s.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/BURN-launches-OLD-installation-when-Power-off-during-UPGRADE-tp7591047.html
Sent from the wix-users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to