I just committed a draft readme to the new icebreaker repo: https://github.com/wixtoolset/icebreaker
It lays out some rough plans and requirements. Interesting ones include: * Tests are required. This is all-new code so there's no excuse not to have them. They won't necessarily be unit tests, though. One of the goals of the project is to replace the ICEs, so we need to validate that the replacements have output comparable to the ICEs. We need to figure out how we might automate that kind of testing. The simplest would be a unit test that ran ICEs and ICE Breaker against a test .msi and asserted the right number of ICE messages and ICE Breaker messages came out the end. * The deliverables are the extension that WiX v4.x can consume and command-line tool(s). At the least we should have an equivalent of WiX v3.x's Smoke.exe. We might also want to deliver a command-line tool (either separate or as a mode of the Smoke replacement) that uses a .wixpdb instead of an .msi. My next step is to build a shell extension and implement a couple of simple ICE replacements. ICE08 and ICE21 are my current picks because they're easy. :) -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk _______________________________________________ WiX-devs mailing list WiX-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-devs
