In short, binding files into the wixpdb was unintended and never should've happened.
The time it started binding files into the wixpdb was actually a mistake. The reason that was started was to including binary columns like those found in the Binary and Icon tables so that differences were available for pyro. But since WixFile - which stores information about all files - had a binary column performance was degreded severally. Builds taking around 7 minutes were now taking almost 40 and it was an unintended change anyway. So that performance bug was removed (files not found into the wixpdb anymore) while maintaining differences in binary columns by referencing source file paths. But the correct way to get what you want, it seems, is just build your MSI initually (light ... -out product.msi). By default a wixpdb file is created from which you can create patches (now including any changes in binary columns, which wasn't working originally). So you get your MSI and a wixpdb for building patches - which contains all the same data as a wixout (it actually is currently just an embedded wixout with future potential for other things, though nothing has been considered or planned). 2009/4/2 Matt Ziegler <[email protected]> > Did the behavior of light change to not automatically bind files into the > wixpdb? If so was this done for the performance of wixpdb generation as > specified in the release notes of 3.0.5120.0? Finally what is the > recommended method to bind files into a wixpdb? > > I use the wixpdb files for generating patches and before I had to create a > wixout file first and then create my msi from that. One of the previous > builds (not sure which one) then started binding the files directly into the > wixpdb so I stopped building the wixout. > > Thanks > > Matt > > > ------------------------------------------------------------------------------ > > _______________________________________________ > WiX-devs mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wix-devs > > -- Heath Stewart Deployment Technologies Team, Microsoft http://blogs.msdn.com/heaths
------------------------------------------------------------------------------
_______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
