The problem you are hitting is that the Wixpdb contains no information about msm's they are merged in after the fact.
Three options: 1. Instead of using the wixpdb, just use the admin image functionality I added in order to create transforms for the products that contain msm's. 2. Use Melt.exe to convert your msm into a componentgroup, then remove the msm from your authoring and add in the componentgroup. 3. Don't use MSM's. :) To answer your repair question, it depends on the flags that are passed to msi during the repair, by default the newest version wins. One way to solve the long build time is to consider a langpack model. Where all the files that aren't per language live together in a single msi. This would mean that if you are patching a language neutral component you only have to patch the core msi and not the langpacks. -----Original Message----- From: Cristian N. Baiu [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 02, 2007 11:18 AM To: Peter Marcu; [EMAIL PROTECTED]; Cristian Baiu Cc: wix-users@lists.sourceforge.net Subject: Fw: [WiX-users] Fw: Some STUPID Limitations in WiX Thanks Bob, thanks Peter for your answers. I will not have problems with the localizations. The only problem will be the time to generate a patch, because my setup takes a very long time to build - about 30 mins for each MSI and I have over 20 MSI's (12 languages * 2 - due to x86 and x64). Knowing that my patches (hot-fixes most of them) will patch only non-localizable files (practically will update versioned DLL files), I was hoping I could optimize the patch build process by building only two upgrade MSIs (one for x86 and x64) and then pass by some other means only the product codes for the other MSI's to pyro. I don't know if it would be a "best practice" but it would sure suite me. Anyway, in lack of alternatives, I will do all the differences. Still, the biggest of my problems is the patching of the MSM which I was talking earlier. I have done some testing, trying to patch a (versioned) dll which is part of my MSM using pyro but had no success. The patch log wasn't saying anything about my file. Then I have tried to build the patch removing all the physical occurences of the file which I needed to patch (the MSM and MSI target and upgrade versions being build at the testing time). I have removed the DLL from my deployment folder - from where the MSM setup resolves it, I have removed the MSM from the folder used by the MSI which includes the MSM, I have removed the upgrade MSI's cabinet from the folder where torch is using it's upgrade wixpdb input file. Then I have build the patch and had no errors. This makes me think that neither torch, candle, light or pyro are even trying to do something with that file. (The reason for all of these was my hope to find out which of them needs to resolve the file and then try to debug it and understand what I've done wrong). Peter, you said in an earlier post that you could provide some workarounds for patching MSMs. It seems I have reached the moment when I need very bad to know them. Could you help me please ? Also Bob said earlier: "It will update the shared component but it won't update the other product, so a repair operation can "undo" the patch. That's why merge modules are falling way out of favor..." (refering to a patch for an MSM component which targets only one of more products containing the MSM). These are bad news. I do not know how installer performs the repair so my question is : does the repair replace a newer version of the shared file with an older one if the file is versioned correctly ? Thanks for your answers. I hope I was not too boring with my long story. Cristian. ----- Original Message ----- From: "Peter Marcu" <[EMAIL PROTECTED]> To: "Peter Marcu" <[EMAIL PROTECTED]>; "Bob Arnson" <[EMAIL PROTECTED]>; "Cristian Baiu" <[EMAIL PROTECTED]> Cc: <wix-users@lists.sourceforge.net> Sent: Tuesday, October 02, 2007 8:24 PM Subject: RE: [WiX-users] Fw: Some STUPID Limitations in WiX I meant pyro when I said torch below. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Marcu Sent: Tuesday, October 02, 2007 10:15 AM To: Bob Arnson; Cristian Baiu Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Fw: Some STUPID Limitations in WiX You should be able to pass transforms generated from wixpdb's in combination with ones generated from admin images. You will need a transform passed to torch for each product you want to target because product code information is important and I assume each language you ship has a different product code. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: Tuesday, October 02, 2007 9:07 AM To: Cristian Baiu Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Fw: Some STUPID Limitations in WiX Cristian Baiu wrote: > So far I don't know how to instruct pyro to address my patch to all > MSIs unless I make differences for > all of them and pass all these difference sets to pyro. > Can you please advice me if it's possible to target multiple MSIs with > only one set of differences and how ? > You'll need to use Torch's -ax switch to use admin images. I'm not sure how well that works to create one patch that also targets products using .wixpdbs. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
