I must be missing something simple. I verified that the "diff" file
(diff.wixmst) has my new components in it. Each "row" for my new components
has a "<row op='add'..." tag.
Another follow-on question .. I have new TRANSFORMS to be passed in as part
of the patch. I created a ".mst" file for these. Do i pass these in like I
do when I installed the inital msi? Here is the command I am using:
msiexec.exe /p kCTools.v1.0.1.Patch.msp /l*vx kCTools.v1.0.1.Patch.log
TRANSFORMS=DevEnvSettings.mst
Thanks,
- Troy
On Fri, May 22, 2009 at 11:18 AM, troy hostetter
<troy.hostet...@gmail.com>wrote:
> This is really odd. I created a small patch demo project, and was able to
> patch an existing xml file using XmlConfig, however my main WiX project is
> not able to generate a patch :(
>
> I attempted the KeyPath setting as shown here:
>
> <DirectoryRef Id="TARGETDIR">
> <Component Id="C__kCPursuit.Search.AppSettings"
> Guid="{CFDBC7EE-B7C0-48bb-864B-8D0DBF75BF42}" KeyPath="yes" DiskId="1">
> <!-- Create SearchDefaultConfigSection node -->
> <util:XmlConfig Id="XC__Search.web.config.create.1"
> File="[ROOT.WEBDIR]web.config" Action="create" On="install"
> ElementPath="//configuration/appSettings"
> Name="add" Node="element"
> VerifyPath="add[...@key='SearchDefaultConfigSection'[\]]"
> Sequence="1" />
> <util:XmlConfig Id="XC__Search.web.config.create.2"
> File="[ROOT.WEBDIR]web.config" ElementPath="XC__Search.web.config.create.1"
> Name="key"
> Value="SearchDefaultConfigSection"
> Sequence="2" />
> <util:XmlConfig Id="XC__Search.web.config.create.3"
> File="[ROOT.WEBDIR]web.config" ElementPath="XC__Search.web.config.create.1"
> Name="value" Value="SearchServiceConfig"
> Sequence="3" />
> </Component>
> </DirectoryRef>
>
> However, I get the following pyro error when i run my patch script
>
> Patch Script:
>
> %WiXPath%\torch -p -xi -v -notidy
> %V1.0.0Path%\bin\x64\Release\kCTools.Deploy.wixpdb
> %V1.0.1Path%\bin\x64\Release\kCTools.Deploy.wixpdb -out diff.wixmst
> %WiXPath%\candle.exe kCTools.v1.0.1.Patch.wxs
> %WiXPath%\light.exe kCTools.v1.0.1.Patch.wixobj -out
> kCTools.v1.0.1.Patch.wixmsp
> %WiXPath%\pyro.exe kCTools.v1.0.1.Patch.wixmsp -out
> kCTools.v1.0.1.Patch.msp -t RTM diff.wixmst
>
> Pyro Error:
>
> error PYRO0260 : Product '{1F6FE067-01BE-4D39-B880-0AEF3E4F84D0}': Table
> 'CreateFolder' has a new row 'TARGETDIR/C__Search.AppSettings' added. This
> makes the patch not uninstallable.
> pyro.exe : error PYRO0261 : This patch is not uninstallable. The 'Patch'
> element's attribute 'AllowRemoval' should be set to 'no'.
>
> Also, what process (torch, candle, light, pyro) should I set verbose
> logging? I tried "torch -p -xi -v -notidy" and do not see any log files.
> Torch output says:
>
> Binder temporary directory located at
> 'C:\Users\hostette\AppData\Local\Temp\xmydgbq7'.
> Unbinder temporary directory located at
> 'C:\Users\hostette\AppData\Local\Temp\xmydgbq7'.
> Torch temporary directory located at
> 'C:\Users\hostette\AppData\Local\Temp\ad4e_pqn'.
>
> However there is no such temp directory for Torch. I assumed the notidy
> option would keep the files around.
>
> Thanks,
> - Troy
>
>
>
> On Tue, May 19, 2009 at 8:15 PM, Rob Mensching <r...@wixtoolset.org> wrote:
>
>> Verbose log file should show you what Components are being changed. My
>> bet is that your 10 unchanged Components KeyPaths are not being updated.
>>
>> troy hostetter wrote:
>> > I am attempting to patch an existing web.config file with new web.config
>> > settings. When I execute msiexec and pass in the msp file, the
>> > "util:XmlConfig" patches are not being applied.
>> >
>> > My Tools.v1.0.1.Patch.wxs file looks like:
>> >
>> > *<?xml version="1.0" encoding="UTF-8"?>
>> > <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";>
>> > <Patch
>> > AllowRemoval="yes"
>> > Manufacturer="Company"
>> > DisplayName="v1.0.1 Patch"
>> > Description="UI Patch"
>> > Classification="Update"
>> > >
>> >
>> > <Media Id="5000" Cabinet="RTM.cab">
>> > <PatchBaseline Id="RTM"/>
>> > </Media>
>> >
>> > <PatchFamilyRef Id="v1.0.1_PatchFamily"/>
>> > </Patch>
>> >
>> > <Fragment>
>> > <PatchFamily Id='v1.0.1_PatchFamily' Version='1.0.0.0'
>> Supersede='yes'>
>> > <ComponentRef Id="C__CustomSearch.RegKey" />
>> > <ComponentRef Id="C__Pursuit.Search.AppSettings" />
>> > <ComponentRef Id="C__Project.Search.AppSettings" />
>> > <ComponentRef Id="C__Enterprise.Search.AppSettings" />
>> > <ComponentRef Id="C__Pursuit.SearchRDLWS.serviceModel" />
>> > <ComponentRef Id="C__Project.SearchRDLWS.serviceModel" />
>> > <ComponentRef Id="C__Enterprise.SearchRDLWS.serviceModel" />
>> > <ComponentRef Id="C__Pursuit.SearchWS.serviceModel" />
>> > <ComponentRef Id="C__Project.SearchWS.serviceModel" />
>> > <ComponentRef Id="C__Enterprise.SearchWS.serviceModel" />
>> >
>> > <ComponentRef Id="C__SPDeploy.exe"/>
>> > <ComponentRef Id="C__SPDeploy.Tools.config"/>
>> > <ComponentRef Id="C__SPDeploy.Search.config"/>
>> > <ComponentRef Id="C__SPDeploy.CustomSearch.Solutions"/>
>> > <ComponentRef Id="C__SPDeploy.CustomSearch.ListTemplates"/>
>> > </PatchFamily>
>> > </Fragment>
>> > </Wix>
>> > *
>> >
>> > The first 10 ComponentRefs are not being applied, however the last 5 are
>> > being applied. As I mentioned earlier, the first 10 are util:XmlConfig
>> ..
>> > the last 5 push out new files.
>> >
>> > Is there something special I need to be doing in order to patch xml
>> using
>> > util:XmlConfig entries?
>> >
>> > Here's my pyro commands:
>> >
>> > *SET WiXPath="C:\Program Files\Windows Installer XML v3\bin"
>> > SET
>> >
>> V1.0.0Path="C:\Users\x\Desktop\PatchBuild\_DeploymentStaging\Tools.Deploy\Tools.Deploy"
>> > SET
>> >
>> V1.0.1Path="C:\Users\x\Desktop\PatchBuild\_DeploymentStaging_V1.0.1\Tools.Deploy\Tools.Deploy"
>> >
>> > %WiXPath%\torch -p -xi %V1.0.0Path%\bin\x64\Release\Tools.Deploy.wixpdb
>> > %V1.0.1Path%\bin\x64\Release\Tools.Deploy.wixpdb -out diff.wixmst
>> > %WiXPath%\candle.exe Tools.v1.0.1.Patch.wxs
>> > %WiXPath%\light.exe Tools.v1.0.1.Patch.wixobj -out
>> Tools.v1.0.1.Patch.wixmsp
>> > %WiXPath%\pyro.exe Tools.v1.0.1.Patch.wixmsp -out Tools.v1.0.1.Patch.msp
>> -t
>> > RTM diff.wixmst*
>> >
>> > I then execute the following statement to apply the patch:
>> >
>> > *msiexec.exe /p Tools.v1.0.1.Patch.msp /l*vx Tools.v1.0.1.Patch.log
>> > TRANSFORMS=DevEnvSettings.mst*
>> >
>> > - Troy
>> >
>> ------------------------------------------------------------------------------
>> > Crystal Reports - New Free Runtime and 30 Day Trial
>> > Check out the new simplified licensing option that enables
>> > unlimited royalty-free distribution of the report engine
>> > for externally facing server and web deployment.
>> > http://p.sf.net/sfu/businessobjects
>> > _______________________________________________
>> > WiX-users mailing list
>> > WiX-users@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/wix-users
>> >
>>
>>
>> ------------------------------------------------------------------------------
>> Crystal Reports - New Free Runtime and 30 Day Trial
>> Check out the new simplified licensing option that enables
>> unlimited royalty-free distribution of the report engine
>> for externally facing server and web deployment.
>> http://p.sf.net/sfu/businessobjects
>> _______________________________________________
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>
>
------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, &
iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://www.creativitycat.com
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
