Sharat: I am a little confused as to what exactly you are trying to achieve.
If you already have an MSP (SP1_Patch.msp), I think the diff between
Release.MSI and (Release.MSI + SP1_Patch.msp) would be exactly SP1_Patch.msp,
thus you don't need to do anything. What am I missing?
Svet
__
Are you consuming the merge module through Merge/MergeRef?
If so, you wouldn't be able to get past this error - merge modules are
processed as part of the binding phase of the WiX build process which is well
after linking -- where you got the error.
I can suggest you two approaches:
1) Modify th
WiX 3.0 patches produced using torch on wixpdbs will not include payload coming
from merge modules. This is by design because the merge modules are merged
*after* the wixpdbs are created.
You have 2 options:
1) Use admin images instead of wixpdbs.
2) Change your build process to use melt.exe on
http://www.wixwiki.com/index.php?title=Deploying_Additional_Components might be
helpful.
-Original Message-
From: Muthuramakrishnan [mailto:s...@srasys.co.in]
Sent: Tuesday, September 15, 2009 5:07 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Rega
Another option would be to use an include file and not a standalone wxs file
for the product-specific stuff:
In your %baseName%.wxs, somewhere under Product, add:
In your makefile do:
candle -DCurrentProduct=%baseName% %baseName%.wxs
Of course, you need to make sure that all
not the case.
--- On Thu, 9/3/09, Svet Bonev wrote:
From: Svet Bonev
Subject: Re: [WiX-users] Extra Files in Patch
To: "General discussion for Windows Installer XML toolset."
Date: Thursday, September 3, 2009, 4:15 PM
The granularity at which WiX v3 patching operates is a Fragment.
The granularity at which WiX v3 patching operates is a Fragment. This means
that any updated files authored in that Fragment will be packaged into the
patch.
When you say the files have not changed, I assume you mean that you haven't
changed their source code. But most likely they got new file
No, there is no built-in functionality to accomplish that.
But the bigger question is why you want to create such components. Ideally, you
would have file KeyPaths. Random component guids are usually bad for servicing
scenarios. What are you doing with these components? Giving us more details
Jaspreet: Your xmlns:iis="http://schemas.microsoft.com/wix/IIsExtension "
declaration has a space character before the closing quote. Remove the space
and try again.
Svet Bonev
Microsoft Corporation
-Original Message-
From: Sebastian Brand (Instyler Software) [mai
9 matches
Mail list logo
