Use the WixBundleVersion builtin variable instead?
On Fri, Aug 1, 2014 at 1:41 PM, Hoover, Jacob <jacob.hoo...@greenheck.com>
wrote:
> In the case where a bundle uses SetUpdate to do an update, I’ve seen an
> issue caused by the “automagic” cleanup of the bundle when the updated
> bundle is trying to get its version info from the file on disk. This is
> caused by bundle 1.0 downloading and executing bundle 1.1, but then
> immediately doing cleanup which uses MoveFileEx to move the running bundles
> file on disk to the temp folder. WixStdBA has a method,
> GetBundleFileVersion, which then fails because the file is no longer on
> disk in the expected location.
>
>
>
> I ponder if it’s worth going down the route of using
> FindResource/LoadResource/LockResource/VerQueryValue to get the resource
> information from the currently running process handle instead of having to
> use the file name.
>
>
>
> Thanks,
>
> Jacob
>
>
>
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> WiX-devs mailing list
> WiX-devs@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-devs
>
>
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
