Re: [WiX-users] Queries on Upgrade

Search for the productcode. -- Sincerely, Gabriel -- Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible,

Re: [WiX-users] Queries on Upgrade

Good day, 1. What's your installation context ? User or Machine ? 2. Your condition seem ok if UPGRADINGPRODUCTCODE is the right property. 3. What's your need ? Check your msi with [1]InstEd. It's always instructive. Le Jeu 24 Avril 2014, à 12:37, Karkare,Aparna a écrit : Hello,

Re: [WiX-users] Queries on Upgrade

with AllowSameVersionUpgrades =yes. Can you please explain about 1st point? Thanks for your reply. Aparna Karkare LT Infotech OAI-sys, Enterprise Components and Frameworks Office: 020-6641-6142 Email: [1]akark...@travelers.com -Original Message- From: Gabriel Ivanes [[2]mailto:g...@fastmail.net

Re: [WiX-users] Run external Exe on Install

Depending if you want a Bundle : [1]http://wixtoolset.org/documentation/manual/v3/xsd/wix/exepackage.htm l Or an MSI : [2]http://wixtoolset.org/documentation/manual/v3/xsd/wix/customaction.h tml Le Ven 21 Mars 2014, à 17:56, Hoover, Jacob a écrit : Burn, running an EXE installer

[WiX-users] Burn : MSP and Installcondition

Hi guys, Here is my problem : ... MspPackage Id=Lync_msp_2737155_x64 Compressed=yes InstallCondition='VersionNT64'​ SourceFile=..\..\Sources\Lync2010\Lync_MSP_4.0

Re: [WiX-users] Burn : MSP and Installcondition

why Installcondition and code below don't work. Le Mar 18 Mars 2014, à 11:16, Gabriel Ivanes a écrit : Hi guys, Here is my problem : ... MspPackage Id=Lync_msp_2737155_x64 Compressed=yes InstallCondition

Re: [WiX-users] Extract Binary file from MSI to Temp folder using C#

You may want a complete example : !-- *** BINARY *** -- !-- Stockage des fichiers dans la table Binary -- Binary Id=polyval.hta SourceFile=Binary\polyval.hta / ... CustomAction Id=Launch_HTA_binary_table

Re: [WiX-users] Extract Binary file from MSI to Temp folder using C#

Hello, An example function in vbscript : Function ExtractBinary(BinaryName, OutputFile) Const msiReadStreamAnsi = 2 Dim oDatabase Set oDatabase = Session.Database Dim View Set View = oDatabase.OpenView(SELECT * FROM Binary WHERE Name = ' amp; BinaryName amp; ')

Re: [WiX-users] MsiPackage InstallCondition

Tim, LANG is just a burn's parameter i choose sets in installation's command line. My need was to get logonuser's language not UserLanguageID (installation is in system context) But custom actions are not possible in Burn and i usually need a script to know which user (hkusers\sid) to look for.

Re: [WiX-users] Change content of Config file after installation

My 2 cents, a vbscript's function : ' Prerequisites ' Proprierty FILE : File Path + Its name ' Propriété LINE : what you want to replace ' Propriété REG_EXP : Reg exp to identify what you want to be replaced ' Theses 3 properties are passed throught CustomActionData's property. ' Sub

Re: [WiX-users] Heat, XSLT, and Difxapp

I change my mind. Hardcored oemsetup.inf in global wxs with difxapp:driver. Then, heat harvest driver's file and exclude oemsetup.inf. Obvious. Le %:Date:, Gabriel Ivanes [1]g...@fastmail.net a écrit: Hi there, I want to automat heat with difxapp. I use heat this way : heat

Re: [WiX-users] Is there the way to pass installed product path to the major upgrade installer

Set Property and Set Directory are 2 different kind of custom action : [1]http://blogs.technet.com/b/alexshev/archive/2008/02/21/from-msi-to-w ix-part-5-custom-actions.aspx Le %:Date:, AK [2]kisslo...@gmail.com a écrit: Hi! I need to save install directory during major upgrade. To do this I

[WiX-users] Heat, XSLT, and Difxapp

Hi there, I want to automat heat with difxapp. I use heat this way : heat dir .\Sources -cg cmp_files_driver_x86 -dr TARGETDIR -gg -ke -out Projet\Files_driver.wxs -var var.Sources = .\Sources -t Build\Set_difxapp_to_inf.xsl. But XSLT failed because i don't know it well. First, i

Re: [WiX-users] acces hklm from a current user installer

Hi, You're sure your key and value exist ? To me -2147287038 means : not exist Le %:Date:, Sean Farrow sean.far...@seanfarrow.co.uk a écrit: Hi, I need to access the hklm key from a per-user install from a registry search element My property looks like: Fragment !--JAWS 14 exe

Re: [WiX-users] Noobie Help

Hi, Here is a sample : MsiPackage Name=2010 Redistributable x86 SP1 SourceFile=Sources\PreReqs\Vcredist_2010_SP1\x86\vc_red.msi MsiProperty Name=ROOTDRIVE Value=C:\/

Re: [WiX-users] Using Product Id=*

Hello, If you plan an upgrade, why do you need ProductCode of the previous version ? Le %:Date:, Gary Ewan Park ge...@gep13.co.uk a écrit: Hello, I am still quite new to WiX, so please bear with me... I have implemented the following pattern:

[WiX-users] CustomAction : FirstSequence/Rollback, OncePerProcess/Commit

Hello, Anyone knows why does the bit FirstSequence automatically set Rollback's bit ? The same with OncePerProcess and Commit. I made an immediat custom action with FirstSequence but i don't want rollback's bit. No problem in execution, but i'm just curious why. Thanks.

Re: [WiX-users] InstallUISequence

Like a condition ? : InstallUISequence Show Dialog=Migration_MAP_a00 Before=ExecuteAction USRCONCERNED = YES /Show /InstallUISequence Le %:Date:, Joseph, Sijo sijo.jos...@cgi.com a écrit: Hi All,

Re: [WiX-users] Running an MSI a second time to install more features or uninstall an already installed feature (while keeping others)

Good day, I had this required. I used transitive components. You could try ADDLOCAL property. Dunno know if it's available during msi repair. Le %:Date:, Hans ter Horst hoshis...@gmail.com a écrit: Hi, I have a feature tree based installer that has 4 features. If I install during a first

Re: [WiX-users] Running an MSI a second time to install more features or uninstall an already installed feature (while keeping others)

OK. Bootstrapper allow repair command. Le %:Date:, Hans ter Horst hoshis...@gmail.com a écrit: Ah, sorry, I meant when running the MSI via the burn bootstrapper. I have the MSI working like I want but I do run my MSI with user interface from the Bun bootstrapper, but when I run the

Re: [WiX-users] Running an MSI a second time to install more features or uninstall an already installed feature (while keeping others)

You could pass ADDLOCAL parameter to your Bootstrapper with different value in install and repair. Bundle .. Variable Name=ADDLOCAL bal:Overridable=yes/ .. /Bundle MsiPackage MsiProperty Name=ADDLOCAL Value=[ADDLOCAL]/ /MsiPackage Le %:Date:, Gabriel Ivanes g...@fastmail.net a écrit: OK

Re: [WiX-users] Running an MSI a second time to install more features or uninstall an already installed feature (while keeping others)

, Feb 15, 2013 at 6:21 AM, Gabriel Ivanes g...@fastmail.net wrote: You could pass ADDLOCAL parameter to your Bootstrapper with different value in install and repair. Bundle .. Variable Name=ADDLOCAL bal:Overridable=yes/ .. /Bundle MsiPackage MsiProperty Name=ADDLOCAL Value

Re: [WiX-users] [Wix-users] XSLT

/xsl:choose /xsl:attribute /xsl:template -Original Message- From: Gabriel Ivanes [mailto:g...@fastmail.net] Sent: Monday, February 11, 2013 10:16 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] [Wix-users] XSLT I already has a template. I changed

