Re: [WiX-users] defining sequence in Custom element
Hi Rob, I agree that starting services would be difficult before installing files ;) But in a pure logical way, does not mean that CustomAction2 will be executed after InstallFiles. It just means that it will be executed before StartServices... Why wouldn't the sequence be : CustomAction2 -> InstallFiles -> StartServices ? The former element is still valid (CustomAction2 is executed before StartServices) In fact, while writing these lines, I think I start to understand the way it works. Tell me if I'm wrong... The before or after attribute means that the CustomAction will be executed *right* before or after the specified Sequence i.e., if I write this means that CustomAction2 will be executed right before StartServices BUT after any other Sequence preceding StartServices (as installFiles for example)... Am I right? Thanks again for your time. Fred Le 16/09/2011 20:10, Rob Mensching a écrit : > Because StartServices can't start services before the files for the services > are installed. > > 2011/9/16 Frédéric Viollet > >> Hi Rob, >> >> Do you mean that if I write: >> >> >> >> >> Or >> >> >> >> >> In both cases, I'm sure that CustomAction1 will be executed after >> InstallFiles, that CustomAction2 will be executed after CustomAction1 >> and before StartServices? >> If so, what's the logic associated to these After and Before attributes? >> Why would >> >> >> >> guarantee me that it will be executed after InstallFiles? >> >> >> Thanks. >> Fred >> >> Le 16/09/2011 11:56, Rob Mensching a écrit : >>> Pick one. >>> >>> 2011/9/15 Frédéric Viollet >>> >>>> Hi All, >>>> >>>> I have defined two custom actions and I would like it to be triggered >>>> after InstallFiles, but before StartServices. >>>> Lets say I want to setup the following sequence: >>>> InstallFiles -> CustomAction1 -> CustomAction2 -> StartServices >>>> >>>> I would have liked to write: >>>> >>>> >>> Before="StartServices" /> >>>> But, in the wxs, Before and After tags are mutually exclusive in the >>>> Custom element. >>>> How can I achieve this? >>>> >>>> Thanks for your help. >>>> Frederic >>>> >>>> >>>> >> -- >>>> Doing More with Less: The Next Generation Virtual Desktop >>>> What are the key obstacles that have prevented many mid-market >> businesses >>>> from deploying virtual desktops? How do next-generation virtual >> desktops >>>> provide companies an easier-to-deploy, easier-to-manage and more >> affordable >>>> virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ >>>> _______ >>>> WiX-users mailing list >>>> WiX-users@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/wix-users >>>> >>>> >> >> >> >> -- >> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA >> http://p.sf.net/sfu/rim-devcon-copy2 >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> > > -- ** *Frédéric VIOLLET* - Role Management Software Engineer Tel: +33 (0) 1 30 80 77 34 Fax: +33 (0) 1 30 80 77 99 Std: +33 (0) 1 30 80 70 00 www.wiseguard.com <http://www.evidian.com/blog/> This e-mail contains material that is confidential for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA http://p.sf.net/sfu/rim-devcon-copy2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] defining sequence in Custom element
Hi Rob, Do you mean that if I write: Or In both cases, I'm sure that CustomAction1 will be executed after InstallFiles, that CustomAction2 will be executed after CustomAction1 and before StartServices? If so, what's the logic associated to these After and Before attributes? Why would guarantee me that it will be executed after InstallFiles? Thanks. Fred Le 16/09/2011 11:56, Rob Mensching a écrit : > Pick one. > > 2011/9/15 Frédéric Viollet > >> Hi All, >> >> I have defined two custom actions and I would like it to be triggered >> after InstallFiles, but before StartServices. >> Lets say I want to setup the following sequence: >> InstallFiles -> CustomAction1 -> CustomAction2 -> StartServices >> >> I would have liked to write: >> >> > Before="StartServices" /> >> But, in the wxs, Before and After tags are mutually exclusive in the >> Custom element. >> How can I achieve this? >> >> Thanks for your help. >> Frederic >> >> >> -- >> Doing More with Less: The Next Generation Virtual Desktop >> What are the key obstacles that have prevented many mid-market businesses >> from deploying virtual desktops? How do next-generation virtual desktops >> provide companies an easier-to-deploy, easier-to-manage and more affordable >> virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> > -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA http://p.sf.net/sfu/rim-devcon-copy2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] defining sequence in Custom element
Hi All, I have defined two custom actions and I would like it to be triggered after InstallFiles, but before StartServices. Lets say I want to setup the following sequence: InstallFiles -> CustomAction1 -> CustomAction2 -> StartServices I would have liked to write: But, in the wxs, Before and After tags are mutually exclusive in the Custom element. How can I achieve this? Thanks for your help. Frederic -- Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] simple condition...
Great, it does indeed seem to work now! Thanks again. Fred Le 22/03/2011 14:04, Pally Sandher a écrit : > dblock of dotnetinstaller fame created a bunch of standard properties in a > WiX include which you may find useful for this. See > http://code.dblock.org/ShowPost.aspx?id=101 > > Palbinder Sandher > Software Deployment Engineer > T: +44 (0) 141 945 8500 > F: +44 (0) 141 945 8501 > > http://www.iesve.com > **Design, Simulate + Innovate with the** > 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: Frédéric Viollet [mailto:frederic.viol...@evidian.com] > Sent: 22 March 2011 11:19 > To: 'General discussion for Windows Installer XML toolset.' > Subject: [WiX-users] simple condition... > > Hi folks, > > I'm trying to implement a very (at least, I guess it is...) simple > condition... > I would like a Component to be installed ONLY on an initial installation > (and not on Major Upgrade or Repair) > > The code looks like this: > > > IncludeMinimum='yes' Minimum='8.0.001.0' /> > > > snip > > > NOT OLDPRODUCT > DestinationName="server.xml" FileId="server.xml.ssl" /> > DestinationName="my_file1" FileId="Console_conf_file1" /> > DestinationName="my_file2" FileId="Console_conf_file2" /> > DestinationName="my_file3" FileId="Console_conf_file3" /> > > > My problem is that the CopyFiles are done on each installation (initial, > Major upgrade and Repair) > > NOTE : I didn't set any Guid for the component since I don't want this > component to be managed on uninstallation. Is this a valid way for > managing this? > NOTE2 : My product only upgrades through major upgrades. > > Could someone please tell me what I am doing wrong? > Thanks for your help... > > Fred -- ** *Frédéric VIOLLET* - Role Management Software Engineer Tel: +33 (0) 1 30 80 77 34 Fax: +33 (0) 1 30 80 77 99 Std: +33 (0) 1 30 80 70 00 www.wiseguard.com <http://www.evidian.com/blog/> This e-mail contains material that is confidential for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] simple condition...
Hi folks, I'm trying to implement a very (at least, I guess it is...) simple condition... I would like a Component to be installed ONLY on an initial installation (and not on Major Upgrade or Repair) The code looks like this: snip NOT OLDPRODUCT My problem is that the CopyFiles are done on each installation (initial, Major upgrade and Repair) NOTE : I didn't set any Guid for the component since I don't want this component to be managed on uninstallation. Is this a valid way for managing this? NOTE2 : My product only upgrades through major upgrades. Could someone please tell me what I am doing wrong? Thanks for your help... Fred -- *____* *Frédéric VIOLLET* - Role Management Software Engineer Tel: +33 (0) 1 30 80 77 34 Fax: +33 (0) 1 30 80 77 99 Std: +33 (0) 1 30 80 70 00 www.wiseguard.com <http://www.evidian.com/blog/> This e-mail contains material that is confidential for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Setting a property through a custom action
Hi all, I've been struggling for two days trying to achieve something that I believe simple (obvioulsy not for me...) Here's some part of my code: ... install some stuff here ... ... close all directories On an initial installation, the UI allows me to set the 'A_DIRECTORY_ID' property to ... lets say E:\Program Files\Company\myProduct On majors upgrades, the installer reads the registry (on the AppSearch sequence) to retrieve a given key (that I have set on the initial installation) and sets 'A_DIRECTORY_ID' with this value. So the upgrade installed to new version at the same place the old version was installed. Everything worked well ... untill I had to add some files in another directory under 'Company' ex: install some file here ... ... install some stuff here ... ... close all directories The problem, here, is that since the initial installation or an upgrade only setups the 'A_DIRECTORY_ID' property, 'myProduct2' will systematically be created under C:\Program Files\Company instead of E:\Program Files\Company (this is of course an example) I've tried writing a Custom Action to set the 'ANOTHER_DIR_ID' by using the 'A_DIRECTORY_ID' property. I used to MsiSetProperty function. But, although the customaction is triggered, the log nevers tells me that the 'ANOTHER_DIR_ID' is changed by this. Any idea? Here are some snippets from my wix code: -- the way I retrieve the 'A_DIRECTORY_ID' property on an upgrade -- -- the way I triggered my custom action -- The apm_get_webservice_parent_directory custom action reads the 'A_DIRECTORY_ID' property and builds the 'ANOTHER_DIR_ID' property (and then calls MsiSetProperty) Please Help Thanks. Fred -- Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] heat and UNC paths
Hi, I'm trying to use heat to generate a wxs fragment file out of a directory. But it seems the heat does not support UNC paths neither for the "dir" parameter nor for the "out" parameter... Is this a "normal" behaviour? Here are the two tested command lines: heat.exe dir thedir -ag -sfrag -out //mycomputer/othershared_folder/thewxs.file.wxs heat.exe : error HEAT0114 : The parameter '-out' must be followed by a file path. heat.exe dir //mycomputer/shared_folder/thedir -ag -sfrag -out thewxsfile.wxs heat.exe : error HEAT0001 : Value cannot be null. Parameter name: argument Exception Type: System.ArgumentNullException Stack Trace: at Microsoft.Tools.WindowsInstallerXml.Harvester.Harvest(String argument) at Microsoft.Tools.WindowsInstallerXml.Tools.Heat.Run(String[] args) Any ideas? Thanks Fred -- Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] setupbld bootstrapper & 64bit
Bob Arnson a écrit : > Frédéric Viollet wrote: > >> -I want to install a 64 bit product (my exes and dll are natively >> compiled for 64bit) on a 64bit OS >> -I build an x64 MSI (Platform=x64, Win64=yes in Components, etc...) >> -I build a 32bit bootstrapper using setupbld >> -This setup will be able to install the embedded x64 MSI. >> >> Am I right? >> >> > > Yes or at least, I'm not aware of any bugs that would prevent it. MSI > has both 32-bit and 64-bit install engines. > > Ok. Thank you very much for your help. I'll try this out. Fred -- Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] setupbld bootstrapper & 64bit
Bob Arnson a écrit : > Frédéric Viollet wrote: > >> -do I have to install the 64bit version of Wix? I guess not...the >> 32bit version should still be working... am I right? >> > > The 64-bit WiX installer exists to support MSBuild running as a 64-bit > process. That's all. > > >> -will setupbld.exe build 64bit executables? If not, could this be a >> problem in installing a 64bit product? Can a 32bit bootstrapper >> install 64bit products? >> > > No, no, yes. This all assumes you're talking x64, not IA64. > Thanks for your reply. I am indeed talking about x64 components. So to be sure I'm not getting mixed up, let me summarize: -I want to install a 64 bit product (my exes and dll are natively compiled for 64bit) on a 64bit OS -I build an x64 MSI (Platform=x64, Win64=yes in Components, etc...) -I build a 32bit bootstrapper using setupbld -This setup will be able to install the embedded x64 MSI. Am I right? Thanks again for your help. Fred -- Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] setupbld bootstrapper & 64bit
Hi, I'm currently using setupbld (in Wix V3) as a bootstrapper for managing my product upgrades. My team is willing to build a native 64 product. Compilation will be done on a 64 bit OS. My questions are : -do I have to install the 64bit version of Wix? I guess not...the 32bit version should still be working... am I right? -will setupbld.exe build 64bit executables? If not, could this be a problem in installing a 64bit product? Can a 32bit bootstrapper install 64bit products? Thanks for your help. Fred -- Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] multiple language installer
Ok. I'll have a look at former discussions than. Thanks. Fred Rob Mensching a écrit : > This is discussed much in the list. You might search to get lots of options. > Nothing is supported natively. > > -Original Message- > From: Frédéric Viollet [mailto:frederic.viol...@evidian.com] > Sent: Friday, January 30, 2009 00:57 > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] multiple language installer > > Hi everyone, > > I was wondering if it was possible to build a single installer that embeds > several languages (this installer would switch to the platform's current > language)? > Or do I have to build as many installers as I have languages to support? > I want my product to be able to be deployed in France, Germany, United States > and Japan. So I would like to embed these four languages. > > Thanks. > > Fred > > -- > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] multiple language installer
Hi everyone, I was wondering if it was possible to build a single installer that embeds several languages (this installer would switch to the platform's current language)? Or do I have to build as many installers as I have languages to support? I want my product to be able to be deployed in France, Germany, United States and Japan. So I would like to embed these four languages. Thanks. Fred -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] InstallDir is lost on minor upgrade
Johan Appelgren a écrit : > On Tue, Jul 1, 2008 at 11:29 AM, Frédéric Viollet > <[EMAIL PROTECTED]> wrote: > >> Johan Appelgren a écrit : >> >>> On Tue, Jul 1, 2008 at 10:07 AM, Frédéric Viollet >>> <[EMAIL PROTECTED]> wrote: >>> >>> >>>> Hi everyone, >>>> >>>> I've got a real big problem here on applying minor upgrades to my >>>> product. I really need your help here :) >>>> During the first install, I ask the user where the product should be >>>> installed (by using the wix standard Gui) >>>> But on minor upgrades, I do not ask him again. I just re-install the >>>> files to the previously selected location (well, that's what I'd like to >>>> do) >>>> I seem to have some problems with the property that points to my >>>> installation directory. >>>> Here's an extraction of the code I'm using: >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>>>>> Key="Software\MyCompany\MyProduct\MySuite\MyModule"> >>>> >>> Value="[SUITEINSTALLDIR]MyModule" Type="string" Action="write" /> >>>> >>>>. Install a bunch of files >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> Now, let's say that the default ProgramFilesFolder is C:\Program Files\ >>>> On the first installation, the installdir is ask for. I enter F:\Program >>>> Files\MyCompany\MyProduct\MySuite *(and not C:)*. Everything works well : >>>> -the files are installed in F:\Program Files\MyCompany\MyProduct\MySuite >>>> -the registry value "InstallDir" is set to F:\Program >>>> Files\MyCompany\MyProduct\MySuite\MyModule >>>> >>>> On a minor upgrade, no installation dir is ask for (this is ok), and the >>>> new files are correctly copied to F:\Program >>>> Files\MyCompany\MyProduct\MySuite, but : >>>> -the registry value "InstallDir" is set to *C::\Program >>>> Files\MyCompany\MyProduct\MySuite\MyModule* >>>> >>>> Any idea of how I could fix this? >>>> >>>> Thanks a lot for your patience for reading all way down here :) >>>> >>>> Fred >>>> >>>> >>> I think you must set the SUITEINSTALLDIR property using a RegistrySearch. >>> http://wix.sourceforge.net/manual-wix2/wix_xsd_registrysearch.htm >>> >>> >> Ok. I will try this. >> The code should look like this then I guess: >> >> | >> > Key="|Software\MyCompany\MyProduct\MySuite\MyModule|" Name="InstallDir" /> >> >> >> snip >> >> >> snip >> >> >> >> | >> >> But, will this work on first install (the registry key will not be >> found)? Will the SUITEINSTALLDIR Property have a default value? >> > > Yes, in that case the registry search will not set the property. > SUITEINSTALLDIR will then be set as before based on the Directory > structure. > > >>> Why is the InstallDir registry value the KeyPath for all your files? >>> Normally you have one component per .exe, .dll, .ocx and so on with >>> the file as KeyPath. >>> >>> >> My fault. The extracted code was incomplete. There was a missing >> after the Registry entries :) >> > > Okey. :) > Thanks a lot for your help. Fred - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Parsing properties
Ok, thanks for your answer. Fred Nitin Chaudhari a écrit : String manipulation is not supported in WIX, you will have to write a C++/.net/vbs custom action to get substring. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frédéric Viollet Sent: Tuesday, July 01, 2008 3:41 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Parsing properties Hi everyone, Let's say that I have a registry key HKLM\Software\MyProduct with a String value "TheDir" = "c:\program files\My product\module" I can easily get the value by using a RegistrySearch: Key="Software\MyProduct" Name="TheDir" /> Here's the question: :) Is there a way to extract a substring from the retrieved value i.e. The value in the registry is "c:\program files\My product\module", and I would like to set MYPROP to "c:\program files\My product" (get rid of the trailing "module") Thanks for your help. Fred DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Parsing properties
Hi everyone, Let's say that I have a registry key HKLM\Software\MyProduct with a String value "TheDir" = "c:\program files\My product\module" I can easily get the value by using a RegistrySearch: Here's the question: :) Is there a way to extract a substring from the retrieved value i.e. The value in the registry is "c:\program files\My product\module", and I would like to set MYPROP to "c:\program files\My product" (get rid of the trailing "module") Thanks for your help. Fred - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] InstallDir is lost on minor upgrade
Johan Appelgren a écrit : > On Tue, Jul 1, 2008 at 10:07 AM, Frédéric Viollet > <[EMAIL PROTECTED]> wrote: > >> Hi everyone, >> >> I've got a real big problem here on applying minor upgrades to my >> product. I really need your help here :) >> During the first install, I ask the user where the product should be >> installed (by using the wix standard Gui) >> But on minor upgrades, I do not ask him again. I just re-install the >> files to the previously selected location (well, that's what I'd like to do) >> I seem to have some problems with the property that points to my >> installation directory. >> Here's an extraction of the code I'm using: >> >> >> >> >> >> >> >>> Key="Software\MyCompany\MyProduct\MySuite\MyModule"> >> > Value="[SUITEINSTALLDIR]MyModule" Type="string" Action="write" /> >> >>. Install a bunch of files >> >> >> >> >> >> >> >> >> >> >> Now, let's say that the default ProgramFilesFolder is C:\Program Files\ >> On the first installation, the installdir is ask for. I enter F:\Program >> Files\MyCompany\MyProduct\MySuite *(and not C:)*. Everything works well : >> -the files are installed in F:\Program Files\MyCompany\MyProduct\MySuite >> -the registry value "InstallDir" is set to F:\Program >> Files\MyCompany\MyProduct\MySuite\MyModule >> >> On a minor upgrade, no installation dir is ask for (this is ok), and the >> new files are correctly copied to F:\Program >> Files\MyCompany\MyProduct\MySuite, but : >> -the registry value "InstallDir" is set to *C::\Program >> Files\MyCompany\MyProduct\MySuite\MyModule* >> >> Any idea of how I could fix this? >> >> Thanks a lot for your patience for reading all way down here :) >> >> Fred >> > > I think you must set the SUITEINSTALLDIR property using a RegistrySearch. > http://wix.sourceforge.net/manual-wix2/wix_xsd_registrysearch.htm > Ok. I will try this. The code should look like this then I guess: | snip snip | But, will this work on first install (the registry key will not be found)? Will the SUITEINSTALLDIR Property have a default value? > Why is the InstallDir registry value the KeyPath for all your files? > Normally you have one component per .exe, .dll, .ocx and so on with > the file as KeyPath. > My fault. The extracted code was incomplete. There was a missing after the Registry entries :) Thanks again for your help. Fred - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] InstallDir is lost on minor upgrade
Hi everyone, I've got a real big problem here on applying minor upgrades to my product. I really need your help here :) During the first install, I ask the user where the product should be installed (by using the wix standard Gui) But on minor upgrades, I do not ask him again. I just re-install the files to the previously selected location (well, that's what I'd like to do) I seem to have some problems with the property that points to my installation directory. Here's an extraction of the code I'm using: . Install a bunch of files Now, let's say that the default ProgramFilesFolder is C:\Program Files\ On the first installation, the installdir is ask for. I enter F:\Program Files\MyCompany\MyProduct\MySuite *(and not C:)*. Everything works well : -the files are installed in F:\Program Files\MyCompany\MyProduct\MySuite -the registry value "InstallDir" is set to F:\Program Files\MyCompany\MyProduct\MySuite\MyModule On a minor upgrade, no installation dir is ask for (this is ok), and the new files are correctly copied to F:\Program Files\MyCompany\MyProduct\MySuite, but : -the registry value "InstallDir" is set to *C::\Program Files\MyCompany\MyProduct\MySuite\MyModule* Any idea of how I could fix this? Thanks a lot for your patience for reading all way down here :) Fred - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] not executing custom actions on uninstall
Bob Arnson a écrit : Frédéric Viollet wrote: Could someone please tell me which condition I should use to trigger a custom action only on installations (initial installation and minor upgrades). This custom action must not be run on uninstall. See http://msdn.microsoft.com/en-us/library/aa368561(VS.85).aspx. Ok, thanks. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] not executing custom actions on uninstall
Hi, Could someone please tell me which condition I should use to trigger a custom action only on installations (initial installation and minor upgrades). This custom action must not be run on uninstall. Thanks a lot. Fred - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] custom actions and merge modules
Hi, I have a package in which the MFC and MSVCRT runtime libraries are needed. So I decided to use Microsoft's merge modules... so far so good... The problem is that I have a custom action that calls an executable which needs these MFC and Runtime libraries to be installed. I'm calling the custom action in the following way : NOT Installed It seems (am I wrong) that the 'rclPwdInput.exe won't start because the merge modules haven't been installed yet. The merge modules are inserted in the package through: Are the merge modules installed after 'StartServices'? PS : I really need to use the MFC DLLs. I cannot link the executable statically... Is there a way to get out of this? Thanks Fred - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] adding a component on a minor upgrade
Bob Arnson a écrit : > Frédéric Viollet wrote: >> The problem is that, according to the MSDN, REINSTALL=ALL only >> reinstalls the previously installed features. So I am not able to add >> new features on a minor upgrade. >> > > You need to install new features using the ADDLOCAL property. Can the ADDLOCAL property be used in the feature definition? Or does it have to be specified on the command line? > >> However, contrary to what I thought, I *am* able to add new >> components to an existing (installed) feature. > > Yes, but see Heath's blog posts on this issue: > > http://blogs.msdn.com/heaths/archive/2008/02/18/adding-new-components-to-existing-features-installs-the-feature-tree.aspx > > > http://blogs.msdn.com/heaths/archive/2008/02/19/another-workaround-to-add-new-components-to-existing-features.aspx > > Yes indeed. I found these links while trying to find an explanation to my problem. But this isn't really a problem in my case, because I only have one feature and all the components of the feature must be installed. Fred - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] adding a component on a minor upgrade
Hi Lincoln, I went a little further in my investigations. You were right for the arguments used during the minor upgrade I'm using the Wix bootstrapper (setupbld) to deal with these installation/upgrade issues. And the bootstrapper sets the REINSTALL=ALL REINSTALLMODE="vomus" flags for a minor upgrade. The problem is that, according to the MSDN, REINSTALL=ALL only reinstalls the previously installed features. So I am not able to add new features on a minor upgrade. However, contrary to what I thought, I *am* able to add new components to an existing (installed) feature. The reason why my upgrade failed was that another component had also been removed. I wasn't aware of this removal and, removing a component on a minor upgrade *is* clearly forbidden. I've set the MSIENFORCEUPGRADECOMPONENTRULES property on, so that this kind of surprise won't happen again So I'll have to go through a major upgrade this time, but minor upgrades will do the trick next time. Thanks to all of you for following my problem. Fred Lincoln Y Lavoie a écrit : > Hi Fredrick, > > I'm going to guess it may have something to do with the arguments for > the msiexec on the minor update. The arguments specify things like, > replace files only if..., etc. I would make sure there isn't one that > specifies to add files/features not previously present. > > Cheers, > Lincoln > > Frédéric Viollet wrote: >> Hi Rob, >> Thanks for your answer. >> Now I'm trying to add my new Component in a new Feature. >> The problem is that I can't figure out where to add my Feature. >> At the moment, I have only one Feature, and this Feature should >> always be installed. >> The Feature I'd like to add should also always be installed. >> I tried adding it as a new Feature at the same level as the first >> Feature, and I also tried adding it as a new leaf in the first Feature. >> None of these configurations get my new feature to be installed. It >> seems that I can't install the new Feature. >> Here are the confs I tried: >> >> #1: >> >> <. a bunch of existing components > >> >> >> >> >> >> #2: >> >> <. a bunch of existing components > >> >> >> >> >> >> Any ideas? >> >> Thanks again for your help. >> >> Fred >> >> Rob Mensching a écrit : >> >>> I think the MSI SDK on "Minor Upgrades" confirms your observations: >>> >>> A minor upgrade can be used to add new features and >>> components but cannot reorganize the feature-component tree. >>> >>> You'll need to add the new Components to a new Feature. >>> >>> >>> -Original Message- >>> From: [EMAIL PROTECTED] >>> [mailto:[EMAIL PROTECTED] On Behalf Of >>> Frédéric Viollet >>> Sent: Thursday, April 24, 2008 06:30 >>> To: wix-users@lists.sourceforge.net >>> Subject: [WiX-users] adding a component on a minor upgrade >>> >>> Hi everyone, >>> >>> Is it possible to add a component to an installed feature through a >>> minor upgrade? >>> The component I'm trying to add contains two files. And it seems, by >>> the >>> behavior I'm experiencing, that the answer is *no*. >>> Could someone confirm this? >>> >>> Point #1: The product, to which I'd like to add a component, upgrades >>> well if I don't add the component... >>> >>> Point #2: If I try to add the component, I get the following behavior: >>> the product upgrades without apparent errors. However, none of the >>> files >>> are updated, the "Add/Remove Programs" is updated with the new version >>> name. And when I try to uninstall the upgraded version, the entry in >>> "Add/Remove Programs" is removed *but* none of the files/services are >>> removed. >>> >>> Point #3: Strangely, I have another product in which I already had >>> added >>> a Component in an installed feature without any problem. The only >>> difference, is that the component I added only contained any entry >>> (no Files) >>> >>> Thanks for your help. >>> >>> Fred >>> >>> - >>> >>> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference >>> Don't miss this year's exciting event. There's sti
Re: [WiX-users] adding a component on a minor upgrade
News again The error 2771 was indeed my fault. So please don't pay attention to last message I posted. But with packages that do not raise the 2771 error, I still can't add a new feature with a new component :( Fred Frédéric Viollet a écrit : > Hi, > > I've done some other tests and added the MSIENFORCEUPGRADECOMPONENTRULES > property in my wxs file. > The results are quite surprising. > In both of the configurations listed below I get the error 2771: > The MSDN says that it means: "Upgrade of feature [2] has a missing > component. ." > I don't understand this message since none of the existing components > have been removed. > I'm only trying to add a new component in a new feature :( > > I'm really lost. :( > > Fred > > Frédéric Viollet a écrit : > >> Hi Rob, >> Thanks for your answer. >> Now I'm trying to add my new Component in a new Feature. >> The problem is that I can't figure out where to add my Feature. >> At the moment, I have only one Feature, and this Feature should always >> be installed. >> The Feature I'd like to add should also always be installed. >> I tried adding it as a new Feature at the same level as the first >> Feature, and I also tried adding it as a new leaf in the first Feature. >> None of these configurations get my new feature to be installed. It >> seems that I can't install the new Feature. >> Here are the confs I tried: >> >> #1: >> >> <. a bunch of existing components > >> >> >> >> >> >> #2: >> >> <. a bunch of existing components > >> >> >> >> >> >> Any ideas? >> >> Thanks again for your help. >> >> Fred >> >> Rob Mensching a écrit : >> >> >>> I think the MSI SDK on "Minor Upgrades" confirms your observations: >>> >>> A minor upgrade can be used to add new features and components but >>> cannot reorganize the feature-component tree. >>> >>> You'll need to add the new Components to a new Feature. >>> >>> >>> -Original Message- >>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frédéric >>> Viollet >>> Sent: Thursday, April 24, 2008 06:30 >>> To: wix-users@lists.sourceforge.net >>> Subject: [WiX-users] adding a component on a minor upgrade >>> >>> Hi everyone, >>> >>> Is it possible to add a component to an installed feature through a >>> minor upgrade? >>> The component I'm trying to add contains two files. And it seems, by the >>> behavior I'm experiencing, that the answer is *no*. >>> Could someone confirm this? >>> >>> Point #1: The product, to which I'd like to add a component, upgrades >>> well if I don't add the component... >>> >>> Point #2: If I try to add the component, I get the following behavior: >>> the product upgrades without apparent errors. However, none of the files >>> are updated, the "Add/Remove Programs" is updated with the new version >>> name. And when I try to uninstall the upgraded version, the entry in >>> "Add/Remove Programs" is removed *but* none of the files/services are >>> removed. >>> >>> Point #3: Strangely, I have another product in which I already had added >>> a Component in an installed feature without any problem. The only >>> difference, is that the component I added only contained any entry >>> (no Files) >>> >>> Thanks for your help. >>> >>> Fred >>> >>> - >>> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference >>> Don't miss this year's exciting event. There's still time to save $100. >>> Use priority code J8TL2D2. >>> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone >>> ___ >>> WiX-users mailing list >>> WiX-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wix-users >>> >>> >>> >>> >> - >> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference >> Don't miss this year's exciting event. There's still
Re: [WiX-users] adding a component on a minor upgrade
Hi, I've done some other tests and added the MSIENFORCEUPGRADECOMPONENTRULES property in my wxs file. The results are quite surprising. In both of the configurations listed below I get the error 2771: The MSDN says that it means: "Upgrade of feature [2] has a missing component. ." I don't understand this message since none of the existing components have been removed. I'm only trying to add a new component in a new feature :( I'm really lost..... :( Fred Frédéric Viollet a écrit : > Hi Rob, > Thanks for your answer. > Now I'm trying to add my new Component in a new Feature. > The problem is that I can't figure out where to add my Feature. > At the moment, I have only one Feature, and this Feature should always > be installed. > The Feature I'd like to add should also always be installed. > I tried adding it as a new Feature at the same level as the first > Feature, and I also tried adding it as a new leaf in the first Feature. > None of these configurations get my new feature to be installed. It > seems that I can't install the new Feature. > Here are the confs I tried: > > #1: > > <. a bunch of existing components > > > > > > > #2: > > <. a bunch of existing components > > > > > > > Any ideas? > > Thanks again for your help. > > Fred > > Rob Mensching a écrit : > >> I think the MSI SDK on "Minor Upgrades" confirms your observations: >> >> A minor upgrade can be used to add new features and components but >> cannot reorganize the feature-component tree. >> >> You'll need to add the new Components to a new Feature. >> >> >> -Original Message- >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frédéric >> Viollet >> Sent: Thursday, April 24, 2008 06:30 >> To: wix-users@lists.sourceforge.net >> Subject: [WiX-users] adding a component on a minor upgrade >> >> Hi everyone, >> >> Is it possible to add a component to an installed feature through a >> minor upgrade? >> The component I'm trying to add contains two files. And it seems, by the >> behavior I'm experiencing, that the answer is *no*. >> Could someone confirm this? >> >> Point #1: The product, to which I'd like to add a component, upgrades >> well if I don't add the component... >> >> Point #2: If I try to add the component, I get the following behavior: >> the product upgrades without apparent errors. However, none of the files >> are updated, the "Add/Remove Programs" is updated with the new version >> name. And when I try to uninstall the upgraded version, the entry in >> "Add/Remove Programs" is removed *but* none of the files/services are >> removed. >> >> Point #3: Strangely, I have another product in which I already had added >> a Component in an installed feature without any problem. The only >> difference, is that the component I added only contained any entry >> (no Files) >> >> Thanks for your help. >> >> Fred >> >> - >> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference >> Don't miss this year's exciting event. There's still time to save $100. >> Use priority code J8TL2D2. >> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >> > > > - > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] adding a component on a minor upgrade
Hi Rob, Thanks for your answer. Now I'm trying to add my new Component in a new Feature. The problem is that I can't figure out where to add my Feature. At the moment, I have only one Feature, and this Feature should always be installed. The Feature I'd like to add should also always be installed. I tried adding it as a new Feature at the same level as the first Feature, and I also tried adding it as a new leaf in the first Feature. None of these configurations get my new feature to be installed. It seems that I can't install the new Feature. Here are the confs I tried: #1: <. a bunch of existing components > #2: <. a bunch of existing components > Any ideas? Thanks again for your help. Fred Rob Mensching a écrit : > I think the MSI SDK on "Minor Upgrades" confirms your observations: > > A minor upgrade can be used to add new features and components but > cannot reorganize the feature-component tree. > > You'll need to add the new Components to a new Feature. > > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frédéric > Viollet > Sent: Thursday, April 24, 2008 06:30 > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] adding a component on a minor upgrade > > Hi everyone, > > Is it possible to add a component to an installed feature through a > minor upgrade? > The component I'm trying to add contains two files. And it seems, by the > behavior I'm experiencing, that the answer is *no*. > Could someone confirm this? > > Point #1: The product, to which I'd like to add a component, upgrades > well if I don't add the component... > > Point #2: If I try to add the component, I get the following behavior: > the product upgrades without apparent errors. However, none of the files > are updated, the "Add/Remove Programs" is updated with the new version > name. And when I try to uninstall the upgraded version, the entry in > "Add/Remove Programs" is removed *but* none of the files/services are > removed. > > Point #3: Strangely, I have another product in which I already had added > a Component in an installed feature without any problem. The only > difference, is that the component I added only contained any entry > (no Files) > > Thanks for your help. > > Fred > > - > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] adding a component on a minor upgrade
Hi everyone, Is it possible to add a component to an installed feature through a minor upgrade? The component I'm trying to add contains two files. And it seems, by the behavior I'm experiencing, that the answer is *no*. Could someone confirm this? Point #1: The product, to which I'd like to add a component, upgrades well if I don't add the component... Point #2: If I try to add the component, I get the following behavior: the product upgrades without apparent errors. However, none of the files are updated, the "Add/Remove Programs" is updated with the new version name. And when I try to uninstall the upgraded version, the entry in "Add/Remove Programs" is removed *but* none of the files/services are removed. Point #3: Strangely, I have another product in which I already had added a Component in an installed feature without any problem. The only difference, is that the component I added only contained any entry (no Files) Thanks for your help. Fred - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] removing an existing product
I've just found out how to manage this. I changed ProductId, UpgradeCode (and UpgradeId). Then I added an Upgrade entry with the old UpgradeCode (and I also removed the OnlyDetect attribute). Everything works fine now! Thanks anyway :) Fred Frédéric Viollet a écrit : > Oups...! > My mistake : changing the productId *does* trigger a new installation > (from scratch ... asking for install dir and all that) *but* my previous > version is not removed... > Any idea? > > Thanks again. > > Fred > > Frédéric Viollet a écrit : > >> Hi everyone, >> >> I've changed a lot of things (files and directories) in my application, >> and I'd like to remove any previously installed version of the product >> before installing the new one. >> Here's the situation >> previous version of my product had the following items in the wxs: >> >> >UpgradeCode='F0B9C286-DA33-7842-A4FD-91F34F02D6B4' >>Language='1033' >>Manufacturer='MyCompany' >>Name="Console 8.0." >>Version="8.0..0"> >> > InstallerVersion="300" /> >> >> > IncludeMinimum='yes' Minimum='8.0.001' /> >> >> >> >> >> >> >> New version's have the following items in the wxs: >> >> >UpgradeCode='F0B9C286-DA33-7842-A4FD-91F34F02D6B4' >>Language='1033' >>Manufacturer='MyCompany' >>Name="Console 8.01." >>Version="8.01..0"> >> > Compressed='yes' InstallerVersion="300" /> >> >> > IncludeMinimum='yes' Minimum='8.0.001' /> >> >> >> >> >> >> >> As you can see, I've changed the ProductId, but left the UpgradeId >> unchanged. But this doesn't work. It still is recognized as a minor upgrade. >> Since a lot of things have changed in my new packaging, many components >> have either been removed or added to the wxs. GUIDs have changed to. >> >> What would be, in you opinion, the best way to achieve what I'm trying >> to do? i.e. remove previous versions (all 8.0.abcd.0 versions) before >> starting a new installation (during this new installation, I'll need to >> ask the user an installation directory. This is a thing I don't do >> during upgrades. So I really need this new installation to be considered >> as an installation from scratch). >> >> Thanks for your help. >> >> Fred >> >> - >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >> > > > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] removing an existing product
Oups...! My mistake : changing the productId *does* trigger a new installation (from scratch ... asking for install dir and all that) *but* my previous version is not removed... Any idea? Thanks again. Fred Frédéric Viollet a écrit : > Hi everyone, > > I've changed a lot of things (files and directories) in my application, > and I'd like to remove any previously installed version of the product > before installing the new one. > Here's the situation > previous version of my product had the following items in the wxs: > > UpgradeCode='F0B9C286-DA33-7842-A4FD-91F34F02D6B4' >Language='1033' >Manufacturer='MyCompany' >Name="Console 8.0." >Version="8.0..0"> > InstallerVersion="300" /> > >IncludeMinimum='yes' Minimum='8.0.001' /> > > > > > > > New version's have the following items in the wxs: > > UpgradeCode='F0B9C286-DA33-7842-A4FD-91F34F02D6B4' >Language='1033' >Manufacturer='MyCompany' >Name="Console 8.01." >Version="8.01..0"> > Compressed='yes' InstallerVersion="300" /> > >IncludeMinimum='yes' Minimum='8.0.001' /> > > > > > > > As you can see, I've changed the ProductId, but left the UpgradeId > unchanged. But this doesn't work. It still is recognized as a minor upgrade. > Since a lot of things have changed in my new packaging, many components > have either been removed or added to the wxs. GUIDs have changed to. > > What would be, in you opinion, the best way to achieve what I'm trying > to do? i.e. remove previous versions (all 8.0.abcd.0 versions) before > starting a new installation (during this new installation, I'll need to > ask the user an installation directory. This is a thing I don't do > during upgrades. So I really need this new installation to be considered > as an installation from scratch). > > Thanks for your help. > > Fred > > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] removing an existing product
Hi everyone, I've changed a lot of things (files and directories) in my application, and I'd like to remove any previously installed version of the product before installing the new one. Here's the situation previous version of my product had the following items in the wxs: New version's have the following items in the wxs: As you can see, I've changed the ProductId, but left the UpgradeId unchanged. But this doesn't work. It still is recognized as a minor upgrade. Since a lot of things have changed in my new packaging, many components have either been removed or added to the wxs. GUIDs have changed to. What would be, in you opinion, the best way to achieve what I'm trying to do? i.e. remove previous versions (all 8.0.abcd.0 versions) before starting a new installation (during this new installation, I'll need to ask the user an installation directory. This is a thing I don't do during upgrades. So I really need this new installation to be considered as an installation from scratch). Thanks for your help. Fred - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] log file and setupbld
Frédéric Viollet a écrit : > Hi everyone, > > I'm using the setupbld tool to generate exe files from my msi files and > this is working pretty well. > I was wondering, though, how could I do to send the "/log" command to > the msi > I tried > "mysetup.exe /msicl "log c:\temp\msi.log" > "mysetup.exe /msicl "/log c:\temp\msi.log" > but none one the two above attemps succeeded :( > > I thought, by looking at the code, that msicl could by used to pass > additional commands to the msi... am I wrong? > > Thanks a lot for your help. > > Does anybody have an idea? Thanks Fred - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] log file and setupbld
Hi everyone, I'm using the setupbld tool to generate exe files from my msi files and this is working pretty well. I was wondering, though, how could I do to send the "/log" command to the msi I tried "mysetup.exe /msicl "log c:\temp\msi.log" "mysetup.exe /msicl "/log c:\temp\msi.log" but none one the two above attemps succeeded :( I thought, by looking at the code, that msicl could by used to pass additional commands to the msi... am I wrong? Thanks a lot for your help. Fred - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] building wix
Bob Arnson a écrit : Frédéric Viollet wrote: C:\temp\wix-3.0.2925.0-sources>make.bat ship Please try a weekly release from http://wix.sourceforge.net/releases/ or a CVS checkout. Hi Bob, Thanks again for replying. -I tried from a CVS checkout, I got the following error: c:\temp\wix_cvs\wix.build(64,4): Build file 'C:\temp\wix_cvs\tests\vstests\vstests.build' does not exist. -I tried from the weekly release sources, I got errors telling that some files were missing (mergemod.cub, mergemod.dll, etc) -I finally found these files in the binary distribution. I tried from the weekly release sources after copying the files above, I got the following error: 71 errors, all about missing references... because Nant.Core could not be found. :) Is there a way to build Wix? Thanks again. Fred PS : I quite of join Dominik Guders message on building Wix without a CVS connection. I'm behind a firewall that prevents me from accessing Wix's CVS repository and building Wix from weekly release sources seems to be tricky since you have to copy some files from another place :( Is it really not possible to include all files in the source distribution so that building wix can be automated in a production environment? begin:vcard fn;quoted-printable:Fr=C3=A9d=C3=A9ric Viollet n;quoted-printable:Viollet;Fr=C3=A9d=C3=A9ric org:Bull, Architect of an Open World (TM);Evidian S.A. adr;quoted-printable:;;Rue Jean Jaur=C3=A8s;Les Clayes Sous Bois;;78340;France email;internet:[EMAIL PROTECTED] title:Software Engineer tel;work:01 30 80 77 34 url:http://www.evidian.com - http://www.bull.com version:2.1 end:vcard - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] building wix
Hi everyone,
I'm encoutering some problems while trying to build Wix v3 with nant
I get the following error message:
C:\temp\wix-3.0.2925.0-sources>make.bat ship
NAnt 0.85 (Build 0.85.2478.0; release; 14/10/2006)
Copyright (C) 2001-2006 Gerry Shaw
http://nant.sourceforge.net
Buildfile: file:///C:/temp/wix-3.0.2925.0-sources//wix.build
Target framework: Microsoft .NET Framework 2.0
Target(s) specified: inc
[property] Target framework changed to "Microsoft .NET Framework 1.1".
BUILD FAILED
C:\temp\wix-3.0.2925.0-sources\wix.include(10,4):
Property evaluation failed.
Expression: ${file.global.include}
^^^
Property 'file.global.include' has not been set.
Total time: 0.1 seconds.
Does anyone have an idea?
Thanks for your help.
Fred
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] batch and custom actions
Hi everyone, I'm launching a .bat file through a custom action. Everything works well except that I can see in the background (very quickly, because the batch doesn't do much) a cmd window executing the batch file. My question : is there a way to tell that the cmd window should be hidden during the batch execution? Thanks for your help. Fred - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WixV3 and light's -b flag
Hi everyone, I'm trying to use a custom Eula.rtf file for the LicenseAgreementDlg dialog. So I added the -dWixUILicenseRtf=Eula.rtf flag to my light command line and I also added a -b with the base path to my Eula.rtf file. The linker fails with the following error : LicenseAgreementDlg.wxs(28) : error LGHT0103 : The system cannot find the file 'Eula.rtf'. I saw this bug had already been fixed in WixV2. Is it planned to be fixed in WixV3 soon? My Wix version is : 3.0.2420.0 Thanks a lot. Fred - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] setupbld
Bob Arnson a écrit : > Frédéric Viollet wrote: >> Ok. I've just had a look at setupbld source code. And it seems that >> REINSTALLMODE is set to vomus for a minor upgrade. >> I guess I need it to be set to vamus to force all files to be >> rewritten. Is there another bootstrapper that would allow me to >> achieve this? > > SetupExe isn't currently configurable for that. > Do you know another bootstrapper that would allow me to do this? Thanks - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] setupbld
Frédéric Viollet a écrit : Bob Arnson a écrit : Frédéric Viollet wrote: When I perform a minor upgrade of my product using the generated executable file, not all of the files are upgraded. Only the files that have changed are updated. I thought that even on a minor upgrade, all the files for the installed components would be upgraded (even if they haven't changed). That's controlled by the settings in REINSTALLMODE. The REINSTALLMODE options are set by the bootstrapper, aren't they? I'm using the setupbld bootstrapper with the "mcpsu" options. Does this seem correct? Thanks again. Fred Ok. I've just had a look at setupbld source code. And it seems that REINSTALLMODE is set to vomus for a minor upgrade. I guess I need it to be set to vamus to force all files to be rewritten. Is there another bootstrapper that would allow me to achieve this? Thanks again. Fred begin:vcard fn;quoted-printable:Fr=C3=A9d=C3=A9ric Viollet n;quoted-printable:Viollet;Fr=C3=A9d=C3=A9ric org:Bull, Architect of an Open World (TM);Evidian S.A. adr;quoted-printable:;;Rue Jean Jaur=C3=A8s;Les Clayes Sous Bois;;78340;France email;internet:[EMAIL PROTECTED] title:Software Engineer tel;work:01 30 80 77 34 url:http://www.evidian.com - http://www.bull.com version:2.1 end:vcard - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] setupbld
Bob Arnson a écrit : > Frédéric Viollet wrote: >> When I perform a minor upgrade of my product using the generated >> executable file, not all of the files are upgraded. Only the files >> that have changed are updated. >> I thought that even on a minor upgrade, all the files for the >> installed components would be upgraded (even if they haven't changed). > > That's controlled by the settings in REINSTALLMODE. > The REINSTALLMODE options are set by the bootstrapper, aren't they? I'm using the setupbld bootstrapper with the "mcpsu" options. Does this seem correct? Thanks again. Fred - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] setupbld
Hi all, I have a question about the setupbld.exe tool. I'm using this tool in WixV3 with the mcpsu options and I've noticed some strange behaviour. When I perform a minor upgrade of my product using the generated executable file, not all of the files are upgraded. Only the files that have changed are updated. I thought that even on a minor upgrade, all the files for the installed components would be upgraded (even if they haven't changed). If this is the normal behaviour, is there a way to force all files to be upgraded? By the way, I see that the files have not been updated because the timestamps don't change on upgrade... maybe my test is not right. Thanks for your help. Fred begin:vcard fn;quoted-printable:Fr=C3=A9d=C3=A9ric Viollet n;quoted-printable:Viollet;Fr=C3=A9d=C3=A9ric org:Bull, Architect of an Open World (TM);Evidian S.A. adr;quoted-printable:;;Rue Jean Jaur=C3=A8s;Les Clayes Sous Bois;;78340;France email;internet:[EMAIL PROTECTED] title:Software Engineer tel;work:01 30 80 77 34 url:http://www.evidian.com - http://www.bull.com version:2.1 end:vcard - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Silent install won't copy in files
I haven't tried this out, maybe other contributors will correct me. But I think you can use any property between square brackets in DestinationDirectory. Square brackets make the property to be evaluated. The difference is between DestinationProperty and DestinationDirectory would be: DestinationProperty=MyProperty DestinationDirectory=[MyProperty] Maybe I'm wrong, but I understand that DestinationProperty waits for a single property to contain the whole destination path. Have you tried using DestinationDirectory? Mike Menaker a écrit : I don't think I can use [ProgramFilesFolder] with DestinationDirectory -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frédéric Viollet Sent: Monday, September 17, 2007 12:14 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Silent install won't copy in files Mike Menaker a écrit : Hi, I'm having a problem with a silent install. I have a component that copies 2 files and writes to the registry however it isn't copying the 3 files correctly (yet writing the registry correctly). This is my component. Guid="49861A79-A034-4e15-BA38-783D2FCC4D90"> DestinationProperty="[ProgramFilesFolder]Test\Config\" /> DestinationProperty="[ProgramFilesFolder]Test\Config\" /> Type='string' Value='[ProgramFilesFolder]Test\license_manager\license\test.lic' /> Any ideas why it isn't copying in the files correctly? Thanks, Mike You are using the DestinationProperty attribute in the CopyFile element. Try using DestinationDirectory instead. Fred begin:vcard fn;quoted-printable:Fr=C3=A9d=C3=A9ric Viollet n;quoted-printable:Viollet;Fr=C3=A9d=C3=A9ric org:Bull, Architect of an Open World (TM);Evidian S.A. adr;quoted-printable:;;Rue Jean Jaur=C3=A8s;Les Clayes Sous Bois;;78340;France email;internet:[EMAIL PROTECTED] title:Software Engineer tel;work:01 30 80 77 34 url:http://www.evidian.com - http://www.bull.com version:2.1 end:vcard - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Silent install won't copy in files
Mike Menaker a écrit : Hi, I’m having a problem with a silent install. I have a component that copies 2 files and writes to the registry however it isn’t copying the 3 files correctly (yet writing the registry correctly). This is my component. Guid="49861A79-A034-4e15-BA38-783D2FCC4D90"> DestinationProperty="[ProgramFilesFolder]Test\Config\" /> DestinationProperty="[ProgramFilesFolder]Test\Config\" /> Type='string' Value='[ProgramFilesFolder]Test\license_manager\license\test.lic' /> Any ideas why it isn’t copying in the files correctly? Thanks, Mike You are using the DestinationProperty attribute in the CopyFile element. Try using DestinationDirectory instead. Fred begin:vcard fn;quoted-printable:Fr=C3=A9d=C3=A9ric Viollet n;quoted-printable:Viollet;Fr=C3=A9d=C3=A9ric org:Bull, Architect of an Open World (TM);Evidian S.A. adr;quoted-printable:;;Rue Jean Jaur=C3=A8s;Les Clayes Sous Bois;;78340;France email;internet:[EMAIL PROTECTED] title:Software Engineer tel;work:01 30 80 77 34 url:http://www.evidian.com - http://www.bull.com version:2.1 end:vcard - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] condition onl component
Ok. This isn't really the behavior I'm looking for. I managed to solve my problem by using Components with empty GUIDs to install and modify the config files. In that way, the component is not managed. Since it cannot be updated or removed, my config files are not overwritten on upgrades any more. And I manage the remove part with RemoveFile elements. Thanks for your help. Fred Stefan Krueger [MVP] a écrit : > I'm not sure about the WiX syntax but in MSI terms: if the component > condition evaluates to FALSEthe component will NOT be installed. And if it > was True in the first time install and then becomes False in the upgrade, > that component will be REMOVED - but only if the component has the > transitive flag set. Otherwise the condition willö not be re-evaluated. > > - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] sequence question...
Hi, I've got a new question for the community. Could someone tell me if the element is called before or after the action Thanks in advance for your help. Fred - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] condition onl component
Does nobody have a clue? I'm really sorry to insist on my problem, but it's getting quite a critical issue :( Thanks again for your help. Frédéric Viollet a écrit : > Stefan Krueger [MVP] a écrit : > >> So you only want to condition the copy (which corresponds to a MoveFile >> table row I guess) but not the instalaltion of the component. To do this you >> need to put the copy element in a separate component, because rows in the >> MoveFile table can't have conditions by themselves, instead they use >> components as a "gate". >> >> >> > I tried this out as well. With no success... > My problem is really to affect a condition to a component. > It seems that whether my condition is full filed or not, the component > is upgraded in both cases. > > This is what my code looks like: > > >Key='SOFTWARE\MyProduct\Engine' Name='InstallDir' Type='directory'> > > > > > > > Guid="4C6B380E-4DFE-458C-A29F-8A0C434E7F70"> > ENGINECONFISINSTALLED >Source="$(var.FACT_DESTDIR)\var\config\ampm_engine.ref"> > DestinationName="amengine.ini" DestinationLongName="ampm_engine.ini" /> > >Name="ampm_engine.ini" Section="NETWORK" Key="Port" Value="[PORTNUMBER]" /> > > > I thought that the upper code would allow me to perform the component's > tasks only if ENGINECONFISINSTALLED was false (that would be on a first > install). > What I'm trying to do is condition the whole APM_ENGINE_CONFIG_REF > component. But I can't : whatever I put as a condition, the component > tasks are executed (on first install AND on upgrade) > I must be doing something wrong here, but I can't find out what... > > Thanks for your help. > > Fred > > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] condition onl component
Stefan Krueger [MVP] a écrit : > So you only want to condition the copy (which corresponds to a MoveFile > table row I guess) but not the instalaltion of the component. To do this you > need to put the copy element in a separate component, because rows in the > MoveFile table can't have conditions by themselves, instead they use > components as a "gate". > > I tried this out as well. With no success... My problem is really to affect a condition to a component. It seems that whether my condition is full filed or not, the component is upgraded in both cases. This is what my code looks like: ENGINECONFISINSTALLED I thought that the upper code would allow me to perform the component's tasks only if ENGINECONFISINSTALLED was false (that would be on a first install). What I'm trying to do is condition the whole APM_ENGINE_CONFIG_REF component. But I can't : whatever I put as a condition, the component tasks are executed (on first install AND on upgrade) I must be doing something wrong here, but I can't find out what... Thanks for your help. Fred - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] condition onl component
Stefan Krueger [MVP] a écrit : > The component must have the msidbComponentAttributesTransitive bit set > (don't know the WiX syntax for this). This should remove the component > during (auto-)repair, modify and small and minor updates - probably not what > you want. BTW in case of Major Upgrade, Installed is FALSE. > I don't fully undertsand what you are trying to achieve, bt maybe > msidbComponentAttributesNeverOverwrite would do what you want. > > In fact, what I'm trying to do is: -on first install, install the file engine.ref and copy it to engine.ini -on upgrades, only install the file engine.ref, but don't touch to the engine.ini file. I was trying to achieve this through the condition element, but I just can make it work... :( Thanks again. Fred - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] condition onl component
Hi everybody, I have some problems while updating a product through Wix v3 I've written the following code : NOT Installed But, even on update, the file amengine.ref is copied to amengine.ini Any idea? Thanks for your help. Fred - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] force upgrade
Bob Arnson a écrit : > Frédéric Viollet wrote: >> product's version is already installed, nothing happens. There isn't >> even a notification to tell that the installation won't start because >> the product is already up to date. What I would like is start the >> installation process even if I'm trying to install the same version. >> > > The current version of WiX's setup.exe doesn't support that. > Ok, thanks. Will this feature be supported in a future release? Fred - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] force upgrade
I forgot to say : I'm using WixV3 3.0.2420.0 Frédéric Viollet a écrit : Hi everyone, is there a way to force an upgrade even if the version I'm want to install is already installed? I'm using the bootstrapping possibility offered by Wix to generate a executable file (setupbld). The options I use are "mcpsu". At the moment, if I double click on the setup file and that the product's version is already installed, nothing happens. There isn't even a notification to tell that the installation won't start because the product is already up to date. What I would like is start the installation process even if I'm trying to install the same version. Is this possible? Thanks for your help. Fred - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users begin:vcard fn;quoted-printable:Fr=C3=A9d=C3=A9ric Viollet n;quoted-printable:Viollet;Fr=C3=A9d=C3=A9ric org:Bull, Architect of an Open World (TM);Evidian S.A. adr;quoted-printable:;;Rue Jean Jaur=C3=A8s;Les Clayes Sous Bois;;78340;France email;internet:[EMAIL PROTECTED] title:Software Engineer tel;work:01 30 80 77 34 url:http://www.evidian.com - http://www.bull.com version:2.1 end:vcard - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] force upgrade
Hi everyone, is there a way to force an upgrade even if the version I'm want to install is already installed? I'm using the bootstrapping possibility offered by Wix to generate a executable file (setupbld). The options I use are "mcpsu". At the moment, if I double click on the setup file and that the product's version is already installed, nothing happens. There isn't even a notification to tell that the installation won't start because the product is already up to date. What I would like is start the installation process even if I'm trying to install the same version. Is this possible? Thanks for your help. Fred - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] checking registry entry
Bob Arnson a écrit : Frédéric Viollet wrote: Guid="924B3E41-7157-4927-B892-8D52D8A392BD"> MAXHEAPSIZE AND (MAXHEAPSIZE< 256) Type="integer" Action="write" /> I get the error : Name cannot begin with the ' ' character, hexadecimal value 0x20 You can't use a "bare" < character in an XML document. You need to use CDATA or < instead. Yes indeed. I tries with CDATA, it works fine. Thanks a lot for your help. Fred begin:vcard fn;quoted-printable:Fr=C3=A9d=C3=A9ric Viollet n;quoted-printable:Viollet;Fr=C3=A9d=C3=A9ric org:Bull, Architect of an Open World (TM);Evidian S.A. adr;quoted-printable:;;Rue Jean Jaur=C3=A8s;Les Clayes Sous Bois;;78340;France email;internet:[EMAIL PROTECTED] title:Software Engineer tel;work:01 30 80 77 34 url:http://www.evidian.com - http://www.bull.com version:2.1 end:vcard - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] checking registry entry
Bob Arnson a écrit : Frédéric Viollet wrote: -During install, I'd like to check for some registry entry (a DWORD. Lets call it "myDword"). Use RegistrySearch to set a property. Ok, but what if myDword doesn't exist? What does RegistrySearch return? -If myDword doesn't exist or is inferior to a given value x, then I would like to create/set it to x. Use a custom action with a condition to write to the property, then RegistryKey/RegistryValue to write it. I tried something like this, but I get an error when compiling: Guid="924B3E41-7157-4927-B892-8D52D8A392BD"> MAXHEAPSIZE AND (MAXHEAPSIZE< 256) Type="integer" Action="write" /> I get the error : Name cannot begin with the ' ' character, hexadecimal value 0x20 Any idea? Thanks a lot. Fred begin:vcard fn;quoted-printable:Fr=C3=A9d=C3=A9ric Viollet n;quoted-printable:Viollet;Fr=C3=A9d=C3=A9ric org:Bull, Architect of an Open World (TM);Evidian S.A. adr;quoted-printable:;;Rue Jean Jaur=C3=A8s;Les Clayes Sous Bois;;78340;France email;internet:[EMAIL PROTECTED] title:Software Engineer tel;work:01 30 80 77 34 url:http://www.evidian.com - http://www.bull.com version:2.1 end:vcard - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] checking registry entry
Hi everyone, I'm looking for some good soul that could help to achieve the following steps: -During install, I'd like to check for some registry entry (a DWORD. Lets call it "myDword"). -If myDword doesn't exist or is inferior to a given value x, then I would like to create/set it to x. Could someone please help with this? I'm using Wix v3. Thanks for your help. Fred begin:vcard fn;quoted-printable:Fr=C3=A9d=C3=A9ric Viollet n;quoted-printable:Viollet;Fr=C3=A9d=C3=A9ric org:Bull, Architect of an Open World (TM);Evidian S.A. adr;quoted-printable:;;Rue Jean Jaur=C3=A8s;Les Clayes Sous Bois;;78340;France email;internet:[EMAIL PROTECTED] title:Software Engineer tel;work:01 30 80 77 34 url:http://www.evidian.com - http://www.bull.com version:2.1 end:vcard - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] customactions and installsequence
Ok. Thanks. I scheduled the action as deferred after InstallFiles (I needed the custom action to be triggered after file installation and before service start). I works fine. Thanks again for your help. Fred Mike Dimmick a écrit : Sorry, either mark as deferred and schedule between InstallInitialize and InstallFinalize, or mark as immediate and schedule after InstallFinalize. If you try to schedule a deferred action after InstallFinalize I believe you'll get a runtime error. If you use an immediate action after InstallFinalize your action cannot cause the install to roll back (because the transaction has already been committed). begin:vcard fn;quoted-printable:Fr=C3=A9d=C3=A9ric Viollet n;quoted-printable:Viollet;Fr=C3=A9d=C3=A9ric org:Bull, Architect of an Open World (TM);Evidian S.A. adr;quoted-printable:;;Rue Jean Jaur=C3=A8s;Les Clayes Sous Bois;;78340;France email;internet:[EMAIL PROTECTED] title:Software Engineer tel;work:01 30 80 77 34 url:http://www.evidian.com - http://www.bull.com version:2.1 end:vcard - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] customactions and installsequence
Ok, thanks a lot for your explanation. So if I correctly understood what you said, I must declare my custom action as deferred. So I guess I write it this way: DllEntry='apm_edit_conf' Execute='deferred' Return='check' /> NOT Installed Is the "After='InstallFiles'" still correct? Thanks again? Mike Dimmick a écrit : In effect, Windows Installer makes two passes over the actions in between InstallInitialize and InstallFinalize. In the first pass, by the client process that called MsiDoAction (which is msiexec.exe if you just ran an .msi from Explorer), the installer writes out a script for the tasks each standard action and *deferred* custom action must perform, but it doesn't actually do them yet. Any *immediate* custom actions are, as the name indicates, executed immediately when encountered. The script generated is then handed off to the Windows Installer service when the InstallFinalize action is encountered in the execute sequence. It's this script which actually installs the files. If you want to modify a file you're installing, you'll need a deferred custom action. This has the limitation that it cannot read the original database, only a special custom action data property which has the same name as the custom action, plus a few other properties (only the script is passed across to the Windows Installer service). The pattern that WiX uses is an immediate custom action that appears in the execute sequence, which reads tables to work out what to do, then schedules one or more deferred custom actions to actually do the work (passing the commands in the custom action data for the deferred actions). If you do this, be sure to set the Modified and Created timestamps to the same value, otherwise when you come to apply an upgrade, Windows Installer will think that the user has modified the file and will not overwrite it. begin:vcard fn;quoted-printable:Fr=C3=A9d=C3=A9ric Viollet n;quoted-printable:Viollet;Fr=C3=A9d=C3=A9ric org:Bull, Architect of an Open World (TM);Evidian S.A. adr;quoted-printable:;;Rue Jean Jaur=C3=A8s;Les Clayes Sous Bois;;78340;France email;internet:[EMAIL PROTECTED] title:Software Engineer tel;work:01 30 80 77 34 url:http://www.evidian.com - http://www.bull.com version:2.1 end:vcard - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] customactions and installsequence
Hi everyone. I'm using CustomActions to modify some files after installation. But I don't really understand the order in which the actions are done. In my source wxs, I have declared some elements, a , a Name="APM_WEBSERVICE" Wait="yes" Start="install" /> and some custom actions. The sequence I would like to execute is: -Install the files -Install the service -ConfigureHttpConf (custom action) -start the service To achieve this, I wrote the following code: DllEntry='apm_edit_conf' /> NOT Installed SourceFile="$(var.FACT_DESTDIR)\shared_lib\apmwsinst.dll" /> Guid="A0C7D596-6E76-493C-AA82-BD27596AB8B5"> Source="$(var.FACT_DESTDIR)\ship\httpd\bin\Apache.exe" KeyPath="yes" /> Name="APM_WEBSERVICE" Arguments="-k runservice" Type="ownProcess" Start="auto" ErrorControl="ignore" Description="IAM Policy Manager Web Service" DisplayName="IAM Policy Manager Administration WebService" Vital="no"> Name="APM_WEBSERVICE" Wait="yes" Stop="both" /> Name="APM_WEBSERVICE" Wait="yes" Remove="uninstall" /> Name="APM_WEBSERVICE" Wait="yes" Start="install" /> ... but I keep getting an error at install. The custom action fails because the file it is supposed to modify hasn't been installed yet. What am I doing wrong? Thanks for your help. Fred begin:vcard fn;quoted-printable:Fr=C3=A9d=C3=A9ric Viollet n;quoted-printable:Viollet;Fr=C3=A9d=C3=A9ric org:Bull, Architect of an Open World (TM);Evidian S.A. adr;quoted-printable:;;Rue Jean Jaur=C3=A8s;Les Clayes Sous Bois;;78340;France email;internet:[EMAIL PROTECTED] title:Software Engineer tel;work:01 30 80 77 34 url:http://www.evidian.com - http://www.bull.com version:2.1 end:vcard - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] minor Updates
Bob Arnson a écrit : Frédéric Viollet wrote: Ok.Thanks. Is there a documentation somewhere on how to use the setupexe bootstrapper? Not really, no. Here's the command line I use to build one: "%WIX%\setupbld" -out "%DIR%\foo.exe" -mcsp "%DIR%\foo.msi" -setup "%WIX%\setup.exe" Value="ChoosePortDlg">1 to my UI element where ChoosePortDlg is my custom dialog, but the dialog still doesn't appear. What am I doing wrong? If ResumeDlg is the WixUI version, the Install control is a button that publishes a bunch of other installation control events and you won't be able to insert a control event there. You need to use another control or dialog. Ok, thanks a lot. Fred begin:vcard fn;quoted-printable:Fr=C3=A9d=C3=A9ric Viollet n;quoted-printable:Viollet;Fr=C3=A9d=C3=A9ric org:Bull, Architect of an Open World (TM);Evidian S.A. adr;quoted-printable:;;Rue Jean Jaur=C3=A8s;Les Clayes Sous Bois;;78340;France email;internet:[EMAIL PROTECTED] title:Software Engineer tel;work:01 30 80 77 34 url:http://www.evidian.com - http://www.bull.com version:2.1 end:vcard - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] install dir in merge modules
Hi everyone, I've got a question about merge modules. I've written a merge module and I would like the files of the merge module to install themselves in the directory that the user selects while installing the main package. Example: *Merge Module: Program Files My Product bin ApmFile.dll *Product Program Files Alternate Product Dir--> the user selected a different directory than My Product2 bin amEngine.exe -->I would like ApmFile to be installed in the same directory (ie : Program Files -> Alternate Product Dir -> bin) Is there a way to achieve this? Here's my merge module: http://schemas.microsoft.com/wix/2006/wi";> Version="$(var.MY_PRODUCT_FILEVERSION_STRING)"> Guid="DC8244DB-25AD-402B-8691-2061797709B1"> Source="$(var.FACT_DESTDIR)\shared_lib\ApiFile.dll" KeyPath="yes" /> The Product wxs goes this way: http://schemas.microsoft.com/wix/2006/wi";> Manufacturer="$(var.MY_COMPANYNAME_STRING)" Name="My Product2 $(var.MY_PRODUCT_PRODUCTVERSION_STRING)" Version="$(var.MY_PRODUCT_FILEVERSION_STRING)" UpgradeCode='1F60EB8D-A0A4-4224-BF1E-C66E3F9CC35E'> IncludeMinimum='yes' Minimum='7.17.001.1' /> Id="Module_Test.504C56F7-1374-424F-B624-157E502CB661" Language="1033" SourceFile="MyModule.msm" DiskId="1" /> Guid="FC95C3A7-085E-4EF5-8018-6E0CDA2A4085"> Source="$(var.FACT_DESTDIR)\bin\amengine.exe" KeyPath="yes" /> Description="Engine"> begin:vcard fn;quoted-printable:Fr=C3=A9d=C3=A9ric Viollet n;quoted-printable:Viollet;Fr=C3=A9d=C3=A9ric org:Bull, Architect of an Open World (TM);Evidian S.A. adr;quoted-printable:;;Rue Jean Jaur=C3=A8s;Les Clayes Sous Bois;;78340;France email;internet:[EMAIL PROTECTED] title:Software Engineer tel;work:01 30 80 77 34 url:http://www.evidian.com - http://www.bull.com version:2.1 end:vcard - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] minor Updates
Bob Arnson a écrit : Frédéric Viollet wrote: Is there a way to perform a minor update without having to add on the command line REINSTALL=ALL REINSTALLMODE=vomus ??? No. If you want to be able to double-click a package to get an upgrade, it's got to be a major upgrade MSI package or a bootstrapper .exe that knows how to install a minor upgrade. The current WiX setupexe bootstrapper supports minor upgrades. Ok.Thanks. Is there a documentation somewhere on how to use the setupexe bootstrapper? I have described a custom UI. In this dialog box, I ask for some configuration properties. Is there a way to make this dialog box appear in update mode? Yes, just include it in the normal Back/Next button control events in your UI authoring. I tried to add Value="ChoosePortDlg">1 to my UI element where ChoosePortDlg is my custom dialog, but the dialog still doesn't appear. What am I doing wrong? Thanks again. Fred begin:vcard fn;quoted-printable:Fr=C3=A9d=C3=A9ric Viollet n;quoted-printable:Viollet;Fr=C3=A9d=C3=A9ric org:Bull, Architect of an Open World (TM);Evidian S.A. adr;quoted-printable:;;Rue Jean Jaur=C3=A8s;Les Clayes Sous Bois;;78340;France email;internet:[EMAIL PROTECTED] title:Software Engineer tel;work:01 30 80 77 34 url:http://www.evidian.com - http://www.bull.com version:2.1 end:vcard - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] minor Updates
Hi everyone, I quite new to Wix and I'm using Wix V3. I've looked around for a solution to my problem but I can't find anything maybe you will be able to help me. So here's the problem: Is there a way to perform a minor update without having to add on the command line REINSTALL=ALL REINSTALLMODE=vomus ??? Isn't there a way to dynamically add these properties when we detect that a former version of the product is already installed? I also have another question: I have described a custom UI. In this dialog box, I ask for some configuration properties. Is there a way to make this dialog box appear in update mode? Thanks for your help. Fred begin:vcard fn;quoted-printable:Fr=C3=A9d=C3=A9ric Viollet n;quoted-printable:Viollet;Fr=C3=A9d=C3=A9ric org:Bull, Architect of an Open World (TM);Evidian S.A. adr;quoted-printable:;;Rue Jean Jaur=C3=A8s;Les Clayes Sous Bois;;78340;France email;internet:[EMAIL PROTECTED] title:Software Engineer tel;work:01 30 80 77 34 url:http://www.evidian.com - http://www.bull.com version:2.1 end:vcard - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
