Re: [WiX-users] Merge modules & wixlib compatibility

s, and is there any documentation for it? > > Thanks, > Jan > > > -Original Message----- > From: Christopher Painter [mailto:chr...@iswix.com] > Sent: 14 March 2013 12:03 > To: General discussion for Windows Installer XML toolset.; > wix-users@lists.sourceforge.net > Sub

Re: [WiX-users] Merge modules & wixlib compatibility

Painter [mailto:chr...@iswix.com] Sent: 14 March 2013 12:03 To: General discussion for Windows Installer XML toolset.; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Merge modules & wixlib compatibility MSM is a Windows Installer standard, wixlib is not. Otherwise they are similar in fun

Re: [WiX-users] Merge modules & wixlib compatibility

MSM is a Windows Installer standard, wixlib is not. Otherwise they are similar in function with wixlib being lighter weight and more flexible. But your scenario confuses me. An MSI can install one and only one product. It would be more accurate to say the files for one feature goes in M1 a

Re: [WiX-users] Merge Modules and Custom actions design

Are you redistributing these merge module or are they only for internal use in order to break out your installer into more composable / manageable peices? Everything I say is meant for the latter  not the former: For Custom Actions,  follow the table data driven design and put the custom action

Re: [WiX-users] Merge modules for Visual C++ 2010 Express?

I haven't installed VC Express, but the location for them in VS 2010 is "C:\Program Files (x86)\Common Files\Merge Modules" (or "C:\Program Files\Common Files\Merge Modules" if your box is 32-bit) but they are an option for the paid versions of VS (I don't know if they are in the defaults or not

Re: [WiX-users] Merge Modules and Multiple Targets

I would suggest shipping multiple merge modules (even if they are interdependent for complete functionality) - we used to integrate merge modules from a third party, they provided ~10 modules but our software only needed 5 of the components. Basically it was base module, licensing module, plus vari

Re: [WiX-users] Merge Modules and Patching

ch table. That path normally should normally NOT be the path to the admin install location. -Original Message- From: nearnick [mailto:n...@nearglobal.com] Sent: Monday, October 26, 2009 2:58 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Merge Modules and Patching Hi gu

Re: [WiX-users] Merge Modules and Patching

: Pally Sandher [mailto:pally.sand...@iesve.com] > Sent: Monday, October 05, 2009 3:52 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Merge Modules and Patching > > Are you totally sure the patch doesn't contain the new files from the &g

Re: [WiX-users] Merge modules install

:disclaime...@gmail.com] Sent: Monday, October 12, 2009 1:18 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Merge modules install Thanks Blair. I supposed such situation but I just didn't believe that this can be possible from Microsoft side. Best regards

Re: [WiX-users] Merge modules install

Thanks Blair. I supposed such situation but I just didn't believe that this can be possible from Microsoft side. Best regards Andreo 2009/10/10 Blair > There is a difference in the VC 8 runtime library installation routines > between XP and Vista. > > In Vista, the Win32 SxS configurati

Re: [WiX-users] Merge modules install

There is a difference in the VC 8 runtime library installation routines between XP and Vista. In Vista, the Win32 SxS configuration isn't completed until Commit, long after the StartServices action. http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=micros oft.public.platformsd

Re: [WiX-users] Merge Modules and Patching

, October 05, 2009 3:52 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Merge Modules and Patching Are you totally sure the patch doesn't contain the new files from the merge module? Have you checked a verbose log of applying the patch? You may find the pr

Re: [WiX-users] Merge Modules and Patching