[WiX-users] [Wix-users] XSLT

Good day, Any good tutorial to use xsl with wix ? For example, replacing C:\windows\system32 with [SystemFolder] in a reg's file with heat. Thanks. -- Sincerely, Gabriel I know no way of judging the future but by the past. Patrick Henry You can never plan the future by the past.

Re: [WiX-users] [Wix-users] XSLT

-Original Message- From: Gabriel Ivanes [mailto:g...@fastmail.net] Sent: Monday, February 11, 2013 9:50 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] [Wix-users] XSLT Good day, Any good tutorial to use xsl with wix ? For example, replacing C:\windows\system32

Re: [WiX-users] Heat-harvesting with subfolder in the File-Source atribute

Hi, And with this : *heat.exe dir $(SolutionDir)MyProject -ag -sfrag -srd -var var.MyProject.ProjectDir -out $(ProjectDir)HarvestedFiles.wxs* Or you could add a subdir Sources in your SolutionDir : C:\\SolutionDir\MyProject\Sources\MyDirectory *heat.exe dir

Re: [WiX-users] Related to Sequences

[TestReg]tab.reg = [INSTALLFOLDER]tab.reg INSTALLFOLDER shouldn't be empty to be created or you need to use CreateFolder's table (http://wix.tramontana.co.hu/tutorial/com-expression-syntax-miscellanea/creating-directories) Any need to import reg.exe in binary table ? Why not using CA 34 ?

Re: [WiX-users] Export-Import registry

You can import a reg file, into a fragment, with heat : http://wix.sourceforge.net/manual-wix3/heat.htm Le Mar 22 Janvier 2013, à 9:49, Karkare,Aparna a écrit : Hi, Can we export the registry values, save the .reg file in install folder and merge it back using WiX? e.g. a particular path

Re: [WiX-users] Export-Import registry

You can import a reg file, into a fragment, with heat : http://wix.sourceforge.net/manual-wix3/heat.htm Le Mar 22 Janvier 2013, à 9:49, Karkare,Aparna a écrit : Hi, Can we export the registry values, save the .reg file in install folder and merge it back using WiX? e.g. a particular path

Re: [WiX-users] Export-Import registry

If you want to export registry's keys, you could use reg export. Not with Wix. Le Mar 22 Janvier 2013, à 10:49, Karkare,Aparna a écrit : Can registry values be exported too in .reg file? Regards, Aparna Karkare -Original Message- From: Gabriel Ivanes [mailto:g

Re: [WiX-users] MsiPackage InstallCondition

Hello, - Here are Burn Built-in Variables : http://wix.sourceforge.net/manual-wix3/bundle_built_in_variables.htm - You can also use burn's arguments. : Bundle ... Variable Name=LANG bal:Overridable=yes/ /Bundle Fragment ... PackageGroup

Re: [WiX-users] [Wix-users] Burn and RegistrySearch

, but if you wanted the user language in the Bundle, would the UserLanguageID variable have worked? On Thu, Dec 27, 2012 at 12:29 AM, Gabriel Ivanes g...@fastmail.net wrote: Finally, I used an MST, a launchcondition and with vital=no. -- I know no way of judging the future

Re: [WiX-users] [Wix-users] Burn and RegistrySearch

For permission's purpose. Le Sam 29 Décembre 2012, à 22:49, Rob Mensching a écrit : Why is your bootstrapper installing in the system context? On Sat, Dec 29, 2012 at 10:56 AM, Gabriel Ivanes g...@fastmail.net wrote: Ok. So here a more complete explanation. Be clement, more english

Re: [WiX-users] [Wix-users] Burn and RegistrySearch

Finally, I used an MST, a launchcondition and with vital=no. -- I know no way of judging the future but by the past. Patrick Henry You can never plan the future by the past. Edmund Burke -- Master Visual

[WiX-users] [Wix-users] Burn and RegistrySearch

Hello guys, I decided to use burn to bundle TortoiseSVN and its LanguagePack (only for french). We're using SCCM2012 with per-machine installation in system context. The language of the user is the result of 2 registry keys : HKEY_CURRENT_USER\Control Panel\Desktop\PreferredUILanguages if the