Hi, While trying to do this I got into the problem of setting the correct condition. So in my case I want a specific file, that it's NOT installed by the installer, but later created by the user, to be deleted only on uninstalls - not upgrades, not repairs or modifies. What condition should I use? Is (NOT UPGRADINGPRODUCTCODE) enough or should I also combine it with REMOVE="ALL"?
[code] <Component Id="MyRemoveConfFile" Guid="GUID"> <RemoveFile Id="MyRemoveConf" Name="*myapp.conf" On="uninstall"/> <Condition>NOT UPGRADINGPRODUCTCODE</Condition> </Component> [/code] Is this enough (having On="uninstall" and (NOT UPGRADINGPRODUCTCODE))? Or the conditioning should be more extensive taking in account that it should happen only on real uninstall (not installs, not upgrades, not repairs or modifies)? Thanks, Viv On 3/31/2010 10:42 AM, Viv Coco wrote: > > Use a Component Condition on your RemoveFile so it doesn't get > touched during major upgrades. > > Thx, I'll do so. > > Viv > > On 3/29/2010 1:14 PM, Pally Sandher wrote: > >> What happens if your Q&A find bugs in your application? Do you fix those >> in the installer too? >> >> Use a Component Condition on your RemoveFile so it doesn't get touched >> during major upgrades. However the copy procedure Sascha explained to >> would be outside of the installation process. If you do it within the >> installer you're going to have the same problem as before. >> >> Palbinder Sandher >> Software Deployment& IT Administrator >> T: +44 (0) 141 945 8500 >> F: +44 (0) 141 945 8501 >> >> http://www.iesve.com >> **Design, Simulate + Innovate with the<Virtual Environment>** >> Integrated Environmental Solutions Limited. Registered in Scotland No. >> SC151456 >> Registered Office - Helix Building, West Of Scotland Science Park, >> Glasgow G20 0SP >> Email Disclaimer >> >> -----Original Message----- >> From: Viv Coco [mailto:vcotirl...@hotmail.com] >> Sent: 29 March 2010 11:09 >> To: General discussion for Windows Installer XML toolset. >> Subject: Re: [WiX-users] don't delete/overwrite a file during major >> upgrade >> >> Hi, >> >> > Can you install a default configuration file and then copy that to >> the "user" configuration if it doesn't exist? >> >> Well, I could do so, already thought about that, but unfortunately the >> application is already in Q&A so we are not allowed to change anything >> to it anymore so everything "that is left" has to be done through the >> installer. I know, bad decision, but unfortunately it's not my decision >> :( >> >> So my application needs a conf file to run correctly (MyApp.cfg) where >> the user has to set some entries (it's per machine, not per user). I was >> thinking to do like this: when installing the application I also put in >> the binary directory the MyApp.cfg.template so that the user has it for >> later reference and the same one put also under the name MyApp.cfg and >> at the end of installation through the msi to open the MyApp.conf file >> so that the user can right away set it as he needs. When he closes the >> modified conf file, installation is finished and application will run >> correctly. Is there a way to do this without getting into those >> headaches you were saying? >> >> > Then just use RemoveFile to delete the config when your application >> is uninstalled. >> >> How can I do that? I mean how can I remove a file only when an real >> uninstall is done and not a major upgrade which also includes an >> uninstall before the new install? >> >> Thx, >> Viv >> >> >> On 3/29/2010 6:51 AM, Sascha Beaumont wrote: >> >> >>> Letting the user modify "installed" files will cause significant >>> headaches. Best solution, until you understand why, just don't do it. >>> >>> Can you install a default configuration file and then copy that to the >>> >>> >> >> >>> "user" configuration if it doesn't exist? That way Windows Installer >>> doesn't 'know' about the configuration file (except for the default >>> one which shouldn't be modified) and so won't try to replace it on >>> repair. Then just use RemoveFile to delete the config when your >>> application is uninstalled. >>> >>> >>> On Fri, Mar 26, 2010 at 8:08 PM, Viv coco<vcotirl...@hotmail.com> >>> >>> >> wrote: >> >> >>> >>> >>>> Hi, >>>> >>>> >>>> >>>> I read the WiX Tutorial from http://www.tramontana.co.hu/wix/ and >>>> >>>> >> there are some things I didn't understand or couldn't find and as I read >> that this is the best place for questions, I'll write them here, but for >> an easier followup I will write each question into a separat email. I >> appreciate your answers/help. >> >> >>>> When I install my application, along with the binaries, in the same >>>> >>>> >> directory a conf file is placed that the user can change as he needs. >> >> >>>> I would like for this conf file to not be deleted (or overwritten) >>>> >>>> >> when we do a major upgrade, but only when we remove the application >> completely from the computer, b/c otherwise the user needs to do the >> right settings in the conf file every time after an upgrade. >> >> >>>> In other words, for this conf file, I would like to have the >>>> >>>> >> following behaviour: when the product is upgraded (major upgrade which >> means first uninstall old version meaning deleting all installed files >> and then install a new version) the conf file should NOT be deleted or >> overwritten. But if the user uninstalls our product, for instance from >> add/remove program, then b/c I want to clean everything I would like >> that conf file to be deleted. How could I have this behaviour? >> >> >>>> >>>> TIA, >>>> Viv >>>> >>>> >>>> _________________________________________________________________ >>>> Hotmail: Trusted email with powerful SPAM protection. >>>> https://signup.live.com/signup.aspx?id=60969 >>>> --------------------------------------------------------------------- >>>> --------- >>>> Download Intel(r) Parallel Studio Eval >>>> Try the new software tools for yourself. Speed compiling, find bugs >>>> proactively, and fine-tune applications for parallel performance. >>>> See why Intel Parallel Studio got high marks during beta. >>>> http://p.sf.net/sfu/intel-sw-dev >>>> _______________________________________________ >>>> WiX-users mailing list >>>> WiX-users@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/wix-users >>>> >>>> >>>> >>>> >>> ---------------------------------------------------------------------- >>> -------- Download Intel® Parallel Studio Eval Try the new >>> software tools for yourself. Speed compiling, find bugs proactively, >>> and fine-tune applications for parallel performance. >>> See why Intel Parallel Studio got high marks during beta. >>> http://p.sf.net/sfu/intel-sw-dev >>> _______________________________________________ >>> WiX-users mailing list >>> WiX-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wix-users >>> >>> >>> >>> >>> >> ------------------------------------------------------------------------ >> ------ >> Download Intel® Parallel Studio Eval Try the new software tools for >> yourself. Speed compiling, find bugs proactively, and fine-tune >> applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >> >> > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
