Freigeben über

WiX: Introducing the WixPdb

  • Artikel

This post has moved here.

Comments

  • Anonymous
    May 25, 2008
    PingBack from http://www.doctordeploy.com/blog/wix/wix-introducing-the-wixpdb.html

  • Anonymous
    July 18, 2008
    So the samples in "Building a Patch using the new Patch Building System - Part 3." should have wixpdb in place of wixout?

  • Anonymous
    July 19, 2008
    Yes. Just updated it.

  • Anonymous
    May 04, 2010
    I have been reading about the latest patching scheme using the wixpdb and would like to incorporate this into our environment but it appears that for this scheme to work you need to build the patch using duplicate pathing as the original build. Is this correct? Our environment allows for each machine to define the enlistment <root> directory(C:enlistment; D:enlistmentsproductA; etc.). Is there any processes in place to account for varying <root> paths?

  • Anonymous
    May 07, 2010
    The comment has been removed

  • Anonymous
    May 13, 2010
    Sorry, I should have provided much more detail. The issue encountered is due to not wanting to rebuild RTM on the same machine building the patch every time we need to ship a patch which appears to be the only way to use the wixpdb files. From additional reading of your other posts, I believe I will have to use the Admin Images route instead of the WixPdb's. Thank you for the great information you have shared over the past years. It is greatly appreciated.

  • Anonymous
    May 14, 2010
    I think you have a great feature request. There are hacky ways to do this but it could definitely be easier. I'll take note of this and see what we can do in the future.

  • Anonymous
    May 14, 2010
    I should note that the hacky way to do this is to do a string replace in the wixpdb to replace the root from the original build machine with the root for the new machine.

  • Anonymous
    February 01, 2011
    Should the wixpdb files be copied into the release folders or should I only see them in the debug folders?