ons Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: nearnick [mailto:n...@nearglobal.com] Sent: 05 October 2009 09:53 To: wix-users@lists.sourceforge.net Subject: Re: [W

Re: [WiX-users] Merge Modules and Patching

So i guess I'll just have to extract the merge module and add its contents to the installer package. That way I know the patch will definetly pick up any changes. Thanks anyway. nearnick wrote: > > They'd be wixpdbs. > > > Blair-2 wrote: >> >> Which files are the inputs to torch (admin-insta

Re: [WiX-users] Merge Modules and Patching

They'd be wixpdbs. Blair-2 wrote: > > Which files are the inputs to torch (admin-installed MSIs, wixpdbs, or > wixouts)? > > -Original Message- > From: nearnick [mailto:n...@nearglobal.com] > Sent: Wednesday, September 30, 2009 9:12 AM > To: wix-users@lists.sourceforge.net > Subject:

Re: [WiX-users] Merge Modules and Patching

Which files are the inputs to torch (admin-installed MSIs, wixpdbs, or wixouts)? -Original Message- From: nearnick [mailto:n...@nearglobal.com] Sent: Wednesday, September 30, 2009 9:12 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Merge Modules and Patching Hi I have this

Re: [WiX-users] Merge modules

Well, A merge module is very similar in structure to an Installer package. The major difference is that it doesn't contain everything a complete package holds so that the component can't be installed by the Installer just by using the merge module. The merge module contains the tables and binary

Re: [WiX-users] merge modules for C++ runtime(2005/2008) withATLsecurity fix?

Hi, I have some from 2006 with schema 300 too, so I would say no. Dave -Original Message- From: John Aldridge [mailto:j...@jjdash.demon.co.uk] Sent: 28 August 2009 13:18 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] merge modules for C

Re: [WiX-users] merge modules for C++ runtime (2005/2008) withATLsecurity fix?

> From: Anthony Wieser [mailto:wix-l...@wieser-software.com] > Sent: 28 August 2009 12:21 > > Does anyone here know for sure if the target version of the installer > changed to 3.00 from 2.00 for the merge modules? I don't know whether it's changed, but I do know that on my machine with the upda

Re: [WiX-users] merge modules for C++ runtime (2005/2008) withATLsecurity fix?

t: Friday, August 07, 2009 5:45 PM Subject: Re: [WiX-users] merge modules for C++ runtime (2005/2008) withATLsecurity fix? > Yes. When you install update for VS 2005/2008. > > > -Original Message- > From: Richard [mailto:legal...@xmission.com] > Sent: Friday,

Re: [WiX-users] merge modules for C++ runtime (2005/2008) with ATLsecurity fix?

In article <5c889913ff236e4190093af280ab4ec40182f17...@wwlkfmail1.wonderware.com>, "Wilson, Phil" writes: > I checked the updated merge modules with the kb article descriptions of file versions. ATL90.DLL is 9.0.30729.4148, that seems to be the one, x86 and x64. I see all my VC80 merge

Re: [WiX-users] merge modules for C++ runtime (2005/2008) with ATLsecurity fix?

: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] merge modules for C++ runtime (2005/2008) with ATLsecurity fix? If you open the following directory, you should find all the available merge modules: C:\Program Files\Common Files\Merge Modules A

Re: [WiX-users] merge modules for C++ runtime (2005/2008) with ATLsecurity fix?

part of the path. Andreas Mertens -Original Message- From: Richard [mailto:legal...@xmission.com] Sent: August-07-09 11:05 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] merge modules for C++ runtime (2005/2008) with ATLsecurity fix? In article , "Alex Iv

Re: [WiX-users] merge modules for C++ runtime (2005/2008) with ATLsecurity fix?

In my box they show up in C:\Program Files (x86)\Common Files\Merge Module YMMV -Original Message- From: Richard [mailto:legal...@xmission.com] Sent: Friday, August 07, 2009 11:05 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] merge modules for C++ runtime (2005/2008

Re: [WiX-users] merge modules for C++ runtime (2005/2008) with ATLsecurity fix?

In article , "Alex Ivanoff" writes: > Yes. When you install update for VS 2005/2008. How can I tell if I have the updated merge modules? I haven't tried using these before; where do they get installed? -- "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download

Re: [WiX-users] merge modules for C++ runtime (2005/2008) with ATLsecurity fix?

Yes. When you install update for VS 2005/2008. -Original Message- From: Richard [mailto:legal...@xmission.com] Sent: Friday, August 07, 2009 10:54 To: wix-users@lists.sourceforge.net Subject: [WiX-users] merge modules for C++ runtime (2005/2008) with ATLsecurity fix? Are there any merge

Re: [WiX-users] merge modules not working only vcredist.exe

Cheers all, that sorted it. > Date: Mon, 20 Jul 2009 12:13:07 +0100 > From: dwat...@sdl.com > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] merge modules not working only vcredist.exe > > Lol, why didn't I spot that. It is Monday morning I supp

Re: [WiX-users] merge modules not working only vcredist.exe

Lol, why didn't I spot that. It is Monday morning I suppose. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: 20 July 2009 12:01 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] merge modules not working only vcredis

Re: [WiX-users] merge modules not working only vcredist.exe

scussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] merge modules not working only vcredist.exe Sorry, 2005 not 2003 (it's late and getting latter...) -Original Message- From: Blair [mailto:os...@live.com] Sent: Monday, July 20, 2009 12:10 AM To: 'General d

Re: [WiX-users] merge modules not working only vcredist.exe

ers] merge modules not working only vcredist.exe Sorry, 2005 not 2003 (it's late and getting latter...) -Original Message- From: Blair [mailto:os...@live.com] Sent: Monday, July 20, 2009 12:10 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users]

Re: [WiX-users] merge modules not working only vcredist.exe

Sorry, 2005 not 2003 (it's late and getting latter...) -Original Message- From: Blair [mailto:os...@live.com] Sent: Monday, July 20, 2009 12:10 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] merge modules not working only vcre

Re: [WiX-users] merge modules not working only vcredist.exe

From: warne warne [mailto:warne...@hotmail.com] Sent: Saturday, July 18, 2009 6:10 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] merge modules not working only vcredist.exe So I remove the custom action to make sure the merge modules, as you say, install correctly.

Re: [WiX-users] merge modules not working only vcredist.exe

So I remove the custom action to make sure the merge modules, as you say, install correctly. Same result... App wont launch with merge modules (see 1st post for list of what I have). Only works if prior install vcredist.exe (2008). Can I rephrase this question. Is there a link s

Re: [WiX-users] merge modules not working only vcredist.exe

warne warne wrote: > Thanks for tip re static link & explaining InstallExecuteSequence. Im not > really concerned though about the custom action (launch app after > installation checkbox). I only mentioned it to reference the error message > 2896 in the log in case someone suggested it. The prob

Re: [WiX-users] merge modules not working only vcredist.exe

Hi Ari, Thanks for tip re static link & explaining InstallExecuteSequence. Im not really concerned though about the custom action (launch app after installation checkbox). I only mentioned it to reference the error message 2896 in the log in case someone suggested it. The problem is,

Re: [WiX-users] merge modules not working only vcredist.exe

Where is your launchapplication custom action scheduled in the InstallExecuteSequence? I think that the VC redists won't actually get installed to the SxS folder until after InstallFinalize, so if your action runs before then, the app won't find the VC dlls and you'll get the error message you're

Re: [WiX-users] Merge Modules for Ink Edit

Mensching [mailto:[EMAIL PROTECTED] Sent: Friday, July 25, 2008 11:15 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Merge Modules for Ink Edit You really do have to go after the people that created the Merge Module. However, it is very likely you can ignore

Re: [WiX-users] Merge Modules for Ink Edit

:[EMAIL PROTECTED] On Behalf Of John McLean, Jr. Sent: Friday, July 25, 2008 08:22 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Merge Modules for Ink Edit Rob, Thanks for the help. I do not know if I am doing this correctly. I have searched for an update to

Re: [WiX-users] Merge Modules for Ink Edit

ECTED] Sent: Thursday, July 24, 2008 7:35 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Merge Modules for Ink Edit 1. The Merge Module should have shipped all of its required actions (MsiPublishAssemblies) but didn't. To work around the bug in their Me

Re: [WiX-users] Merge Modules for Ink Edit

1. The Merge Module should have shipped all of its required actions (MsiPublishAssemblies) but didn't. To work around the bug in their Merge Module add the following to your MSI: That will ensure your MSI gets the required action. 2. The Merge Module shipped a Directory that overlaps

Re: [WiX-users] Merge Modules in General, Specifically - Crystal Reports XI

ation (or at least some of it) due to faults in the merge module. Hope this helps, Regards, Richard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ksmckeetx Sent: Thursday, November 29, 2007 5:25 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-

Re: [WiX-users] Merge Modules in General, Specifically - Crystal Reports XI

Behalf Of Alexei > Boukirev > Sent: Thursday, December 29, 2005 1:30 PM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Merge Modules in General, Specifically - Crystal > Reports XI > > Hello David, > > Add > > > > > to your - Cr

Re: [WiX-users] Merge Modules

Unless you are part of the Windows operating system you shouldn't be installing files into system32. SaiTeja wrote: > Hi, > > Please see the below code. > > When I add this code the following dll's are created not under system32. Its > created out side the folder system32. > > the dll's are "msvc

Re: [WiX-users] Merge Modules Serialized and Stamped at Install Time

DexterSinister wrote: > You'd be amazed at what some vendors will do to their customers ... ! > Amazed, surprised, saddened. All of the above. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by DB2

Re: [WiX-users] Merge Modules Serialized and Stamped at Install Time

Mike Dimmick wrote: > Their build process generates random GUIDs every time they run a build. > Surely nobody does something that insane...?! ** You'd be amazed at what some vendors will do to their customers ... ! And stop calling me Shirley ... Thanks for the laugh Bob ...

Re: [WiX-users] Merge Modules Serialized and Stamped at Install Time

sourceforge.net Subject: Re: [WiX-users] Merge Modules Serialized and Stamped at Install Time Mike Dimmick wrote: > Their build process generates random GUIDs every time they run a build. > Surely nobody does something that insane...?! -- sig://boB

Re: [WiX-users] Merge Modules Serialized and Stamped at Install Time

Mike Dimmick wrote: > Their build process generates random GUIDs every time they run a build. > Surely nobody does something that insane...?! -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by DB2

Re: [WiX-users] Merge Modules Serialized and Stamped at Install Time

Their build process generates random GUIDs every time they run a build. -- Mike Dimmick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nick Sent: 31 May 2007 03:21 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Merge Modules Serialized and Sta

Re: [WiX-users] Merge Modules Serialized and Stamped at Install Time

Nick wrote: "Also since the Modules are serialized and stamped at install time, we are unable to create merge modules that are generic." OK...what are they talking about? Sounds like they used a buzzword generator . Plainer English might reveal a dee

Re: [WiX-users] Merge Modules not retargetable during install?

I really need an explanation here as I'm obviously not understanding what is going on. Basicly my merge module and my components all install to INSTALLDIR. INSTALLDIR has a default value of c:\Program Files. During the installation the user can change that value through the UI to, lets say, c:\

Re: [WiX-users] Merge Modules evaluating earlier then Components?

s? -Original Message- From: Mike Dimmick [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 24, 2007 3:11 PM To: Alex Steen; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Merge Modules evaluating earlier then Components? The contents of a merge module are merged directly into your MSI

Re: [WiX-users] Merge Modules evaluating earlier then Components?

The contents of a merge module are merged directly into your MSI file - at that point, the merge module's identity is lost. The only indication that an entry in a table came from a merge module is that it typically has a GUID at the end of the textual component/file/registry ID, which is appended w

Re: [WiX-users] Merge Modules in Wix

D] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Steen Sent: 24 April 2007 16:04 To: Bob Arnson Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Merge Modules in Wix The contents are fine. However, it is installing the files, just in a completely different place. I'm installing to

Re: [WiX-users] Merge Modules in Wix

ed to? -Original Message- From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Monday, April 23, 2007 10:50 PM To: Alex Steen Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Merge Modules in Wix JCWrs wrote: > > > > > Display='expand' Leve

Re: [WiX-users] Merge Modules

odule - only a reference to it. Hope this helps, Regards, Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carl Quirion Sent: Monday, April 23, 2007 5:04 PM To: Thomas Svare; wix-users@lists.sourceforge.net Subject: Re: [WiX-users]

Re: [WiX-users] Merge Modules

Carl Quirion wrote: > Ive read that the proper way to do it is to get the merge modules made > by the maker of the 3rd party, however, this is not available for most > of my components. > So, i went ahead and decided to create my own. I can compile (candle, > light) them without a problem. I can

Re: [WiX-users] Merge Modules in Wix

JCWrs wrote: > >DiskId='1' /> > > > Display='expand' Level='1'> > > > > There are no errors, it just doesn't install the files. Any ideas? > Use Orca to verify the module's contents got merged in correctly. If they're there, check a verbose log to see what MSI dec

Re: [WiX-users] Merge Modules

Hi Tom, Thanks for you quick answer. I always output full verbose log (/l*vx installlog.txt) of installation while doing the dev. and i tryed looking for 6BE042C8-EE9B-11DB-8314-0800200C9A66, ActiveBar, DataDynamics, Merge and Merge module and couldnt find anything. Ive also did a file search for

Re: [WiX-users] Merge Modules

Your files may be installing just not where you are expecting them to. Take a look at a verbose log and you'll know for sure. One of the potential problems is the "Name" you've specified for the CommonFilesFolder is missing the space. I believe you can leave the name off altogether since the d

Re: [WiX-users] Merge Modules Read Main Install Property

Are you distributing this merge module to anyone else who isn't using WiX? If not, it may be a lot easier to convert from a Module to a Fragment and simply link it into the main installer.   light can accept any number of .wixobj and .wixlib files on the command line. The only restriction is

Re: [WiX-users] Merge Modules Read Main Install Property

Tina:Take a look at the IgnoreModularization tag.  You define it in the merge module wxs file.()Dana On 11/7/06, Tina Basinger <[EMAIL PROTECTED]> wrote: I have a case where my merge modules need to tell if they are running in an upgrade, or a fresh install.  I have a property that is getting set i

Re: [WiX-users] Merge modules again...

On 27.10.2006 17:03, Rob Mensching wrote: > 1. Dependency failure: This warning is telling you that you have a Merge > Module that depends on another Merge Module but you did not include the > second Merge Module. I don't know much about the new ATL Merge Modules, but > it would appear the co

Re: [WiX-users] Merge modules again...

On 30.10.2006 08:15, Christer Solskogen wrote: > Also the application does not start, blaming ATL. > This is bullshit. This is what we call PEBKAC. Despite all the warnings the merge modules work now. -- chs - Using Tomc

Re: [WiX-users] Merge modules again...

Solskogen; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Merge modules again... 1. Dependency failure: This warning is telling you that you have a Merge Module that depends on another Merge Module but you did not include the second Merge Module. I don't know much about the ne

Re: [WiX-users] Merge modules again...

1. Dependency failure: This warning is telling you that you have a Merge Module that depends on another Merge Module but you did not include the second Merge Module. I don't know much about the new ATL Merge Modules, but it would appear the core Merge Module requires a second policy module.