Re: [WiX-users] Running EXEs at install and uninstall
On 07/03/2013 19:37, Alain Forget wrote: 2) I only want the InstEXEs to run during installation (and not when uninstalling). Thus, since there is the special REMOVE=ALL to denote do this only if uninstalling, is there an equivalent I need to use to specify do this only if installing? Use NOT Installed. N.B. This condition will mean your actions won't run during a repair. Rob -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to change xml element value?
Hi All dev I just need to understand how can i use xmlconfig to validate xml element values add the same if not found. for example users userABC/user userXYZ//user /users how do i add one more element user check BDC user is there or not. if not it should add userBDC/user Please reply ASAP. Thanks -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Running EXEs at install and uninstall
Thank you. You bought up something I hadn't considered: repairs. So on a repair, I would like the uninstall exes AND the install exes to run. Suggestions on how to make that happen with inner text conditions? Alain -Original Message- From: Rob Hamflett [mailto:rob_hamfl...@sn.scee.net] Sent: March 8, 2013 03:32 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Running EXEs at install and uninstall On 07/03/2013 19:37, Alain Forget wrote: 2) I only want the InstEXEs to run during installation (and not when uninstalling). Thus, since there is the special REMOVE=ALL to denote do this only if uninstalling, is there an equivalent I need to use to specify do this only if installing? Use NOT Installed. N.B. This condition will mean your actions won't run during a repair. Rob -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Running EXEs at install and uninstall
There's more than just Install, Uninstall Repair to consider for your custom actions. dblock (creator of dotnetinstaller) has a handy WiX include you can use to save time writing all the conditions yourself - http://code.dblock.org/msi-property-patterns-upgrading-firstinstall-and-maintenance Also http://robmensching.com/blog/posts/2007/8/17/zataoca-custom-actions-are-generally-an-admission-of-failure Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: 08 March 2013 12:16 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Running EXEs at install and uninstall Thank you. You bought up something I hadn't considered: repairs. So on a repair, I would like the uninstall exes AND the install exes to run. Suggestions on how to make that happen with inner text conditions? Alain -Original Message- From: Rob Hamflett [mailto:rob_hamfl...@sn.scee.net] Sent: March 8, 2013 03:32 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Running EXEs at install and uninstall On 07/03/2013 19:37, Alain Forget wrote: 2) I only want the InstEXEs to run during installation (and not when uninstalling). Thus, since there is the special REMOVE=ALL to denote do this only if uninstalling, is there an equivalent I need to use to specify do this only if installing? Use NOT Installed. N.B. This condition will mean your actions won't run during a repair. Rob -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Running EXEs at install and uninstall
Cool, thanks for the link to Runtime.wxi . That definitely should save lots of time, effort, and aggravation in figuring all those properties out. Regarding using Custom Actions is an admission of failure ( http://robmensching.com/blog/posts/2007/8/17/zataoca-custom-actions-are-generally-an-admission-of-failure ), I believe our case is a combination of the blog post's points. I'll describe our context, since it may be worth mentioning why our installer is a failure (and maybe find a way to correct it). Our system being installed is written in Java, but it needs to run as a service on the client. Had I been on the project from the beginning, I would have opted for C# (and probably wouldn't be writing this e-mail right now, since I'd expect C# software to be easier to implement as a service). So we need custom actions because: * We don't have the time or budget to re-write the whole thing from scratch in C# or something more service-friendly. * Java programs (or batch files that may execute them) can't run as services, so we need to use a wrapping tool (Java Service Launcher, http://sourceforge.net/projects/jslwin/), which runs as an .exe, which needs a custom action to install, start, stop, and remove the services. So yeah, it's a piecemeal, hacky, suboptimal solution, but if software engineering could ever be done perfectly within time and budget constraints, I can't speak for anyone else, but I'd definitely be much happier. Still, I'm glad you brought it up, because it at least gave me pause to question whether or not we really need to use CAs, since simpler solutions are preferable. Unfortunately, I don't know of any alternatives, given our situation. If you have any suggestions on how to do what I've described better or more easily, we're definitely open to suggestions. Alain -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: March 8, 2013 07:53 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Running EXEs at install and uninstall There's more than just Install, Uninstall Repair to consider for your custom actions. dblock (creator of dotnetinstaller) has a handy WiX include you can use to save time writing all the conditions yourself - http://code.dblock.org/msi-property-patterns-upgrading-firstinstall-and-maintenance Also http://robmensching.com/blog/posts/2007/8/17/zataoca-custom-actions-are-generally-an-admission-of-failure Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: 08 March 2013 12:16 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Running EXEs at install and uninstall Thank you. You bought up something I hadn't considered: repairs. So on a repair, I would like the uninstall exes AND the install exes to run. Suggestions on how to make that happen with inner text conditions? Alain -Original Message- From: Rob Hamflett [mailto:rob_hamfl...@sn.scee.net] Sent: March 8, 2013 03:32 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Running EXEs at install and uninstall On 07/03/2013 19:37, Alain Forget wrote: 2) I only want the InstEXEs to run during installation (and not when uninstalling). Thus, since there is the special REMOVE=ALL to denote do this only if uninstalling, is there an equivalent I need to use to specify do this only if installing? Use NOT Installed. N.B. This condition will mean your actions won't run during a repair. Rob -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
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 path.-- Property Id=JAWS14PATH Secure=yes RegistrySearch Id=JAWS14PATH Root=HKLM Key=SOFTWARE\Freedom Scientific\JAWS\14.0 Name=Target Type=raw/ /Property The log looks a follows: Action 20:40:11: AppSearch. Searching for installed applications Action start 20:40:11: AppSearch. AppSearch: Property: JAWS14PATH, Signature: JAWS14PATH MSI (c) (A0:84) [20:40:11:112]: Note: 1: 2262 2: Signature 3: -2147287038 Do I need escaped backslashes in strings? Does anyone have any ideas how I can get this working? Cheers Sean. -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Sincèrement, Gabriel 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 -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
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:\/ MsiProperty Name=REBOOT Value=ReallySuppress/ MsiProperty Name=USING_EXUIH_SILENT Value=1/ Payload Name=vc_red.cab SourceFile=Sources\PreReqs\Vcredist_2010_SP1\x86\vc_red.cab/ /MsiPackage MsiPackage Name=2010 Redistributable x64 SP1 InstallCondition=VersionNT64 SourceFile=Sources\PreReqs\Vcredist_2010_SP1\x64\vc_red.msi MsiProperty Name=ROOTDRIVE Value=C:\/ MsiProperty Name=REBOOT Value=ReallySuppress/ MsiProperty Name=USING_EXUIH_SILENT Value=1/ Payload Name=vc_red.cab SourceFile=Sources\PreReqs\Vcredist_2010_SP1\x64\vc_red.cab/ /MsiPackage Le %:Date:, Jack Sojourn jack.sojo...@gmail.com a écrit: Thanks Jacob. You wouldn't have any example code or sample wxs file would you? On Tue, Mar 5, 2013 at 2:35 PM, Hoover, Jacob jacob.hoo...@greenheck.comwrote: Skip the merge module, use burn, and add the two redistributables as prerequisites. Make the x64 specific redistributable, give it an InstallCondition of VersionNT64 and a DetectCondition based on a variable you define with a search. -Original Message- From: Jack Sojourn [mailto:jack.sojo...@gmail.com] Sent: Tuesday, March 05, 2013 12:32 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Noobie Help Hello...I am new to wix and installation programming in general. I have a pretty simple setup requirement but am not sure how to do it. My first hurdle is the redist install. I know I should use the Merge Id and Microsoft_VC100_ATL_x86.msm or Microsoft_VC100_ATL_x64.msm. However what I need to do is if the OS is 32bit then install the x86 one. if 64bit then I need to install both as my app has a 32 bit dll and can not be recompiled. can anyone give me some direction on the best way to do this? Thanks. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Sincèrement, Gabriel 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 -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How can I make a setup using WIX 3.7 to delete some registry keys on uninstall
What does the verbose log file say is the state for the SC5RegistryKeys component during uninstall? On Thu, Mar 7, 2013 at 1:36 AM, Cosmin Petrenciuc cosmin.petrenc...@star-storage.ro wrote: Hello, I have created a setup program using WIX 3.7. I need the setup to create a registry key under HKLM on install and delete it upon uninstall. I have used the following code: Component Id=SC5RegistryKeys Guid=C9DCA66D-AFD0-4F0D-8A84-CD1B19611A17 Win64=no RegistryKey Root=HKLM Key=Software\[Manufacturer]\[ProductName] ForceCreateOnInstall=yes ForceDeleteOnUninstall=yes RegistryValue Name=LicenseInfo Type=binary KeyPath=yes Value=/ RegistryValue Name=SerialNumber Type=string Value=/ /RegistryKey /Component ComponentRef Id=SC5RegistryKeys / The registry key HKLM\ Software\[Manufacturer]\[ProductName] is created on install but it is not deleted on uninstall. Why is this happening? I'm running my setup program on a Windows 7 x64 machine, with UAC activated, and under an local administrators account. Thank you. Cosmin Petrenciuc The content of this communication is classified as STAR STORAGE Confidential and Proprietary Information.The content of this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this communication then delete it from your system. We appreciate your assistance in preserving the confidentiality of our correspondence. Thank you. Prezentul mesaj constituie o Informatie confidentiala si este proprietatea exclusiva a STAR STORAGE . Mesajul se adreseaza numai persoanei fizice sau juridice mentionata ca destinatara, precum si altor persoane autorizate sa-l primeasca. In cazul in care nu sunteti destinatarul vizat, va aducem la cunostinta ca dezvaluirea, copierea, distribuirea sau initierea unor actiuni pe baza prezentei informatii sunt strict interzise si atrag raspunderea civila si penala. Daca ati primit acest mesaj dintr-o eroare, va rugam sa ne anuntati imediat, ca raspuns la mesajul de fata, si sa-l stergeti apoi din sistemul dvs. Apreciem si va multumim pentru sprijinul acordat in pastrarea confidentialitatii corespondentei noastre. -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to localize WiX bootstrapper
If you wrote a custom bootstrapper application then it's more a question for the technology you used to create the UI. You'll be better served asking on a forum that supports the technology, in your case it sounds like WPF. On Thu, Mar 7, 2013 at 2:19 AM, Tomas Köhn tomas.k...@cellavision.sewrote: Hi We have created a bootstrapper in WiX for our .msi; and need to localize it. I have failed to find out how to do it, any help is appreciated. I tried to do it in the same way as in WPF: *Before rootVisual resources is loaded, set CultureInfo.DefaultThreadCurrentUICulture and Thread.CurrentThread.CurrentUICulture with new CultureInfo(de-De) *Created directory for German language with the translated resources de/BootStrapperApplication.resources.dll Added the resource as a payload in Bundle.wxs together with all other .dll which is used by the installer BootstrapperApplicationRef Id=ManagedBootstrapperApplicationHost Payload SourceFile=de\CellaVision.CRRS.Setup.Bootstrapper.Application.resources.dll/ ... How to tell the bootstrapper which resource to use? / Tomas -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] acces hklm from a current user installer
Hi: The key definitely exists on my test system, exporting the key from the registry editor gives: [HKEY_LOCAL_MACHINE\SOFTWARE\Freedom Scientific\JAWS\14.0] The Target value exists underneath. If I author a custom action, this can open the top level software\freedom scientific\jaws key but carn't see anything underneath this. The package is being built for x64, so I'm assuming the RegistrySearch will use the 64-bit hive. Any help/info apeciated. Regards Sean. -Original Message- From: Gabriel Ivanes [mailto:g...@fastmail.net] Sent: 08 March 2013 15:41 To: General discussion for Windows Installer XML toolset. Subject: 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 path.-- Property Id=JAWS14PATH Secure=yes RegistrySearch Id=JAWS14PATH Root=HKLM Key=SOFTWARE\Freedom Scientific\JAWS\14.0 Name=Target Type=raw/ /Property The log looks a follows: Action 20:40:11: AppSearch. Searching for installed applications Action start 20:40:11: AppSearch. AppSearch: Property: JAWS14PATH, Signature: JAWS14PATH MSI (c) (A0:84) [20:40:11:112]: Note: 1: 2262 2: Signature 3: -2147287038 Do I need escaped backslashes in strings? Does anyone have any ideas how I can get this working? Cheers Sean. -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Sincèrement, Gabriel 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 -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Noobie Help
Gabriel Thanks! As I said I am just getting into install programming. I usually work on backend and middle-tier server infrastructure so I know I am asking stupid questions but where does this go? do I just put it after the componentgroup or part of it? also the vc_red.cab and vc_red.msi...where do I get these from? I only have the exe and msm for the vs redists. Fragment ComponentGroup Id=ProductComponents Directory=INSTALLFOLDER !-- TODO: Remove the comments around this Component element and the ComponentRef below in order to add resources to this installer. -- !-- Component Id=ProductComponent -- !-- TODO: Insert files, registry keys, and other resources here. -- !-- /Component -- /ComponentGroup /Fragment Thanks again. On Fri, Mar 8, 2013 at 10:50 AM, Gabriel Ivanes g...@fastmail.net wrote: 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:\/ MsiProperty Name=REBOOT Value=ReallySuppress/ MsiProperty Name=USING_EXUIH_SILENT Value=1/ Payload Name=vc_red.cab SourceFile=Sources\PreReqs\Vcredist_2010_SP1\x86\vc_red.cab/ /MsiPackage MsiPackage Name=2010 Redistributable x64 SP1 InstallCondition=VersionNT64 SourceFile=Sources\PreReqs\Vcredist_2010_SP1\x64\vc_red.msi MsiProperty Name=ROOTDRIVE Value=C:\/ MsiProperty Name=REBOOT Value=ReallySuppress/ MsiProperty Name=USING_EXUIH_SILENT Value=1/ Payload Name=vc_red.cab SourceFile=Sources\PreReqs\Vcredist_2010_SP1\x64\vc_red.cab/ /MsiPackage Le %:Date:, Jack Sojourn jack.sojo...@gmail.com a écrit: Thanks Jacob. You wouldn't have any example code or sample wxs file would you? On Tue, Mar 5, 2013 at 2:35 PM, Hoover, Jacob jacob.hoo...@greenheck.comwrote: Skip the merge module, use burn, and add the two redistributables as prerequisites. Make the x64 specific redistributable, give it an InstallCondition of VersionNT64 and a DetectCondition based on a variable you define with a search. -Original Message- From: Jack Sojourn [mailto:jack.sojo...@gmail.com] Sent: Tuesday, March 05, 2013 12:32 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Noobie Help Hello...I am new to wix and installation programming in general. I have a pretty simple setup requirement but am not sure how to do it. My first hurdle is the redist install. I know I should use the Merge Id and Microsoft_VC100_ATL_x86.msm or Microsoft_VC100_ATL_x64.msm. However what I need to do is if the OS is 32bit then install the x86 one. if 64bit then I need to install both as my app has a 32 bit dll and can not be recompiled. can anyone give me some direction on the best way to do this? Thanks. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Sincèrement, Gabriel 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 -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security,
Re: [WiX-users] acces hklm from a current user installer
From the documentation... RegistrySearch Element (Util Extension) Attributes Name Type Description Required Win64 YesNoTypemk:@MSITStore:C:\Program%20Files%20(x86)\WiX%20Toolset%20v3.7\doc\WiX.chm::/html/util_xsd_simple_type_yesnotype.htm Instructs the search to look in the 64-bit registry when the value is 'yes'. When the value is 'no', the search looks in the 32-bit registry. The default value is 'no'. -Original Message- From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] Sent: Friday, March 08, 2013 12:07 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] acces hklm from a current user installer Hi: The key definitely exists on my test system, exporting the key from the registry editor gives: [HKEY_LOCAL_MACHINE\SOFTWARE\Freedom Scientific\JAWS\14.0] The Target value exists underneath. If I author a custom action, this can open the top level software\freedom scientific\jaws key but carn't see anything underneath this. The package is being built for x64, so I'm assuming the RegistrySearch will use the 64-bit hive. Any help/info apeciated. Regards Sean. -Original Message- From: Gabriel Ivanes [mailto:g...@fastmail.net] Sent: 08 March 2013 15:41 To: General discussion for Windows Installer XML toolset. Subject: 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.ukmailto: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 path.-- Property Id=JAWS14PATH Secure=yes RegistrySearch Id=JAWS14PATH Root=HKLM Key=SOFTWARE\Freedom Scientific\JAWS\14.0 Name=Target Type=raw/ /Property The log looks a follows: Action 20:40:11: AppSearch. Searching for installed applications Action start 20:40:11: AppSearch. AppSearch: Property: JAWS14PATH, Signature: JAWS14PATH MSI (c) (A0:84) [20:40:11:112]: Note: 1: 2262 2: Signature 3: -2147287038 Do I need escaped backslashes in strings? Does anyone have any ideas how I can get this working? Cheers Sean. -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.netmailto:WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Sincèrement, Gabriel 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 -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.netmailto:WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.netmailto:WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] acces hklm from a current user installer
Hi: I'm not using th util extension--this is just in msi as tandard! Cheers Sean. -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: 08 March 2013 19:15 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] acces hklm from a current user installer From the documentation... RegistrySearch Element (Util Extension) Attributes Name Type Description Required Win64 YesNoTypemk:@MSITStore:C:\Program%20Files%20(x86)\WiX%20Toolset%20v3.7\doc\WiX.chm::/html/util_xsd_simple_type_yesnotype.htm Instructs the search to look in the 64-bit registry when the value is 'yes'. When the value is 'no', the search looks in the 32-bit registry. The default value is 'no'. -Original Message- From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] Sent: Friday, March 08, 2013 12:07 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] acces hklm from a current user installer Hi: The key definitely exists on my test system, exporting the key from the registry editor gives: [HKEY_LOCAL_MACHINE\SOFTWARE\Freedom Scientific\JAWS\14.0] The Target value exists underneath. If I author a custom action, this can open the top level software\freedom scientific\jaws key but carn't see anything underneath this. The package is being built for x64, so I'm assuming the RegistrySearch will use the 64-bit hive. Any help/info apeciated. Regards Sean. -Original Message- From: Gabriel Ivanes [mailto:g...@fastmail.net] Sent: 08 March 2013 15:41 To: General discussion for Windows Installer XML toolset. Subject: 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.ukmailto: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 path.-- Property Id=JAWS14PATH Secure=yes RegistrySearch Id=JAWS14PATH Root=HKLM Key=SOFTWARE\Freedom Scientific\JAWS\14.0 Name=Target Type=raw/ /Property The log looks a follows: Action 20:40:11: AppSearch. Searching for installed applications Action start 20:40:11: AppSearch. AppSearch: Property: JAWS14PATH, Signature: JAWS14PATH MSI (c) (A0:84) [20:40:11:112]: Note: 1: 2262 2: Signature 3: -2147287038 Do I need escaped backslashes in strings? Does anyone have any ideas how I can get this working? Cheers Sean. -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.netmailto:WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Sincèrement, Gabriel 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 -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.netmailto:WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.netmailto:WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev
Re: [WiX-users] acces hklm from a current user installer
Then I assume you have Package/@Platform assigned as anything other than x86? @Win64 on the default RegistrySearch element instructs the search to look in the 64-bit registry when the value is 'yes'. When the value is 'no', the search looks in the 32-bit registry. The default value depends on the value of the Package/@Platform attribute: if the @Platform attribute value is 'x86', the default @Win64 attribute value is 'no'; otherwise, the default value is 'yes'. -Original Message- From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] Sent: Friday, March 08, 2013 1:31 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] acces hklm from a current user installer Hi: I'm not using th util extension--this is just in msi as tandard! Cheers Sean. -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: 08 March 2013 19:15 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] acces hklm from a current user installer From the documentation... RegistrySearch Element (Util Extension) Attributes Name Type Description Required Win64 YesNoTypemk:@MSITStore:C:\Program%20Files%20(x86)\WiX%20Toolset%20v3.7\doc\WiX.chm::/html/util_xsd_simple_type_yesnotype.htm Instructs the search to look in the 64-bit registry when the value is 'yes'. When the value is 'no', the search looks in the 32-bit registry. The default value is 'no'. -Original Message- From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] Sent: Friday, March 08, 2013 12:07 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] acces hklm from a current user installer Hi: The key definitely exists on my test system, exporting the key from the registry editor gives: [HKEY_LOCAL_MACHINE\SOFTWARE\Freedom Scientific\JAWS\14.0] The Target value exists underneath. If I author a custom action, this can open the top level software\freedom scientific\jaws key but carn't see anything underneath this. The package is being built for x64, so I'm assuming the RegistrySearch will use the 64-bit hive. Any help/info apeciated. Regards Sean. -Original Message- From: Gabriel Ivanes [mailto:g...@fastmail.net] Sent: 08 March 2013 15:41 To: General discussion for Windows Installer XML toolset. Subject: 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.ukmailto: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 path.-- Property Id=JAWS14PATH Secure=yes RegistrySearch Id=JAWS14PATH Root=HKLM Key=SOFTWARE\Freedom Scientific\JAWS\14.0 Name=Target Type=raw/ /Property The log looks a follows: Action 20:40:11: AppSearch. Searching for installed applications Action start 20:40:11: AppSearch. AppSearch: Property: JAWS14PATH, Signature: JAWS14PATH MSI (c) (A0:84) [20:40:11:112]: Note: 1: 2262 2: Signature 3: -2147287038 Do I need escaped backslashes in strings? Does anyone have any ideas how I can get this working? Cheers Sean. -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.netmailto:WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Sincèrement, Gabriel 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 -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.netmailto:WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to
Re: [WiX-users] acces hklm from a current user installer
The platform attribute is x64. Cheers Sean. -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: 08 March 2013 19:40 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] acces hklm from a current user installer Then I assume you have Package/@Platform assigned as anything other than x86? @Win64 on the default RegistrySearch element instructs the search to look in the 64-bit registry when the value is 'yes'. When the value is 'no', the search looks in the 32-bit registry. The default value depends on the value of the Package/@Platform attribute: if the @Platform attribute value is 'x86', the default @Win64 attribute value is 'no'; otherwise, the default value is 'yes'. -Original Message- From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] Sent: Friday, March 08, 2013 1:31 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] acces hklm from a current user installer Hi: I'm not using th util extension--this is just in msi as tandard! Cheers Sean. -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: 08 March 2013 19:15 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] acces hklm from a current user installer From the documentation... RegistrySearch Element (Util Extension) Attributes Name Type Description Required Win64 YesNoTypemk:@MSITStore:C:\Program%20Files%20(x86)\WiX%20Toolset%20v3.7\doc\WiX.chm::/html/util_xsd_simple_type_yesnotype.htm Instructs the search to look in the 64-bit registry when the value is 'yes'. When the value is 'no', the search looks in the 32-bit registry. The default value is 'no'. -Original Message- From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] Sent: Friday, March 08, 2013 12:07 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] acces hklm from a current user installer Hi: The key definitely exists on my test system, exporting the key from the registry editor gives: [HKEY_LOCAL_MACHINE\SOFTWARE\Freedom Scientific\JAWS\14.0] The Target value exists underneath. If I author a custom action, this can open the top level software\freedom scientific\jaws key but carn't see anything underneath this. The package is being built for x64, so I'm assuming the RegistrySearch will use the 64-bit hive. Any help/info apeciated. Regards Sean. -Original Message- From: Gabriel Ivanes [mailto:g...@fastmail.net] Sent: 08 March 2013 15:41 To: General discussion for Windows Installer XML toolset. Subject: 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.ukmailto: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 path.-- Property Id=JAWS14PATH Secure=yes RegistrySearch Id=JAWS14PATH Root=HKLM Key=SOFTWARE\Freedom Scientific\JAWS\14.0 Name=Target Type=raw/ /Property The log looks a follows: Action 20:40:11: AppSearch. Searching for installed applications Action start 20:40:11: AppSearch. AppSearch: Property: JAWS14PATH, Signature: JAWS14PATH MSI (c) (A0:84) [20:40:11:112]: Note: 1: 2262 2: Signature 3: -2147287038 Do I need escaped backslashes in strings? Does anyone have any ideas how I can get this working? Cheers Sean. -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.netmailto:WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Sincèrement, Gabriel 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 -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.netmailto:WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Using Burn/bootstrapper....
Hi guys, Using Burn aka the bootstrapper is their a way to show the user what software will be installed? i.e. create a new page before the Progress page to display what pre requesites will be installed and what our company software is going to be installed? thanks, Steve -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-Burn-bootstrapper-tp7584213.html Sent from the wix-users mailing list archive at Nabble.com. -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using Burn/bootstrapper....
Yes, the Plan() action will report back the action states for all packages to your BA. You'd need a custom BA, the wixstdba doesn't have anything like that today. On Fri, Mar 8, 2013 at 12:18 PM, StevenOgilvie sogil...@msn.com wrote: Hi guys, Using Burn aka the bootstrapper is their a way to show the user what software will be installed? i.e. create a new page before the Progress page to display what pre requesites will be installed and what our company software is going to be installed? thanks, Steve -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-Burn-bootstrapper-tp7584213.html Sent from the wix-users mailing list archive at Nabble.com. -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Noobie Help
Be patient and read wix.chm. Nick's book is also a must have : http://www.packtpub.com/windows-installer-xml-3-6-developers-guide/book Also, i remember redist's msi and wix to be problematic. Those msi are bad but wix don't help either. You need to use exe file. Jack Sojourn jack.sojo...@gmail.com a écrit : Gabriel Thanks! As I said I am just getting into install programming. I usually work on backend and middle-tier server infrastructure so I know I am asking stupid questions but where does this go? do I just put it after the componentgroup or part of it? also the vc_red.cab and vc_red.msi...where do I get these from? I only have the exe and msm for the vs redists. Fragment ComponentGroup Id=ProductComponents Directory=INSTALLFOLDER !-- TODO: Remove the comments around this Component element and the ComponentRef below in order to add resources to this installer. -- !-- Component Id=ProductComponent -- !-- TODO: Insert files, registry keys, and other resources here. -- !-- /Component -- /ComponentGroup /Fragment Thanks again. On Fri, Mar 8, 2013 at 10:50 AM, Gabriel Ivanes g...@fastmail.net wrote: 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:\/ MsiProperty Name=REBOOT Value=ReallySuppress/ MsiProperty Name=USING_EXUIH_SILENT Value=1/ Payload Name=vc_red.cab SourceFile=Sources\PreReqs\Vcredist_2010_SP1\x86\vc_red.cab/ /MsiPackage MsiPackage Name=2010 Redistributable x64 SP1 InstallCondition=VersionNT64 SourceFile=Sources\PreReqs\Vcredist_2010_SP1\x64\vc_red.msi MsiProperty Name=ROOTDRIVE Value=C:\/ MsiProperty Name=REBOOT Value=ReallySuppress/ MsiProperty Name=USING_EXUIH_SILENT Value=1/ Payload Name=vc_red.cab SourceFile=Sources\PreReqs\Vcredist_2010_SP1\x64\vc_red.cab/ /MsiPackage Le %:Date:, Jack Sojourn jack.sojo...@gmail.com a écrit: Thanks Jacob. You wouldn't have any example code or sample wxs file would you? On Tue, Mar 5, 2013 at 2:35 PM, Hoover, Jacob jacob.hoo...@greenheck.comwrote: Skip the merge module, use burn, and add the two redistributables as prerequisites. Make the x64 specific redistributable, give it an InstallCondition of VersionNT64 and a DetectCondition based on a variable you define with a search. -Original Message- From: Jack Sojourn [mailto:jack.sojo...@gmail.com] Sent: Tuesday, March 05, 2013 12:32 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Noobie Help Hello...I am new to wix and installation programming in general. I have a pretty simple setup requirement but am not sure how to do it. My first hurdle is the redist install. I know I should use the Merge Id and Microsoft_VC100_ATL_x86.msm or Microsoft_VC100_ATL_x64.msm. However what I need to do is if the OS is 32bit then install the x86 one. if 64bit then I need to install both as my app has a 32 bit dll and can not be recompiled. can anyone give me some direction on the best way to do this? Thanks. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Sincèrement, Gabriel I
[WiX-users] Force not to Install Same version of the product.
Hi, As of now I can install same version of Installer of a product twice (I mean Installer Product Version is same for both MSI packages but content of the both packages are not same). 1) Can I force the Installer not to install same version if same version is already installed on the machine and make to Prompt conditional error message asking them to uninstall already existing Instance . or 2) Is their any settings to remove already existing files completely(like upgrade) and install the new Installer of same version. Below are existing settings of the product ?define ProductVersion=5.0.0.0 ? Upgrade Id=3f643a18-5ef7-41e3-8bc2-5a9b2928dc94 UpgradeVersion Property=OLD_VERSION_FOUND Minimum=0.0.0.0 Maximum=$(var.ProductVersion) IncludeMinimum=yes IncludeMaximum=no OnlyDetect=no IgnoreRemoveFailure=yes MigrateFeatures=yes Language=1033 / UpgradeVersion Property=NEWER_VERSION_FOUND Minimum=$(var.ProductVersion) IncludeMinimum=no OnlyDetect=yes Language=1033 / /Upgrade Condition Message=A newer version greater than [ProductVersion] of [ProductName] is already installed. Exiting installation. /Condition InstallExecuteSequence RemoveExistingProducts Before=InstallInitialize / /InstallExecuteSequence Thanks in Advance Chatra -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Force-not-to-Install-Same-version-of-the-product-tp7584216.html Sent from the wix-users mailing list archive at Nabble.com. -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Force not to Install Same version of the product.
http://wix.tramontana.co.hu/tutorial/upgrades-and-modularization/checking-for-oldies Look for SELFFOUND. I believe that page discusses how to prevent re-installing the same version. Alain -Original Message- From: chennam [mailto:chatrapathi.chen...@gmail.com] Sent: March 8, 2013 17:15 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Force not to Install Same version of the product. Hi, As of now I can install same version of Installer of a product twice (I mean Installer Product Version is same for both MSI packages but content of the both packages are not same). 1) Can I force the Installer not to install same version if same version is already installed on the machine and make to Prompt conditional error message asking them to uninstall already existing Instance . or 2) Is their any settings to remove already existing files completely(like upgrade) and install the new Installer of same version. Below are existing settings of the product ?define ProductVersion=5.0.0.0 ? Upgrade Id=3f643a18-5ef7-41e3-8bc2-5a9b2928dc94 UpgradeVersion Property=OLD_VERSION_FOUND Minimum=0.0.0.0 Maximum=$(var.ProductVersion) IncludeMinimum=yes IncludeMaximum=no OnlyDetect=no IgnoreRemoveFailure=yes MigrateFeatures=yes Language=1033 / UpgradeVersion Property=NEWER_VERSION_FOUND Minimum=$(var.ProductVersion) IncludeMinimum=no OnlyDetect=yes Language=1033 / /Upgrade Condition Message=A newer version greater than [ProductVersion] of [ProductName] is already installed. Exiting installation. /Condition InstallExecuteSequence RemoveExistingProducts Before=InstallInitialize / /InstallExecuteSequence Thanks in Advance Chatra -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Force-not-to-Install-Same-version-of-the-product-tp7584216.html Sent from the wix-users mailing list archive at Nabble.com. -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to change xml element value?
Not sure yet how to check if the value is already written in the file. But to
write it, you could use something like:
ComponentGroup Id=ProductComponents Directory=INSTALLFOLDER
Component Id=CMP_MyFileXML
Guid={05AB616A-AD9E-468B-AE86-477759234CA0}
File Source=MyFile.xml KeyPath=yes /
util:XmlConfig Id=ConfigureMyFileXML
File=[INSTALLFOLDER]MyFile.xml
Action=create
On=install
Node=element
Name=user
ElementPath=//users
Value=BDC /
/Component
/ComponentGroup
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-change-xml-element-value-tp7584198p7584218.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Formatted strings not being formatted
Yep, after a number of trials and errors, this was bang on. For the record (and anyone in the future trying to do something similar), here's the snippet I ended up with: Component Id='compMyExe' Guid='----' File Id='fileMyExe' Name='my.exe' DiskId='1' Source='my.exe' KeyPath='yes' / /Component ... Component Id='compMyExeConfig' Guid='----' File Id='fileMyExeConfig' Name='MyExeConf.ini' DiskId='1' Source='somePath/'MyExeConf.ini' KeyPath='yes' / /Component ... !-- Sliently install my.exe (with elevated privileges; Execute=deferred, see http://wix.sourceforge.net/manual-wix3/qtexec.htm ) -- CustomAction Id=Set_cmdInstallMyExe Property=cmdInstallMyExe Value=quot;[#fileMyExe]quot; -install ]quot;[#fileMyExeConfig] ]quot; / CustomAction Id=cmdInstallMyExe Execute=deferred BinaryKey=WixCA DllEntry=CAQuietExec Return=check Impersonate=no / InstallExecuteSequence Custom Action=Set_cmdInstallMyExe After=CostFinalize / Custom Action=cmdInstallMyExe After=InstallServices / /InstallExecuteSequence Thanks, Alain -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: March 7, 2013 19:39 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset. Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Formatted strings not being formatted Use a CA to set the value of the property at runtime right before scheduling the deferred CA. You might even be able to assign the property the value of itself so it evaluates it at runtime. Deferred CA's are special as they only have access to the limited data you explicitly send to them (and a subset of standard props). Sent from my iPhone On Mar 7, 2013, at 6:22 PM, Alain Forget afor...@cmu.edu wrote: Hi all, This page ( http://wix.tramontana.co.hu/tutorial/com-expression-syntax-miscellanea/formatted-strings ) suggests that [#fileId] can be used in a string to get the path where that file is installed. However, when I try using them like this... Component Id='compMyExe' Guid='----' File Id='fileMyExe' Name='my.exe' DiskId='1' Source='my.exe' KeyPath='yes' / /Component ... Component Id='compMyExeConfig' Guid='----' File Id='fileMyExeConfig' Name='MyExeConf.ini' DiskId='1' Source='somePath/'MyExeConf.ini' KeyPath='yes' / /Component ... !-- Sliently install my.exe (with elevated privileges; Execute=deferred, see http://wix.sourceforge.net/manual-wix3/qtexec.htm ) -- Property Id=cmdInstallMyExe Value=quot;[#fileMyExe]quot; -install '[#fileMyExeConfig]' / CustomAction Id=cmdInstallMyExe Execute=deferred BinaryKey=WixCA DllEntry=CAQuietExec Return=check Impersonate=no / InstallExecuteSequence Custom Action=cmdInstallMyExe After=InstallServices / /InstallExecuteSequence ...the install fails with the log output showing... Action 18:27:14: cmdInstallMyExe. MSI (s) (B0:6C) [18:27:14:247]: Executing op: CustomActionSchedule(Action= cmdInstallMyExe,ActionType=3073,Source=BinaryData,Target=CAQuietExec,C ustomActionData=[#fileMyExe] -install '[#fileMyExeConfig]') MSI (s) (B0:E8) [18:27:14:263]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI59E3.tmp, Entrypoint: CAQuietExec MSI (s) (B0:80) [18:27:14:263]: Generating random cookie. MSI (s) (B0:80) [18:27:14:263]: Created Custom Action Server with PID 2020 (0x7E4). MSI (s) (B0:9C) [18:27:14:294]: Running as a service. MSI (s) (B0:9C) [18:27:14:294]: Hello, I'm your 32bit Impersonated custom action server. CAQuietExec: Error 0x80070002: Command failed to execute. CAQuietExec: Error 0x80070002: CAQuietExec Failed CustomAction cmdInstallMyExe returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) It appears as though WiX or the installer isn't making the substitution at all. I've triple-checked that there are no typos, and that this CustomAction happens after InstallServices, which implicitly comes after the CostInitialize, FileCost and CostFinalize steps, meaning that the fileIds should be referenceable. The install process was working fine before I added the CustomAction-related tags. Anyone have any idea what might be going wrong, and how to fix it? Alain *** Alain Forget, Ph.D. Postdoctoral Researcher CyLab, Carnegie Mellon University afor...@cmu.edu http://cups.cs.cmu.edu/~aforget/ *** -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report.
