Re: [WiX-users] Msi inside msi ?
This is very common. Fragments solve a great many of the frustrations you're likely to hit with Merge Modules... in case you need any extra ammo. wink/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Collins, James Sent: Wednesday, July 25, 2007 12:09 PM To: Mike Dimmick; Bob Arnson; Jeroen Davelaar Cc: WiX-users@lists.sourceforge.net Subject: Re: [WiX-users] Msi inside msi ? Thanks mike, Yes I would agree fragments offer much more and I will keep that in mind moving forward. For me however I need a migration path from Wise to WIX and that's going to be merge modules for now. Once I have convinced my team WIX is the way to go (and believe me I'm trying very hard), and we are fully WIX then this approach makes much more sense. WIX by stealth! :) Jimbo -Original Message- From: Mike Dimmick [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 25, 2007 12:02 PM To: Collins, James; 'Bob Arnson'; 'Jeroen Davelaar' Cc: WiX-users@lists.sourceforge.net Subject: RE: [WiX-users] Msi inside msi ? WiX was designed to support very large installer projects, with a design goal of distributed setup authoring. To support this idea, WiX supports Fragments. A Fragment is just a section of setup authoring. Loosely, candle compiles source files containing one or more Fragments into .wixobj files, and light links one or more .wixobj files into a final installer/merge module/patch. One, and only one, of the sections of an installation must be a Product, PatchCreation, or Module. candle and light are very much modelled after a C/C++ Compiler and Linker respectively. It took me a while to work out that the first letter of each tool's name indicates its purpose (Candle = compiler, Light = linker, Lit = library tool, Dark = decompiler, Heat = 'harvester', Pyro = patch builder, Torch = transform creation). You can keep .wixobj files between sessions if the corresponding source file hasn't changed, which may reduce build time (although most of the cost is in binding and validating the MSI rather than processing the source files). A traditional C compiler would only operate on a single source file per run, but like Microsoft's cl.exe, candle accepts multiple source files on the same command line. You should probably consider defining one Fragment per logical component (not necessarily Component) of your product. Just like C# and C++ classes, you can have more than one Fragment per source file, but it may be more understandable if you stick to one Fragment per source file. Splitting your installation into more source files reduces the chance of checkout/merge collisions with multiple developers. In general, Fragments are much nicer to work with than merge modules. -- Mike Dimmick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Collins, James Sent: 25 July 2007 19:35 To: Bob Arnson; Jeroen Davelaar Cc: WiX-users@lists.sourceforge.net Subject: Re: [WiX-users] Msi inside msi ? Hey Jeroen, I'm also not sure what your trying to achieve however for me I have very large installers including well over 16k files. For me I need to split that up to reduce build time as well as keeping things modular. The way I do that is with Merge Modules (MSM) which is basically an installer inside an installer. Jimbo -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: Wednesday, July 25, 2007 8:27 AM To: Jeroen Davelaar Cc: WiX-users@lists.sourceforge.net Subject: Re: [WiX-users] Msi inside msi ? Jeroen Davelaar wrote: How is it possible to nest a msi file with Orca while it is nog possible to do the same thing with WiX? WiX deprecated the functionality when the MSI team deprecated it. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using
Re: [WiX-users] Msi inside msi ?
Collins, James wrote: Yes I would agree fragments offer much more and I will keep that in mind moving forward. For me however I need a migration path from Wise to WIX and that's going to be merge modules for now. Once I have convinced my team WIX is the way to go (and believe me I'm trying very hard), and we are fully WIX then this approach makes much more sense. Easy way to start: Build fragments for everything then wrap them in a Module for those that need it and a .wixlib for those who don't. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Msi inside msi ?
Thanks for the confirmation Bob. So I have to drop this msi in msi solution because I want to deliver a msi, not an external .exe Do you have an other idea ? At least I would like the big part to be an msi, and the small one could be a zip or something. Bob Arnson a écrit : Emilien Bertin wrote: So I want the big msi to install the 2 msi. I employ the CustomAction type 50 (with [SystemFolder]msiexec and /quiet /i path_to_small_msi ). But it seems impossible to install two msi in the same time. That's correct. You need to use an external .exe bootstrapper. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Msi inside msi ?
thats not correct! you dont need the external exe. with custom action type 7/23/39 you can nest a msi. http://support.microsoft.com/default.aspx/kb/306439 Emilien Bertin wrote: Thanks for the confirmation Bob. So I have to drop this msi in msi solution because I want to deliver a msi, not an external .exe Do you have an other idea ? At least I would like the big part to be an msi, and the small one could be a zip or something. Bob Arnson a écrit : Emilien Bertin wrote: So I want the big msi to install the 2 msi. I employ the CustomAction type 50 (with [SystemFolder]msiexec and /quiet /i path_to_small_msi ). But it seems impossible to install two msi in the same time. That's correct. You need to use an external .exe bootstrapper. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Msi inside msi ?
How is it possible to nest a msi file with Orca while it is nog possible to do the same thing with WiX? Regards, Jeroen Davelaar -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Bernd Verzonden: woensdag 25 juli 2007 13:47 Aan: Emilien Bertin; WiX-users@lists.sourceforge.net Onderwerp: Re: [WiX-users] Msi inside msi ? thats not correct! you dont need the external exe. with custom action type 7/23/39 you can nest a msi. http://support.microsoft.com/default.aspx/kb/306439 Emilien Bertin wrote: Thanks for the confirmation Bob. So I have to drop this msi in msi solution because I want to deliver a msi, not an external .exe Do you have an other idea ? At least I would like the big part to be an msi, and the small one could be a zip or something. Bob Arnson a écrit : Emilien Bertin wrote: So I want the big msi to install the 2 msi. I employ the CustomAction type 50 (with [SystemFolder]msiexec and /quiet /i path_to_small_msi ). But it seems impossible to install two msi in the same time. That's correct. You need to use an external .exe bootstrapper. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Msi inside msi ?
Bernd, While it is not documented in the article you reference (but probably should be) custom action types 7, 23 and 39 are deprecated. For more details, see the various blog entries by the windows installer team - especially http://blogs.msdn.com/windows_installer_team/archive/2006/11/06/q-a-from-latest-windows-installer-webcast-available.aspx where they state Nested installs are still supported in [Windows Installer] 4.0. Concurrent Installations, also called Nested Installations, is a deprecated feature of the Windows Installer. Applications installed with concurrent installations can eventually fail because they are difficult for customers to service correctly. Do not use concurrent installations to install products that are intended to be released to the public. Regards, Richard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernd Sent: Wednesday, July 25, 2007 7:47 AM To: Emilien Bertin; WiX-users@lists.sourceforge.net Subject: Re: [WiX-users] Msi inside msi ? thats not correct! you dont need the external exe. with custom action type 7/23/39 you can nest a msi. http://support.microsoft.com/default.aspx/kb/306439 Emilien Bertin wrote: Thanks for the confirmation Bob. So I have to drop this msi in msi solution because I want to deliver a msi, not an external .exe Do you have an other idea ? At least I would like the big part to be an msi, and the small one could be a zip or something. Bob Arnson a écrit : Emilien Bertin wrote: So I want the big msi to install the 2 msi. I employ the CustomAction type 50 (with [SystemFolder]msiexec and /quiet /i path_to_small_msi ). But it seems impossible to install two msi in the same time. That's correct. You need to use an external .exe bootstrapper. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Quixote Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Msi inside msi ?
Emilien Bertin wrote: Do you have an other idea ? At least I would like the big part to be an msi, and the small one could be a zip or something. I'm not sure I understand the scope of the problem. WiX works just like every other compiler/linker in that it's scriptable so rebuilding an MSI to include new files is easily automatable. What do you gain by trying to separate? That's a long way of saying I don't know of a better solution if you want to ship just one MSI. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Msi inside msi ?
Jeroen Davelaar wrote: How is it possible to nest a msi file with Orca while it is nog possible to do the same thing with WiX? WiX deprecated the functionality when the MSI team deprecated it. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Msi inside msi ?
WiX was designed to support very large installer projects, with a design goal of distributed setup authoring. To support this idea, WiX supports Fragments. A Fragment is just a section of setup authoring. Loosely, candle compiles source files containing one or more Fragments into .wixobj files, and light links one or more .wixobj files into a final installer/merge module/patch. One, and only one, of the sections of an installation must be a Product, PatchCreation, or Module. candle and light are very much modelled after a C/C++ Compiler and Linker respectively. It took me a while to work out that the first letter of each tool's name indicates its purpose (Candle = compiler, Light = linker, Lit = library tool, Dark = decompiler, Heat = 'harvester', Pyro = patch builder, Torch = transform creation). You can keep .wixobj files between sessions if the corresponding source file hasn't changed, which may reduce build time (although most of the cost is in binding and validating the MSI rather than processing the source files). A traditional C compiler would only operate on a single source file per run, but like Microsoft's cl.exe, candle accepts multiple source files on the same command line. You should probably consider defining one Fragment per logical component (not necessarily Component) of your product. Just like C# and C++ classes, you can have more than one Fragment per source file, but it may be more understandable if you stick to one Fragment per source file. Splitting your installation into more source files reduces the chance of checkout/merge collisions with multiple developers. In general, Fragments are much nicer to work with than merge modules. -- Mike Dimmick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Collins, James Sent: 25 July 2007 19:35 To: Bob Arnson; Jeroen Davelaar Cc: WiX-users@lists.sourceforge.net Subject: Re: [WiX-users] Msi inside msi ? Hey Jeroen, I'm also not sure what your trying to achieve however for me I have very large installers including well over 16k files. For me I need to split that up to reduce build time as well as keeping things modular. The way I do that is with Merge Modules (MSM) which is basically an installer inside an installer. Jimbo -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: Wednesday, July 25, 2007 8:27 AM To: Jeroen Davelaar Cc: WiX-users@lists.sourceforge.net Subject: Re: [WiX-users] Msi inside msi ? Jeroen Davelaar wrote: How is it possible to nest a msi file with Orca while it is nog possible to do the same thing with WiX? WiX deprecated the functionality when the MSI team deprecated it. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Msi inside msi ?
Hey Jeroen, I'm also not sure what your trying to achieve however for me I have very large installers including well over 16k files. For me I need to split that up to reduce build time as well as keeping things modular. The way I do that is with Merge Modules (MSM) which is basically an installer inside an installer. Jimbo -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: Wednesday, July 25, 2007 8:27 AM To: Jeroen Davelaar Cc: WiX-users@lists.sourceforge.net Subject: Re: [WiX-users] Msi inside msi ? Jeroen Davelaar wrote: How is it possible to nest a msi file with Orca while it is nog possible to do the same thing with WiX? WiX deprecated the functionality when the MSI team deprecated it. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Msi inside msi ?
Thanks mike, Yes I would agree fragments offer much more and I will keep that in mind moving forward. For me however I need a migration path from Wise to WIX and that's going to be merge modules for now. Once I have convinced my team WIX is the way to go (and believe me I'm trying very hard), and we are fully WIX then this approach makes much more sense. WIX by stealth! :) Jimbo -Original Message- From: Mike Dimmick [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 25, 2007 12:02 PM To: Collins, James; 'Bob Arnson'; 'Jeroen Davelaar' Cc: WiX-users@lists.sourceforge.net Subject: RE: [WiX-users] Msi inside msi ? WiX was designed to support very large installer projects, with a design goal of distributed setup authoring. To support this idea, WiX supports Fragments. A Fragment is just a section of setup authoring. Loosely, candle compiles source files containing one or more Fragments into .wixobj files, and light links one or more .wixobj files into a final installer/merge module/patch. One, and only one, of the sections of an installation must be a Product, PatchCreation, or Module. candle and light are very much modelled after a C/C++ Compiler and Linker respectively. It took me a while to work out that the first letter of each tool's name indicates its purpose (Candle = compiler, Light = linker, Lit = library tool, Dark = decompiler, Heat = 'harvester', Pyro = patch builder, Torch = transform creation). You can keep .wixobj files between sessions if the corresponding source file hasn't changed, which may reduce build time (although most of the cost is in binding and validating the MSI rather than processing the source files). A traditional C compiler would only operate on a single source file per run, but like Microsoft's cl.exe, candle accepts multiple source files on the same command line. You should probably consider defining one Fragment per logical component (not necessarily Component) of your product. Just like C# and C++ classes, you can have more than one Fragment per source file, but it may be more understandable if you stick to one Fragment per source file. Splitting your installation into more source files reduces the chance of checkout/merge collisions with multiple developers. In general, Fragments are much nicer to work with than merge modules. -- Mike Dimmick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Collins, James Sent: 25 July 2007 19:35 To: Bob Arnson; Jeroen Davelaar Cc: WiX-users@lists.sourceforge.net Subject: Re: [WiX-users] Msi inside msi ? Hey Jeroen, I'm also not sure what your trying to achieve however for me I have very large installers including well over 16k files. For me I need to split that up to reduce build time as well as keeping things modular. The way I do that is with Merge Modules (MSM) which is basically an installer inside an installer. Jimbo -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: Wednesday, July 25, 2007 8:27 AM To: Jeroen Davelaar Cc: WiX-users@lists.sourceforge.net Subject: Re: [WiX-users] Msi inside msi ? Jeroen Davelaar wrote: How is it possible to nest a msi file with Orca while it is nog possible to do the same thing with WiX? WiX deprecated the functionality when the MSI team deprecated it. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Msi inside msi ?
Hi everybody, I'm trying to deliver a product with a msi, and I need help. I want to separate this product in two part, the big and commun one with all the main program, and the small and specific one with some configuration files. The idea behind this separation is to make easier futurs changes in the main program, without having to re-package all the specific parts. I have tried some stuff since a week, but I can't find the good one :( Actually my idea is to create 2 msi, one for each part of my application, and to include them into a bigger msi. (I don't know if this is the best way to achieve my aim, but at the beginning it sounded good). So I want the big msi to install the 2 msi. I employ the CustomAction type 50 (with [SystemFolder]msiexec and /quiet /i path_to_small_msi ). But it seems impossible to install two msi in the same time. So I tried to add Execute=commit to the CustomAction, without success (the first install of the big msi is not finish when the install of one of the two msi inside begins) Last week I also tried to make a module. The module worked fine, but the problem is that the module is include in the main msi when the main msi is created with light.exe, it's not an externel link. I hope you will be able to help me :) Thanks in advance! - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Msi inside msi ?
Emilien Bertin wrote: So I want the big msi to install the 2 msi. I employ the CustomAction type 50 (with [SystemFolder]msiexec and /quiet /i path_to_small_msi ). But it seems impossible to install two msi in the same time. That's correct. You need to use an external .exe bootstrapper. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
