Oh, and on the idea of walking the Directory table (missed this before)... we have quite a number of directories that for one reason or another don't line up, and some whose locations are defined at install-time. Part of this is purely the number of installations we have, another is that some of our installations are quite large and install a number of projects that are disparate at source (but are designed to work together at runtime).
We could of course map the root of one of these "wandering directories" to its real location, but it would be a lot of work and error prone. I think the BinderFileManager solution gives us the best fit for now. I may look at producing an analysis application based on DTF later on, because you do have a good point that it'd be nice to be able to verify that file x in the build area is the actual one that ends up in the MSI - we do have other ways of checking this but they're not fool-proof (as this fool has proven on more than one occasion :) ) Thanks again. John 2009/6/23 Brian Rogers <rogers.br...@gmail.com>: > Hey John, > > Off the top of my head I would say take a look at the DTF tools. You could > write a simple managed code app that reads MSI output itself and does the > verfication. After all the Component, Directory and File table should all > line up if you walk them. You would then be able to validate two things, the > files you are putting into the MSI and where they are going to be installed > on the target system. > > Just a thought, > > Brian Rogers > "Intelligence removes complexity." - Me > http://icumove.spaces.live.com > > > On Tue, Jun 23, 2009 at 7:30 AM, John Ludlow <john.ludlow...@gmail.com>wrote: > >> Hey, all >> >> I'm evaluating Wix v3.0 to see if we should adopt it, and run into a >> snag. The problem is that in wix v2 we run light with -v and it >> chucked out a lot of "Cabbing file xxx from yyy" style messages. >> However, in Wix v3 they seem to have disappeared. Looking through >> the code, it seems that no special logging takes place when a file is >> cabbed anymore. >> >> I can understand why they might have been removed - there were a lot >> of them after all. But we actually use those messages - part of our >> validation process uses this to work out what files are /actually/ >> shipped. This process is in its own build and usually runs once a >> week. >> >> What's the best way of getting this information? As far as I can see, >> these are my options: >> >> >> * Parse the .wxs. However this gives me the variable-based path >> for the file, which I then have to do a string-replace on (since it's >> a different build I don't have actual access to the original values). >> In addition, if someone adds a new file path based on a different >> variable it impacts a part of the script that shouldn't affect at all. >> >> >> * If the worst comes to the worst, I can always modify light.exe >> to emit to the console, but it would be nicer if I didn't have to do >> that. >> >> >> Any other ideas? Ideally, if I could run light and have it produce an >> xml file (or just a flat list in a file, or just dump them to STDOUT) >> of all the files that would be included included full, absolute paths, >> that would be perfect. I was half-expecting the wixout switch to do >> this... >> >> Thanks >> >> John >> >> >> ------------------------------------------------------------------------------ >> Are you an open source citizen? Join us for the Open Source Bridge >> conference! >> Portland, OR, June 17-19. Two days of sessions, one day of unconference: >> $250. >> Need another reason to go? 24-hour hacker lounge. Register today! >> >> http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> > ------------------------------------------------------------------------------ > Are you an open source citizen? Join us for the Open Source Bridge conference! > Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. > Need another reason to go? 24-hour hacker lounge. Register today! > http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
