You can add the new file in a new location in a patch, and it is simpler to leave the old dll in place.
This may work out for you if the application supports the moved dll and will ignore the old dll. If you really need to you can also try and remove the file during patching see http://petermarcu.blogspot.co.uk/2009/05/wix-removing-files-with-patches.html A major upgrade is much simpler. Dave -----Original Message----- From: Farrukhw [mailto:farru...@gmail.com] Sent: 29 May 2014 05:16 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Using '*' in Component Guids and Patches It might not be a common practice, but I faced it due to some customer requirement when we have to move a dll to another location. So ethically, it should be a Major Upgrade which would handle it with no problem. But I was asked to build a patch, as it is just one dll, So we build a new dll with a new incremented version and while sing same GUID for the component, patch didn't moved the file to new location, but did updated the dll to the new version. However, I tried to reproduced this using "*" instead of GUID and it simply didn't worked. On Thu, May 29, 2014 at 3:43 AM, Bryan Wolf-2 [via Windows Installer XML (WiX) toolset] <ml-node+s687559n7594938...@n2.nabble.com> wrote: > You should change the component code if the destination of the component > changes, as documented here: > http://msdn.microsoft.com/en-us/library/aa367849(v=vs.85).aspx > > Changing the component code is incompatible with minor/small updates; > since > you're talking about a patch and a major upgrade patch is more or less a > non-feature, the short answer is that it won't work. Don't change the path > of a component during the course of a patch - it's just not a compatible > use case. > > Technically speaking, you can make it work through careful and very > elaborate tailoring of the MSI package and manipulation of the feature > tree, but you really really don't want to do this :-) > > > On Wed, May 28, 2014 at 5:29 PM, Rob Mensching <[hidden > email]<http://user/SendEmail.jtp?type=node&node=7594938&i=0>> > wrote: > > > IIRC, I don't think that's going to work out well. You can try but I > think > > patching across directory moves probably doesn't work out great since > IIRC > > moving Component directories during repair doesn't tend to work out real > > well either. But that's just from memory... > > > > _______________________________________________________________ > > FireGiant | Dedicated support for the WiX toolset | > > http://www.firegiant.com/ > > > > -----Original Message----- > > From: Farrukhw [mailto:[hidden > > email]<http://user/SendEmail.jtp?type=node&node=7594938&i=1>] > > > Sent: Sunday, May 25, 2014 10:13 PM > > To: [hidden email]<http://user/SendEmail.jtp?type=node&node=7594938&i=2> > > Subject: [WiX-users] Using '*' in Component Guids and Patches > > > > Hi > > While searching for best practices, I came across this thread < > > > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Best-Practices-Using-quot-quot-for-GUID-automation-td5234716.html > > > > > , which is discussing the use of '*' instead of GUIDs in components. > > > > As far I know, while generating GUID dynamically from '*', if the > > destination of a Component is changes, so its GUID would also be > changed. > > There may be some other factors as well. > > > > Let's say we released ver 1.0.0.0 and then in 1.0.1.0 we changed the > > destination of a Component from Dir1 to Dir2. > > > > *Question:* If we generate Differential Patch between these two > versions, > > would the file get patched who's destination was changed in ver 1.0.1.0? > > Would using '*' in this case would be good? > > > > Regards > > Farrukh > > > > > > > > > > > > -- > > View this message in context: > > > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-in-Component-Guids-and-Patches-tp7594909.html > > Sent from the wix-users mailing list archive at Nabble.com. > > > > > > > ------------------------------------------------------------------------------ > > > The best possible search technologies are now affordable for all > companies. > > Download your FREE open source Enterprise Search Engine today! > > Our experts will assist you in its installation for $59/mo, no > commitment. > > Test it for FREE on our Cloud platform anytime! > > > > > http://pubads.g.doubleclick.net/gampad/clk?id=145328191&iu=/4140/ostg.clktrk > > _______________________________________________ > > WiX-users mailing list > > [hidden email] <http://user/SendEmail.jtp?type=node&node=7594938&i=3> > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > ------------------------------------------------------------------------------ > > > Time is money. Stop wasting it! Get your web API in 5 minutes. > > www.restlet.com/download > > http://p.sf.net/sfu/restlet > > _______________________________________________ > > WiX-users mailing list > > [hidden email] <http://user/SendEmail.jtp?type=node&node=7594938&i=4> > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ------------------------------------------------------------------------------ > > Time is money. Stop wasting it! Get your web API in 5 minutes. > www.restlet.com/download > http://p.sf.net/sfu/restlet > _______________________________________________ > WiX-users mailing list > [hidden email] <http://user/SendEmail.jtp?type=node&node=7594938&i=5> > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Patches-and-using-instead-of-Component-Guids-tp7594909p7594938.html > To unsubscribe from Wix Patches and using '*' instead of Component Guids, > click > here<http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=7594909&code=ZmFycnVraDFAZ21haWwuY29tfDc1OTQ5MDl8LTcxNDU3NzEzNQ==> > . > NAML<http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Patches-and-using-instead-of-Component-Guids-tp7594909p7594940.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Time is money. Stop wasting it! Get your web API in 5 minutes. www.restlet.com/download http://p.sf.net/sfu/restlet _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. This message has been scanned for malware by Websense. www.websense.com ------------------------------------------------------------------------------ Time is money. Stop wasting it! Get your web API in 5 minutes. www.restlet.com/download http://p.sf.net/sfu/restlet _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
