I am in the process of developing a formal requirements process for our product installs (currently the process is basically hallway conversations and scattered emails).
Part of the requirement framework is that all existing installs will be migrated to MSI technology from our current InstallShield script-based ones, and all new installs will be authored as MSI. What I am looking for is a mechanism that will be able to capture all the potential requirements of any given MSI and present them to, say, a product manager who would be able to "fill in the blanks" accordingly. Then I could author the MSI based on this provided information, confident that all possible functionality of MSI techology was exposed to the person providing the responses. My first thought was to drop Wix.xsd into InfoPath and let it churn out a form based on that, since after all that schema basically captures the entire MSI spec. As you might imagine that got way too unruly--too many low-level data structures and dependencies that would be too time-consuming to prune down to something more managable. Even just a doc of some sort outlining all the high-level capabilities of MSI technology would do. By "high-level" basically I'm speaking about functionality apparent to an end-user: Registry sessings, service control, shortcuts, IIS, etc. I've looked around online but I can't seem to find a magic "MSI does this, this, and this" kind of doc that I am interested in. Any pointers would be greatly appreciated. -Les ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
