Comments on: Highlights of WiX v3.0.4116.0 http://www.joyofsetup.com/2008/05/17/highlights-of-wix-v3041160/ Bob Arnson's blog about setup and servicing Fri, 23 Jul 2010 01:04:00 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Bob Arnson http://www.joyofsetup.com/2008/05/17/highlights-of-wix-v3041160/comment-page-1/#comment-5180 Bob Arnson Fri, 23 May 2008 18:59:22 +0000 http://www.joyofsetup.com/2008/05/17/highlights-of-wix-v3041160/#comment-5180 Most MSI packages can be installed by automation using the /qb or /qn switches. But there's definitely more that can be done in tools for test automation. Most MSI packages can be installed by automation using the /qb or /qn switches. But there’s definitely more that can be done in tools for test automation.

]]> By: Will http://www.joyofsetup.com/2008/05/17/highlights-of-wix-v3041160/comment-page-1/#comment-5177 Will Fri, 23 May 2008 17:37:34 +0000 http://www.joyofsetup.com/2008/05/17/highlights-of-wix-v3041160/#comment-5177 Suggestion for a blog topic (sorry, no email addy so I'm leaving it here): Automating install after successful build. I'd like to do this so that my wix install package is run after my QA release build completes each night. That way there's a fresh install ready on the test web server for acceptance testing the next day. Suggestion for a blog topic (sorry, no email addy so I’m leaving it here): Automating install after successful build. I’d like to do this so that my wix install package is run after my QA release build completes each night. That way there’s a fresh install ready on the test web server for acceptance testing the next day.

]]> By: Bob Arnson http://www.joyofsetup.com/2008/05/17/highlights-of-wix-v3041160/comment-page-1/#comment-5109 Bob Arnson Thu, 22 May 2008 16:16:33 +0000 http://www.joyofsetup.com/2008/05/17/highlights-of-wix-v3041160/#comment-5109 You can use the lit tool to combine one or more .wixobj files into a .wixlib and use the -bf switch to bind the files the .wixobj(s) refer to into the .wixlib. That gives you the equivalent of a merge module without all the problems of modularization GUIDs and such. You can use the lit tool to combine one or more .wixobj files into a .wixlib and use the -bf switch to bind the files the .wixobj(s) refer to into the .wixlib. That gives you the equivalent of a merge module without all the problems of modularization GUIDs and such.

]]> By: Jim Stout http://www.joyofsetup.com/2008/05/17/highlights-of-wix-v3041160/comment-page-1/#comment-5107 Jim Stout Thu, 22 May 2008 15:32:04 +0000 http://www.joyofsetup.com/2008/05/17/highlights-of-wix-v3041160/#comment-5107 Hi Bob, This is not really a comment about this post, but more of a general question about a comment you made in another group - which I now cannot find..... Q. Is it possible to generate a wixobj (or other type of file) that is a linkable fragment of a database with files, etc. included? If yes, how? Almost 10 years ago we wrote a system to support distributed development & suites of products that used a homegrown textmsi/msm tool. It depends heavily on msm-based fragments that are kicked out by build systems from multiple teams and consumed by multiple installer build systems (which use IMSMMerege and msidb.exe along with custom tools). We now have over 500 of these fragments that don't meet the strict definition of a WiX MSM but we'd like to move away from our legacy system. We are currently using WiX 3.0 and have been quite successful with it, but it still consumes our 'legacy pseudo-MSMs'. We'd like to used dark or some similar tool to convert them from our sql based archive to WiX XML without converting them to full MSMs (too much work). Any ideas? Thanks in advance, Jim Stout - Attachmate Corp (formerly WRQ, Inc.) Hi Bob,

This is not really a comment about this post, but more of a general question about a comment you made in another group – which I now cannot find…..

Q. Is it possible to generate a wixobj (or other type of file) that is a linkable fragment of a database with files, etc. included? If yes, how?

Almost 10 years ago we wrote a system to support distributed development & suites of products that used a homegrown textmsi/msm tool.

It depends heavily on msm-based fragments that are kicked out by build systems from multiple teams and consumed by multiple installer build systems (which use IMSMMerege and msidb.exe along with custom tools).

We now have over 500 of these fragments that don’t meet the strict definition of a WiX MSM but we’d like to move away from our legacy system.

We are currently using WiX 3.0 and have been quite successful with it, but it still consumes our ‘legacy pseudo-MSMs’.

We’d like to used dark or some similar tool to convert them from our sql based archive to WiX XML without converting them to full MSMs (too much work).

Any ideas?

Thanks in advance,

Jim Stout – Attachmate Corp (formerly WRQ, Inc.)

]]>