Windows installer looks at each item in a patch and repairs the entire feature
that item belongs to (unless that feature wasn't installed). Thus, if the new
item is in an already existing feature, and that entire feature isn't in the
patch itself, then Windows Installer may have to prompt for source if any
resource in that feature was somehow changed from what Windows Installer last
wrote for that product.
> Date: Wed, 7 Aug 2013 22:48:19 -0300
> From: nicolas.alva...@gmail.com
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Adding a registry key in a patch
>
> I'm creating a patch using WiX's native support: admin install of both
> packages, compile <Patch> wxs with candle, link into .wixmsp with
> light, create transform between .msi's with torch outputting a
> .wixmst, and put it all together with pyro.
>
> What's the best/correct way to add a new registry key in the patch,
> and get it removed when the patch is uninstalled? I tried adding the
> registry key as a new Component in the only Feature I have, and
> referencing the component in patch.wxs as
> Patch/PatchFamily/ComponentRef. I tested installing the original
> package, installing the patch, and uninstalling the patch, and it all
> seems to work. But pyro is giving me this warning:
>
> C:\Users\Nicolas\testapp\admin-longertext\installer-1.0.0-longertext.msi
> : warning PYRO1110 : Component 'TestReg' was added to feature
> 'Complete' in the transform 'C:\Users\Nicolas\testapp\RtmToLt.wixmst'.
> If you cannot guarantee that this feature will always be installed,
> you should consider adding new components to new top-level features to
> prevent prompts for source when installing this patch.
>
> ...which leaves me with the feeling that I'm not doing things the Right Way™
> :)
>
> I also don't fully understand what the warning means. In my case,
> since this is the only feature, it will obviously be always installed.
> But just for my understanding: let's suppose I have several features,
> I add a new component to one of them in a patch, the user doesn't have
> that particular feature installed, and he tries to install the patch.
> What would go wrong?
>
> --
> Nicolás
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
