Bundle Self updates for a Per-User bundle...

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Bundle Self updates for a Per-User bundle...

Hoover, Jacob

Think I’ve found a bug… If the Bundle is a per user bundle, and you are running an existing installed bundle in modify mode to request it to self-update, the CEngineForApplication::SetUpdate call passes in the existing bundle identifier into PseudoBundleInitialize.  This has the adverse side effect of during the caching of the new bundle, the update one is downloaded but not moved because it thinks the cache path is the per user bundle path of the existing bundle. (If it was per-machine, the modify call would be running from the machine package cache not the user package cache.)

 

If I pass in a different GUID (hard coded to a const for testing purposes), then the self-updating works as I would have expected it and my unit test passes. Hopefully we can reserve some time during next week’s meeting to discuss this, and the unit testing in general, so I can get a pull request in place.

 

Thanks,

Jacob

 


------------------------------------------------------------------------------

_______________________________________________
WiX-devs mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-devs
Reply | Threaded
Open this post in threaded view
|

Re: Bundle Self updates for a Per-User bundle...

Rob Mensching-7

Was a bug opened tracking this issue (if it is real)?

 

_______________________________________________________________

FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/

 

From: Hoover, Jacob [mailto:[hidden email]]
Sent: Thursday, November 6, 2014 1:38 PM
To: WiX toolset developer mailing list
Subject: [WiX-devs] Bundle Self updates for a Per-User bundle...

 

Think I’ve found a bug… If the Bundle is a per user bundle, and you are running an existing installed bundle in modify mode to request it to self-update, the CEngineForApplication::SetUpdate call passes in the existing bundle identifier into PseudoBundleInitialize.  This has the adverse side effect of during the caching of the new bundle, the update one is downloaded but not moved because it thinks the cache path is the per user bundle path of the existing bundle. (If it was per-machine, the modify call would be running from the machine package cache not the user package cache.)

 

If I pass in a different GUID (hard coded to a const for testing purposes), then the self-updating works as I would have expected it and my unit test passes. Hopefully we can reserve some time during next week’s meeting to discuss this, and the unit testing in general, so I can get a pull request in place.

 

Thanks,

Jacob

 


------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-devs