> Were you using Components containing single files as generated by heat.exe? Many of the components only contain a single file but others have multiple files per component (mostly for ASP.NET projects that contain a lot of files). Note that I only have to support major upgrades so having multiple files in a component isn’t a big deal for me but might be for you.
> Can you explain how you modified your File Id's to streamline the > sequencing? I used a common prefix for each library combined with the directory id and then a number at the end. This way when WiX sequences the files this would ensure that every file in my library is installed sequentially for every directory. Here’s what a few of my id’s look like (the first 4 go to one directory the next four go to a different one: webserver.webserver00000.0000 webserver.webserver00000.0001 webserver.webserver00000.0002 webserver.webserver00000.0003 webserver.webserver00001.0000 webserver.webserver00001.0001 webserver.webserver00001.0002 > What's the average size of your installer when built & what's the size of > the files when >installed? Currently I have one external cab file which is around 265 MB (default WiX compression settings), the MSI itself is around 10 MB. -- View this message in context: http://n2.nabble.com/Performance-Issues-with-File-table-sequencing-tp4777168p4780390.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
