Re: [WiX-users] Multiple Instance installations from wix BA application
I think you're the third or fourth person to ask on this mailing list in the last year. It's not supported. There was a discussion on this mailing list some time ago if I recall. -Original Message- From: serkbugs [mailto:serkb...@yandex.ru] Sent: July-31-14 5:51 AM To: wix-users@lists.sourceforge.net Cc: Sergey Kozhemyachenko Subject: [WiX-users] Multiple Instance installations from wix BA application Hi, Our customer wants to install multiple instances of windows service per each service(like SQL server installation with multiple instances). I was trying to build a prototype using custom BA application(Microsoft.Tools.WindowsInstallerXml.Bootstrapper.BootstrapperApp lication). I've read a lot of topics around InstanceTransforms in msi and it looks like I can start it work from msi with msiexec /i MultiInstance.msi MSINEWINSTANCE=1 TRANSFORMS=:I01 but I cannot understand how to run it properly from BA. Here is some pieces from my prototype. Msi(please don't pay attention to extra actions and properties): Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:util=http://schemas.microsoft.com/wix/UtilExtension; Product Id=$(var.I00) Name=$(var.ProductName32) Language=1033 Version=$(var.CurrentVersion) Manufacturer=Me inc UpgradeCode=$(var.UpgradeGuid) Package InstallerVersion=200 Compressed=yes InstallScope=perMachine / MajorUpgrade AllowDowngrades=no AllowSameVersionUpgrades=yes DowngradeErrorMessage=You can't downgrade this application Schedule=afterInstallExecute MigrateFeatures=yes/ MediaTemplate EmbedCab=yes / Feature Id=ProductFeature Title=SetupProjectTest Level=1 ComponentGroupRef Id=ProductComponents / /Feature Property Id=PATHTOCOPY Secure=yes/Property Property Id=PATHTOCOPYTO Secure=yes/Property Binary Id='CustomAction' SourceFile=$(var.TestCustomAction.TargetDir)TestCustomAction.CA.dll / Property Id=PREVIOUSVERSIONSINSTALLED Secure=yes / Property Id='REINSTALLMODE' Value='amus'/ Property Id='ServiceName' Value='Test Service Name 2'/ Property Id='INSTANCEID' Value='I01' RegistrySearch Id=InstanceIdSearch Root=HKLM Key=Software\[Manufacturer]\[ProductCode]\$(var.ProductName32) Name=InstanceId Type=raw / /Property InstanceTransforms Property='INSTANCEID' Instance Id='I01' ProductCode='$(var.I01)' ProductName='I01'/ Instance Id='I02' ProductCode='$(var.I02)' ProductName='I02'/ Instance Id='I03' ProductCode='$(var.I03)' ProductName='I03'/ /InstanceTransforms /Product Bundle: Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:util=http://schemas.microsoft.com/wix/UtilExtension; xmlns:bal=http://schemas.microsoft.com/wix/BalExtension; Bundle Name=$(var.ProductName) Version=$(var.CurrentVersion) Manufacturer=$(var.Manufacturer) UpgradeCode=$(var.UpgradeGuid) BootstrapperApplicationRef Id=ManagedBootstrapperApplicationHost Payload SourceFile=$(var.TestBootstrapperApplication.TargetDir)BootstrapperCore.con fig/ Payload SourceFile=$(var.TestBootstrapperApplication.TargetDir)TestBootstrapperAppl ication.dll/ Payload SourceFile=$(var.TestBootstrapperApplication.TargetDir)GalaSoft.MvvmLight.W PF4.dll/ Payload SourceFile=c:\Program Files (x86)\WiX Toolset v3.7\SDK\Microsoft.Deployment.WindowsInstaller.dll/ /BootstrapperApplicationRef Variable Name=DIR_EXISTS Value=NO Persisted=yes Type=string / Variable Name=PATHTOAPP Value=c:\program files (x86)\SetupProjectTest\ Persisted=yes Type=string / Chain PackageGroupRef Id=NetFx40Web / PackageGroupRef Id=pkgMsi/ /Chain /Bundle /Wix another bundle file: Fragment .. Variable Name='TRANSFORMS' bal:Overridable=yes/ Variable Name='MSINEWINSTANCE' bal:Overridable=yes/ .. PackageGroup Id=pkgMsi MsiPackage Id=package32 SourceFile=$(var.SetupProjectTest.TargetDir)\SetupProjectTest.msi Vital=yes LogPathVariable=WixBundleLog_package32 DisplayInternalUI=yes EnableFeatureSelection=no SuppressSignatureVerification=yes ForcePerMachine=yes InstallCondition=NOT TRANSFORMS MsiProperty Name=INSTALLFOLDER Value=[INSTALLFOLDER]/ /MsiPackage MsiPackage Id=package32Multiple SourceFile=$(var.SetupProjectTest.TargetDir)\SetupProjectTest.msi Vital=yes LogPathVariable=WixBundleLog_package32 DisplayInternalUI=yes EnableFeatureSelection=no SuppressSignatureVerification=yes ForcePerMachine=yes InstallCondition=TRANSFORMS
[WiX-users] Microsoft office: click to run
Interesting. Microsoft office came out with their own install technology called Click to run. Here: http://office.microsoft.com/en-us/outlook-help/click-to-run-introduction-HA1 01850493.aspx Never heard of it before. Wonder why they created that over MSI. -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck#174; Code Sight#153; - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] simple re-packaging of a 3rd party redistributable -- fixed link to screen shot
So your installer will install package you created PLUS this third party setup.exe? Or is the only thing your installer installing is this setup.exe? -Original Message- From: Sean Hall [mailto:r.sean.h...@gmail.com] Sent: June-15-14 11:43 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] simple re-packaging of a 3rd party redistributable -- fixed link to screen shot It sounds like you want to create a self extracting archive of the 3rd party files. 7zip is a free tool that can do this. On Sun, Jun 15, 2014 at 9:25 PM, Moyer, Andy andy.mo...@cpii.com wrote: Thank you, but my user base can install click-once prerequisites. Security is not the problem today. The problem is that the 3rd party redistributable is in the form of a setup.exe, with accompanying supporting sub-directories and multiple .msi files. I need to take all the files together, package them, deliver them, and then execute the setup.exe silently from my own installer. I would be ok on my own if the 3rd party files were embedded in a single file, but they are not. Any help is greatly appreciated, thank you, Andy Moyer -Original Message- From: Marek Mielcarek [mailto:mmielca...@actuate.com] Sent: Sunday, June 15, 2014 6:55 PM To: wix-users@lists.sourceforge.net; 'wix-users@lists.sourceforge.net' Subject: Re: [WiX-users] simple re-packaging of a 3rd party redistributable -- fixed link to screen shot I am sorry, I hit sent before finishing the answer. A vanilla/plain version of your problem goes like trhis: how to install a 3rd party distributable using click-once deployment. As I already pointed before, this is is security issue. You can deliver (virtually) any binary to users host but you need user with admin privilege to execute successful installation. Provided your 3rd party piece is available as msi or exe or zip you do not need wix to re-wrap it msi. Instead you can easily push it to client-side as embedded resource that you write to local folder at execution time. After that you can launch that (locally saved) resource but as soon as you do that your user has to be admin to succeed. This is the essential explanation of your problem and, if I correctly understand it, you do not even need wix and Your challenge is related to security. Thanks Original Message From: Moyer, Andy Sent: Sunday, June 15, 2014 21:12 To: 'wix-users@lists.sourceforge.net' Reply To: General discussion about the WiX toolset. Subject: [WiX-users] simple re-packaging of a 3rd party redistributable -- fixed link to screen shot Hi All, Sorry about the link on my previous email. This one should work. Please, I need help. I have a 3rd party redistributable on which my vb.net 2012 application is dependent. I've attached a link to a screen shot of the files that make up the redistributable. Screen capture: https://onedrive.live.com/redir?resid=CA08CB94DCE2E3E7%211376 The point of the link is to show that the payload is a setup.exe with supporting folders and files, that the setup.exe depends on, i.e. it is not a single setup.exe file, it is with dependent directories and files, and that's where I get lost. The 3rd party redistributable fully supports a silent install, I've tested it with a command prompt. Ultimately, I deploy my apps with click-once, so my goal is to bundle this 3rd party redist as a prerequisite to my click-once app-I can handle that on my own once I have a tidy bundle. What I need help with is, how can I make an .msi or .exe that bundles up all the files shown in the attached screen shot, such that when the new .msi or .exe is ran, it invokes the payload setup.exe (the 3rd party redist) with command line args that will make it run silently. (please not the setup.exe needs the rest of the files shown to run properly.) I really need help with this, I'm trying to deploy an app I've been working on for a while and now I've lost another week because I can't put together a seamless installer for this 3rd party redist. To sum it up another way, I want to wrap the 3rd party redist (shown in the attached screen shot) within my own windows installer package, such that the 3rd party redist is installed silently as part of my own windows installer package. Thank you very much, Andy Moyer _ This message, including any attachments, may include privileged, confidential and/or inside information. Any distribution or use of this communication by anyone other than the intended recipient(s) is strictly prohibited and may be unlawful. If you are not the intended recipient, please notify the sender by replying to this message and then delete it from your system. -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in
Re: [WiX-users] simple re-packaging of a 3rd party redistributable -- fixed link to screen shot
OK. As mentioned by Sean a self extracting zip would be the simplest. You can set it up to automatically run setup.exe after it extracts the files with a custom command line. Or you can use burn and use the ExePackage element. It creates an EXE and you can run it silently. But likely overkill for what you want to do. If you wanted to get rid of your clickonce installer and do everything in wix then it would make more sense. -Original Message- From: Moyer, Andy [mailto:andy.mo...@cpii.com] Sent: June-16-14 11:34 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] simple re-packaging of a 3rd party redistributable -- fixed link to screen shot The only thing my installer needs to install is the setup.exe. Thank you. -Andy Moyer -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: Monday, June 16, 2014 7:06 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] simple re-packaging of a 3rd party redistributable -- fixed link to screen shot So your installer will install package you created PLUS this third party setup.exe? Or is the only thing your installer installing is this setup.exe? -Original Message- From: Sean Hall [mailto:r.sean.h...@gmail.com] Sent: June-15-14 11:43 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] simple re-packaging of a 3rd party redistributable -- fixed link to screen shot It sounds like you want to create a self extracting archive of the 3rd party files. 7zip is a free tool that can do this. On Sun, Jun 15, 2014 at 9:25 PM, Moyer, Andy andy.mo...@cpii.com wrote: Thank you, but my user base can install click-once prerequisites. Security is not the problem today. The problem is that the 3rd party redistributable is in the form of a setup.exe, with accompanying supporting sub-directories and multiple .msi files. I need to take all the files together, package them, deliver them, and then execute the setup.exe silently from my own installer. I would be ok on my own if the 3rd party files were embedded in a single file, but they are not. Any help is greatly appreciated, thank you, Andy Moyer -Original Message- From: Marek Mielcarek [mailto:mmielca...@actuate.com] Sent: Sunday, June 15, 2014 6:55 PM To: wix-users@lists.sourceforge.net; 'wix-users@lists.sourceforge.net' Subject: Re: [WiX-users] simple re-packaging of a 3rd party redistributable -- fixed link to screen shot I am sorry, I hit sent before finishing the answer. A vanilla/plain version of your problem goes like trhis: how to install a 3rd party distributable using click-once deployment. As I already pointed before, this is is security issue. You can deliver (virtually) any binary to users host but you need user with admin privilege to execute successful installation. Provided your 3rd party piece is available as msi or exe or zip you do not need wix to re-wrap it msi. Instead you can easily push it to client-side as embedded resource that you write to local folder at execution time. After that you can launch that (locally saved) resource but as soon as you do that your user has to be admin to succeed. This is the essential explanation of your problem and, if I correctly understand it, you do not even need wix and Your challenge is related to security. Thanks Original Message From: Moyer, Andy Sent: Sunday, June 15, 2014 21:12 To: 'wix-users@lists.sourceforge.net' Reply To: General discussion about the WiX toolset. Subject: [WiX-users] simple re-packaging of a 3rd party redistributable -- fixed link to screen shot Hi All, Sorry about the link on my previous email. This one should work. Please, I need help. I have a 3rd party redistributable on which my vb.net 2012 application is dependent. I've attached a link to a screen shot of the files that make up the redistributable. Screen capture: https://onedrive.live.com/redir?resid=CA08CB94DCE2E3E7%211376 The point of the link is to show that the payload is a setup.exe with supporting folders and files, that the setup.exe depends on, i.e. it is not a single setup.exe file, it is with dependent directories and files, and that's where I get lost. The 3rd party redistributable fully supports a silent install, I've tested it with a command prompt. Ultimately, I deploy my apps with click-once, so my goal is to bundle this 3rd party redist as a prerequisite to my click-once app-I can handle that on my own once I have a tidy bundle. What I need help with is, how can I make an .msi or .exe that bundles up all the files shown in the attached screen shot, such that when the new .msi or .exe is ran, it invokes the payload setup.exe (the 3rd party redist) with command line args that will make it run silently. (please not the setup.exe needs the rest of the files shown to run properly.) I really need help with this, I'm trying
Re: [WiX-users] Bundle fails to verify signature of payload
Does the computer have internet access? Looks like it's not finding a parent
certificate for validation. Not sure. Others on this list said that
validation can be a problem when you don't have internet access and the proper
certificates aren't on the computer.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: April-01-14 9:33 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Bundle fails to verify signature of payload
Anyone seen this before? I've bundles built using WiX v3.6 which are failing to
apply a patch which has been signed by a renewed code signing certificate. The
bundle was signed by the previous certificate which expired last month but both
the bundle the patch show up as valid signatures when I check their file
properties.
The Burn log is as follows:
[09F8:0818][2014-03-31T12:53:35]: Prompt for source of package:
SharedContentPatch, payload: SharedContentPatch, path:
C:\Temp\ve2013fp2_hotfix3_final\VESharedContent.msp
[09F8:0818][2014-03-31T12:53:35]: Acquiring package: SharedContentPatch,
payload: SharedContentPatch, download from:
http://cdn.iesve.com/ve/VESharedContent.msp
[0BFC:0BD4][2014-03-31T12:54:32]: Error 0x80070490: Failed to find expected
public key in certificate chain.
[0BFC:0BD4][2014-03-31T12:54:32]: Error 0x80070490: Failed to verify expected
payload against actual certificate chain.
[0BFC:0BD4][2014-03-31T12:54:32]: Error 0x80070490: Failed to verify signature
of payload: SharedContentPatch
[0BFC:0BD4][2014-03-31T12:54:32]: Failed to verify payload: SharedContentPatch
at path: C:\ProgramData\Package Cache\.unverified\SharedContentPatch, error:
0x80070490. Deleting file.
[0BFC:0BD4][2014-03-31T12:54:32]: Error 0x80070490: Failed to cache payload:
SharedContentPatch
[09F8:0818][2014-03-31T12:54:32]: Failed to cache payload: SharedContentPatch
from working path:
C:\Users\zxc\AppData\Local\Temp\{28ab7e13-61b4-4bdd-a582-d2197a5e794f}\SharedContentPatch,
error: 0x80070490.
[09F8:0818][2014-03-31T12:54:32]: Application requested retry of payload:
SharedContentPatch, encountered error: 0x80070490. Retrying...
[09F8:0818][2014-03-31T12:54:32]: Prompt for source of package:
SharedContentPatch, payload: SharedContentPatch, path:
C:\Temp\ve2013fp2_hotfix3_final\VESharedContent.msp
[09F8:0818][2014-03-31T12:54:35]: Acquiring package: SharedContentPatch,
payload: SharedContentPatch, download from:
http://cdn.iesve.com/ve/VESharedContent.msp
[0BFC:0BD4][2014-03-31T12:55:32]: Error 0x80070490: Failed to find expected
public key in certificate chain.
[0BFC:0BD4][2014-03-31T12:55:32]: Error 0x80070490: Failed to verify expected
payload against actual certificate chain.
[0BFC:0BD4][2014-03-31T12:55:32]: Error 0x80070490: Failed to verify signature
of payload: SharedContentPatch
[0BFC:0BD4][2014-03-31T12:55:32]: Failed to verify payload: SharedContentPatch
at path: C:\ProgramData\Package Cache\.unverified\SharedContentPatch, error:
0x80070490. Deleting file.
[0BFC:0BD4][2014-03-31T12:55:32]: Error 0x80070490: Failed to cache payload:
SharedContentPatch
[09F8:0818][2014-03-31T12:55:32]: Failed to cache payload: SharedContentPatch
from working path:
C:\Users\zxc\AppData\Local\Temp\{28ab7e13-61b4-4bdd-a582-d2197a5e794f}\SharedContentPatch,
error: 0x80070490.
[09F8:0818][2014-03-31T12:55:32]: Application requested retry of payload:
SharedContentPatch, encountered error: 0x80070490. Retrying...
[09F8:0818][2014-03-31T12:55:32]: Prompt for source of package:
SharedContentPatch, payload: SharedContentPatch, path:
C:\Temp\ve2013fp2_hotfix3_final\VESharedContent.msp
[09F8:0818][2014-03-31T12:55:35]: Acquiring package: SharedContentPatch,
payload: SharedContentPatch, download from:
http://cdn.iesve.com/ve/VESharedContent.msp
[0BFC:0BD4][2014-03-31T12:56:31]: Error 0x80070490: Failed to find expected
public key in certificate chain.
[0BFC:0BD4][2014-03-31T12:56:31]: Error 0x80070490: Failed to verify expected
payload against actual certificate chain.
[0BFC:0BD4][2014-03-31T12:56:31]: Error 0x80070490: Failed to verify signature
of payload: SharedContentPatch
[0BFC:0BD4][2014-03-31T12:56:31]: Failed to verify payload: SharedContentPatch
at path: C:\ProgramData\Package Cache\.unverified\SharedContentPatch, error:
0x80070490. Deleting file.
[0BFC:0BD4][2014-03-31T12:56:31]: Error 0x80070490: Failed to cache payload:
SharedContentPatch
[09F8:0818][2014-03-31T12:56:31]: Failed to cache payload: SharedContentPatch
from working path:
C:\Users\zxc\AppData\Local\Temp\{28ab7e13-61b4-4bdd-a582-d2197a5e794f}\SharedContentPatch,
error: 0x80070490.
[09F8:03F0][2014-03-31T12:56:31]: Error 0x80070490: Failed while caching,
aborting execution.
The error is the same regardless of whether the patch is available locally or
if it downloads the file from the URL above.
The patch applies perfectly fine if I double click it or run it using msiexec
/update myself from a command prompt.
It also fails if I don't sign the
Re: [WiX-users] Bundle fails to verify signature of payload
I should mention there was discussion by wix team on defaulting to hash
checking of files instead of the vericode signature. I changed over my bundles
to use hash checking. From what I can tell and find using hash verification is
just as good.
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: April-01-14 11:11 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Bundle fails to verify signature of payload
Does the computer have internet access? Looks like it's not finding a parent
certificate for validation. Not sure. Others on this list said that
validation can be a problem when you don't have internet access and the proper
certificates aren't on the computer.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: April-01-14 9:33 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Bundle fails to verify signature of payload
Anyone seen this before? I've bundles built using WiX v3.6 which are failing to
apply a patch which has been signed by a renewed code signing certificate. The
bundle was signed by the previous certificate which expired last month but both
the bundle the patch show up as valid signatures when I check their file
properties.
The Burn log is as follows:
[09F8:0818][2014-03-31T12:53:35]: Prompt for source of package:
SharedContentPatch, payload: SharedContentPatch, path:
C:\Temp\ve2013fp2_hotfix3_final\VESharedContent.msp
[09F8:0818][2014-03-31T12:53:35]: Acquiring package: SharedContentPatch,
payload: SharedContentPatch, download from:
http://cdn.iesve.com/ve/VESharedContent.msp
[0BFC:0BD4][2014-03-31T12:54:32]: Error 0x80070490: Failed to find expected
public key in certificate chain.
[0BFC:0BD4][2014-03-31T12:54:32]: Error 0x80070490: Failed to verify expected
payload against actual certificate chain.
[0BFC:0BD4][2014-03-31T12:54:32]: Error 0x80070490: Failed to verify signature
of payload: SharedContentPatch
[0BFC:0BD4][2014-03-31T12:54:32]: Failed to verify payload: SharedContentPatch
at path: C:\ProgramData\Package Cache\.unverified\SharedContentPatch, error:
0x80070490. Deleting file.
[0BFC:0BD4][2014-03-31T12:54:32]: Error 0x80070490: Failed to cache payload:
SharedContentPatch
[09F8:0818][2014-03-31T12:54:32]: Failed to cache payload: SharedContentPatch
from working path:
C:\Users\zxc\AppData\Local\Temp\{28ab7e13-61b4-4bdd-a582-d2197a5e794f}\SharedContentPatch,
error: 0x80070490.
[09F8:0818][2014-03-31T12:54:32]: Application requested retry of payload:
SharedContentPatch, encountered error: 0x80070490. Retrying...
[09F8:0818][2014-03-31T12:54:32]: Prompt for source of package:
SharedContentPatch, payload: SharedContentPatch, path:
C:\Temp\ve2013fp2_hotfix3_final\VESharedContent.msp
[09F8:0818][2014-03-31T12:54:35]: Acquiring package: SharedContentPatch,
payload: SharedContentPatch, download from:
http://cdn.iesve.com/ve/VESharedContent.msp
[0BFC:0BD4][2014-03-31T12:55:32]: Error 0x80070490: Failed to find expected
public key in certificate chain.
[0BFC:0BD4][2014-03-31T12:55:32]: Error 0x80070490: Failed to verify expected
payload against actual certificate chain.
[0BFC:0BD4][2014-03-31T12:55:32]: Error 0x80070490: Failed to verify signature
of payload: SharedContentPatch
[0BFC:0BD4][2014-03-31T12:55:32]: Failed to verify payload: SharedContentPatch
at path: C:\ProgramData\Package Cache\.unverified\SharedContentPatch, error:
0x80070490. Deleting file.
[0BFC:0BD4][2014-03-31T12:55:32]: Error 0x80070490: Failed to cache payload:
SharedContentPatch
[09F8:0818][2014-03-31T12:55:32]: Failed to cache payload: SharedContentPatch
from working path:
C:\Users\zxc\AppData\Local\Temp\{28ab7e13-61b4-4bdd-a582-d2197a5e794f}\SharedContentPatch,
error: 0x80070490.
[09F8:0818][2014-03-31T12:55:32]: Application requested retry of payload:
SharedContentPatch, encountered error: 0x80070490. Retrying...
[09F8:0818][2014-03-31T12:55:32]: Prompt for source of package:
SharedContentPatch, payload: SharedContentPatch, path:
C:\Temp\ve2013fp2_hotfix3_final\VESharedContent.msp
[09F8:0818][2014-03-31T12:55:35]: Acquiring package: SharedContentPatch,
payload: SharedContentPatch, download from:
http://cdn.iesve.com/ve/VESharedContent.msp
[0BFC:0BD4][2014-03-31T12:56:31]: Error 0x80070490: Failed to find expected
public key in certificate chain.
[0BFC:0BD4][2014-03-31T12:56:31]: Error 0x80070490: Failed to verify expected
payload against actual certificate chain.
[0BFC:0BD4][2014-03-31T12:56:31]: Error 0x80070490: Failed to verify signature
of payload: SharedContentPatch
[0BFC:0BD4][2014-03-31T12:56:31]: Failed to verify payload: SharedContentPatch
at path: C:\ProgramData\Package Cache\.unverified\SharedContentPatch, error:
0x80070490. Deleting file.
[0BFC:0BD4][2014-03-31T12:56:31]: Error 0x80070490: Failed to cache payload:
SharedContentPatch
[09F8:0818][2014-03-31T12:56:31]: Failed to cache payload: SharedContentPatch
from working path:
C:\Users\zxc\AppData
Re: [WiX-users] Bundle fails to verify signature of payload
Customers may vary. My customers are not computer inclined at all and 90% of time don't have IT backup. They are mechanical technicians who often who don't know the first thing about computers. If the installer doesn't work they can't do their job. The PC is an annoying tool they have to use. :) So I use SuppressSignatureVerification=yes (i.e. use hash verification) as it makes the installer more robust. I still sign my packages though. Wes -Original Message- From: Carter Young [mailto:ecyo...@grandecom.net] Sent: April-01-14 11:49 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bundle fails to verify signature of payload I apologize for cludging up the list with possible unneeded replies, but it's things like this that get me riled up. As an IT Professional and programmer, it really bothers me when as programmers, we ignore a xritival erroor bevause we know the option to do so. I'm a proponent of a healthy system, and suppressing an error now only makes the problem worse later. As such, I have been researching the issue between my replies. Please consider at lest reading the additional link below, before taking the easy way out by suppressing the validation check: http://blogs.technet.com/b/asiasupp/archive/2011/06/20/the-error-0x80070490-element-not-found-when-you-are-installing-a-service-pack-or-update.aspx I believe the steps outlined must be performed on each affected machine, as the caches are local to the affected machines. Carter Quoting Carter Young ecyo...@grandecom.net: I suggest doing this only after running the System Update Readiness Tool as I stated earlier. Although it has been my observation that Method 2 only makes the issue worse... If the System Update Readiness Tool reports no inconsistencies, then I would feel more comfortable suppressing the warning. Once again the KB Article is: http://support.microsoft.com/kb/958044 Carter Quoting Phill Hogland phogl...@rimage.com: I noticed a problem once. Not sure why. I also saw comments from others that this can be problematic, so I set SuppressSignatureVerification=yes on my packages in the bundle chain. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle- fails-to-verify-signature-of-payload-tp7593877p7593882.html Sent from the wix-users mailing list archive at Nabble.com. - - ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Setup hang when trying to disable windows updates
Yes. Not that I know of. I only seen it once I think where the computer was out of date. Once I patched it, I didn't see it again. -Original Message- From: Ogrodowski, Sabine [mailto:sabine.ogrodow...@haufe-lexware.com] Sent: March-25-14 10:37 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Setup hang when trying to disable windows updates Hi, I'm experiencing something strange with my custom bootstrapper. When I click the Install button on a Windows 8 machine with enabled windows updates, the installation hangs for some time before really starting to apply my packages. In the log file I think I managed to track it down to the action of disabling windows updates, which fails. I have seen this fail in Windows 7 in some cases but there it only hangs for about 2 minutes (which I think is some timeout), but on Windows 8 it took 12 minutes before it finally continued: [0558:06AC][2014-03-11T09:45:14]i000: Plan complete. [0558:06AC][2014-03-11T09:45:14]i299: Plan complete, result: 0x0 [0558:06AC][2014-03-11T09:45:14]i300: Apply begin [03D4:10BC][2014-03-11T09:57:20]w308: Automatic updates could not be paused due to error: 0x80080005. Continuing... [03D4:10BC][2014-03-11T09:57:20]i360: Creating a system restore point. Has anyone seen this before? Is there something I can do about this? Regards, Sabine -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] What is the best way to design a Bootstrapper requiring external input ?
It hides the addon (or any type) bundle as well. The progress is then shown on main bundle like Jacob said. Wes -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: March-24-14 5:13 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] What is the best way to design a Bootstrapper requiring external input ? Exe protocol will allow the primary bundle to display messages from the add-on bundle. -Original Message- From: Scott Moyer [mailto:scott.mo...@appliedvision.com] Sent: Monday, March 24, 2014 2:31 PM To: 'General discussion about the WiX toolset.' Subject: Re: [WiX-users] What is the best way to design a Bootstrapper requiring external input ? I added ExeProtocol=burn to the ExePackage element in the first bundle, and I added RelatedBundle Id=first-bundle's-guid Action=Addon/ to the Fragment in the second/driver bundle. Not sure if that is correct as it does not appear to make any difference, good or bad, to the installation. -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Monday, March 24, 2014 12:59 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] What is the best way to design a Bootstrapper requiring external input ? Have two bundles; The first containing your prerequisites and core application install and a second bundle containing the drivers. Yes, it would be an Exe package with ExeProtocol=burn. In the driver bundle, I believe you'd want to look at the RelatedBundle element. http://blogs.msdn.com/b/heaths/archive/2012/02/21/introducing-sticky-patching-and-add-ons.aspx -Original Message- From: Scott Moyer [mailto:scott.mo...@appliedvision.com] Sent: Monday, March 24, 2014 11:50 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] What is the best way to design a Bootstrapper requiring external input ? Thanks for the response. Just to clarify... You can have more than one bundle/bundle in a Bootstrapper.wxs? Or by second bundle do you mean second Bootstrapper.exe? As in targeting a second Bootstrapper (Bootstrapper2.exe) as the SourceFile in an ExePackage in the first Bootstrapper (Bootstrapper1.exe)? (This actually does work). For example ... Wix ... Bundle Name=Bootstrapper1 ... chain ... ExePackage Id=DriverSetup SourceFile=Bootstrapper2.exe ''' InstallCommand=/q /norestart/ /chain (/Bundle /Wix -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Monday, March 24, 2014 11:49 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] What is the best way to design a Bootstrapper requiring external input ? There isn't any communication between the MSI and the BA for returning property values. Since you've written your own BA, you have a bit more latitude but you can't modify the plan in between packages in Apply. To me it almost seems like it would make sense (and be easier and not require a custom BA) to utilize a second bundle for the camera drivers. There you could do your install check to assert your initial bundle is in place, and utilize registry searches to read the persisted values from your main MSI install to then allow this aux bundle to plan the proper driver MSI. As for the remember me property pattern, http://robmensching.com/blog/posts/2010/5/2/the-wix-toolsets-remember-property-pattern -Original Message- From: Scott Moyer [mailto:scott.mo...@appliedvision.com] Sent: Monday, March 24, 2014 10:37 AM To: 'General discussion about the WiX toolset.' Subject: Re: [WiX-users] What is the best way to design a Bootstrapper requiring external input ? Thanks for the reply. I already have four MSIs for the two drivers (two x64 and two x86), and I am familiar with passing variables from a BA to an MSI. I just need to figure out how to pass information back from the MSI so the BA can access it. I do not understand how to persist a variable and am not familiar with the 'remember property' pattern. Do you have any examples you can share, as I am a pretty visual learner? -Original Message- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: Monday, March 24, 2014 11:11 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] What is the best way to design a Bootstrapper requiring external input ? I am in a similar boat, converting an old IS script project to Wix/msi. So I am also learning, and very impressed with WIX. Most of my time so far has been trying to sort out oddball configuration issues for drivers. In my case in some scenarios I need to get printer drivers installed as print-to-file and in other situations the same driver as pnp when hardware is attached. But since the pc is embedded into the hardware the hardware is attached even before the software is installed, which creates pnp issues. Given your info, I think I
Re: [WiX-users] What is the best way to design a Bootstrapper requiring external input ?
You don't need an addon bundle if you just want to embed a bundle within a bundle. An addon is useful if you want users to install bundles outside of the main install say to add new features to your software or maybe a language pack. Then burn is smart enough to remove all addon bundles when the user uninstalls the main bundle. You need to have a relatedbundle element with action=detect in your main bundle. Set it's guid attribute to that of the releatedbundle guid attribute in your addon bundle. Wes -Original Message- From: Scott Moyer [mailto:scott.mo...@appliedvision.com] Sent: March-24-14 4:31 PM To: 'General discussion about the WiX toolset.' Subject: Re: [WiX-users] What is the best way to design a Bootstrapper requiring external input ? I added ExeProtocol=burn to the ExePackage element in the first bundle, and I added RelatedBundle Id=first-bundle's-guid Action=Addon/ to the Fragment in the second/driver bundle. Not sure if that is correct as it does not appear to make any difference, good or bad, to the installation. -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Monday, March 24, 2014 12:59 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] What is the best way to design a Bootstrapper requiring external input ? Have two bundles; The first containing your prerequisites and core application install and a second bundle containing the drivers. Yes, it would be an Exe package with ExeProtocol=burn. In the driver bundle, I believe you'd want to look at the RelatedBundle element. http://blogs.msdn.com/b/heaths/archive/2012/02/21/introducing-sticky-patching-and-add-ons.aspx -Original Message- From: Scott Moyer [mailto:scott.mo...@appliedvision.com] Sent: Monday, March 24, 2014 11:50 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] What is the best way to design a Bootstrapper requiring external input ? Thanks for the response. Just to clarify... You can have more than one bundle/bundle in a Bootstrapper.wxs? Or by second bundle do you mean second Bootstrapper.exe? As in targeting a second Bootstrapper (Bootstrapper2.exe) as the SourceFile in an ExePackage in the first Bootstrapper (Bootstrapper1.exe)? (This actually does work). For example ... Wix ... Bundle Name=Bootstrapper1 ... chain ... ExePackage Id=DriverSetup SourceFile=Bootstrapper2.exe ''' InstallCommand=/q /norestart/ /chain (/Bundle /Wix -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Monday, March 24, 2014 11:49 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] What is the best way to design a Bootstrapper requiring external input ? There isn't any communication between the MSI and the BA for returning property values. Since you've written your own BA, you have a bit more latitude but you can't modify the plan in between packages in Apply. To me it almost seems like it would make sense (and be easier and not require a custom BA) to utilize a second bundle for the camera drivers. There you could do your install check to assert your initial bundle is in place, and utilize registry searches to read the persisted values from your main MSI install to then allow this aux bundle to plan the proper driver MSI. As for the remember me property pattern, http://robmensching.com/blog/posts/2010/5/2/the-wix-toolsets-remember-property-pattern -Original Message- From: Scott Moyer [mailto:scott.mo...@appliedvision.com] Sent: Monday, March 24, 2014 10:37 AM To: 'General discussion about the WiX toolset.' Subject: Re: [WiX-users] What is the best way to design a Bootstrapper requiring external input ? Thanks for the reply. I already have four MSIs for the two drivers (two x64 and two x86), and I am familiar with passing variables from a BA to an MSI. I just need to figure out how to pass information back from the MSI so the BA can access it. I do not understand how to persist a variable and am not familiar with the 'remember property' pattern. Do you have any examples you can share, as I am a pretty visual learner? -Original Message- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: Monday, March 24, 2014 11:11 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] What is the best way to design a Bootstrapper requiring external input ? I am in a similar boat, converting an old IS script project to Wix/msi. So I am also learning, and very impressed with WIX. Most of my time so far has been trying to sort out oddball configuration issues for drivers. In my case in some scenarios I need to get printer drivers installed as print-to-file and in other situations the same driver as pnp when hardware is attached. But since the pc is embedded into the hardware the hardware is attached even before the software is installed, which
Re: [WiX-users] Suppress ICE Validation for a Specific Table
Yes, right click on project and select properties. In there there's a Tools Setting tab with ICE verification. -Original Message- From: Levi Wilson [mailto:l...@leviwilson.com] Sent: March-13-14 4:38 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Suppress ICE Validation for a Specific Table Is it possible to suppress ICE validation for a particular table? The reason I'm asking is because using a property to set the SqlDatabase\@User attribute results in an ICE30 (seemingly) incorrectly. I'd like to tell it to not do ICE validation on the SqlDatabase table, rather than for everything. -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditional SSPI / SQL Authentication on SqlScript
Actually you can modify the MSI at runtime, at least its database. Don't know if you can modify the embedded files. Semi-custom action: http://www.joyofsetup.com/2007/07/01/semi-custom-actions/. -Original Message- From: Levi Wilson [mailto:l...@leviwilson.com] Sent: March-12-14 7:19 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Conditional SSPI / SQL Authentication on SqlScript I tried this example; yours has the @User set on the SqlString / rather than the SqlDatabase /. I tried this, so I removed the @User from the SqlDatabase and added it to SqlScript instead...this looks like it ONLY uses Integrated Security (because of the absence of it on the SqlDatabase / and NEVER uses the SQL Authentication. This is aggravating that you cannot use something like @User=[SOME_USER_PROPERTY] and then have it evaluate it then :(. I feel like I HAVE to be missing something. The OTHER fix I can think of is to update the User_ field in the SqlDatabase table...but it doesn't appear that you can modify the MSI at runtime. On Wed, Mar 12, 2014 at 5:43 PM, John Cooper jocoo...@jackhenry.com wrote: Well, I had only one product that deploys using sql:SqlDatabase, and it has recently converted to SqlPackage. Here's a sampling of the code I use which has been tested under both Windows and SQL Authentication on several products for over two years: Fragment PropertyRef Id=SQL_SERVERNAME / PropertyRef Id=SQL_USERNAME / PropertyRef Id=SQL_PASSWORD / util:User Id=DbUser Name=[SQL_USERNAME] Password=[SQL_PASSWORD] / sql:SqlDatabase Id=DbProduct Database=Product Server=[SQL_SERVERNAME] / /Fragment Fragment PropertyRef Id=SQL_DEPLOY_DATABASE / PropertyRef Id=SQL_RECOVERY_SIMPLE / DirectoryRef Id=INSTALLLOCATION Component Id=CmpProductRecoveryFull Guid=PUT-GUID-HERE KeyPath=yes Condition![CDATA[NOT SQL_RECOVERY_SIMPLE AND SQL_DEPLOY_DATABASE]]/Condition sql:SqlString Id=SqlRecoveryAsFull ExecuteOnInstall=yes SqlDb=DbProduct User=DbUser SQL=ALTER DATABASE Product SET RECOVERY FULL/ /Component /DirectoryRef /Fragment -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.(r) Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Levi Wilson [mailto:l...@leviwilson.com] Sent: Wednesday, March 12, 2014 4:03 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Conditional SSPI / SQL Authentication on SqlScript This leads me to believe that I should be able to do this? http://sourceforge.net/p/wix/bugs/626/ On Wed, Mar 12, 2014 at 4:19 PM, Levi Wilson l...@leviwilson.com wrote: John, how were you able to accomplish this? I tried to explicitly do this like so: Property Id=EMPTY_USER / Property Id=EMPTY_PASSWORD / util:User Id='SqlInstallerUserId' Name='[EMPTY_USER]' Password='[EMPTY_PASSWORD]' / Doing so yields ExecuteSqlStrings: Error 0x80040e4d: failed to connect to database: 'my database' in the output log, and the EMPTY_USER and EMPTY_PASSWORD do not even show up (because they were never set). I'm not sure how to get them to evaluate to empty, but I thought that would suffice. Since it did not, then I tried this: Property Id=EMPTY_USER Value=something / Property Id=EMPTY_PASSWORD Value=something / SetProperty Id=EMPTY_USER After=AppSearch Value= / SetProperty Id=EMPTY_PASSWORD After=AppSearch Value= / In the output log, I see the original property values, then when it sets them to empty it says it's Deleting the properties because their values are empty, and I still get the same error: ExecuteSqlStrings: Error 0x80040e4d: failed to connect to database: 'my database' I have a feeling I'm missing something simple. Additionally, I thought I would be able to set the User_ column of the SqlDatabase table to a NULL to try to get that to happen, but apparently you can't modify a value in the MSI database at runtime? Thanks in advance, Levi On Tue, Mar 11, 2014 at 11:42 AM, John Cooper jocoo...@jackhenry.com wrote: Yes. In your case, if SQL_ADMIN_USERNAME and SQL_ADMIN_PASSWORD both evaluate to empty-string, then the sql:SqlDatabase will deploy with Windows Authentication. I use this pattern all the time. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.(r) Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Levi Wilson [mailto:l...@leviwilson.com] Sent: Tuesday, March 11, 2014 10:33 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Conditional SSPI / SQL Authentication on SqlScript I have a component that has multiple
Re: [WiX-users] Conditional SSPI / SQL Authentication on SqlScript
Yes you're correct. I missed that part. -Original Message- From: Levi Wilson [mailto:l...@leviwilson.com] Sent: March-13-14 10:33 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Conditional SSPI / SQL Authentication on SqlScript You can add to the MSI database, but as near as I can tell you cannot UPDATE the MSI database :( On Thu, Mar 13, 2014 at 9:09 AM, Wesley Manning wmann...@dynagen.ca wrote: Actually you can modify the MSI at runtime, at least its database. Don't know if you can modify the embedded files. Semi-custom action: http://www.joyofsetup.com/2007/07/01/semi-custom-actions/. -Original Message- From: Levi Wilson [mailto:l...@leviwilson.com] Sent: March-12-14 7:19 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Conditional SSPI / SQL Authentication on SqlScript I tried this example; yours has the @User set on the SqlString / rather than the SqlDatabase /. I tried this, so I removed the @User from the SqlDatabase and added it to SqlScript instead...this looks like it ONLY uses Integrated Security (because of the absence of it on the SqlDatabase / and NEVER uses the SQL Authentication. This is aggravating that you cannot use something like @User=[SOME_USER_PROPERTY] and then have it evaluate it then :(. I feel like I HAVE to be missing something. The OTHER fix I can think of is to update the User_ field in the SqlDatabase table...but it doesn't appear that you can modify the MSI at runtime. On Wed, Mar 12, 2014 at 5:43 PM, John Cooper jocoo...@jackhenry.com wrote: Well, I had only one product that deploys using sql:SqlDatabase, and it has recently converted to SqlPackage. Here's a sampling of the code I use which has been tested under both Windows and SQL Authentication on several products for over two years: Fragment PropertyRef Id=SQL_SERVERNAME / PropertyRef Id=SQL_USERNAME / PropertyRef Id=SQL_PASSWORD / util:User Id=DbUser Name=[SQL_USERNAME] Password=[SQL_PASSWORD] / sql:SqlDatabase Id=DbProduct Database=Product Server=[SQL_SERVERNAME] / /Fragment Fragment PropertyRef Id=SQL_DEPLOY_DATABASE / PropertyRef Id=SQL_RECOVERY_SIMPLE / DirectoryRef Id=INSTALLLOCATION Component Id=CmpProductRecoveryFull Guid=PUT-GUID-HERE KeyPath=yes Condition![CDATA[NOT SQL_RECOVERY_SIMPLE AND SQL_DEPLOY_DATABASE]]/Condition sql:SqlString Id=SqlRecoveryAsFull ExecuteOnInstall=yes SqlDb=DbProduct User=DbUser SQL=ALTER DATABASE Product SET RECOVERY FULL/ /Component /DirectoryRef /Fragment -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.(r) Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Levi Wilson [mailto:l...@leviwilson.com] Sent: Wednesday, March 12, 2014 4:03 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Conditional SSPI / SQL Authentication on SqlScript This leads me to believe that I should be able to do this? http://sourceforge.net/p/wix/bugs/626/ On Wed, Mar 12, 2014 at 4:19 PM, Levi Wilson l...@leviwilson.com wrote: John, how were you able to accomplish this? I tried to explicitly do this like so: Property Id=EMPTY_USER / Property Id=EMPTY_PASSWORD / util:User Id='SqlInstallerUserId' Name='[EMPTY_USER]' Password='[EMPTY_PASSWORD]' / Doing so yields ExecuteSqlStrings: Error 0x80040e4d: failed to connect to database: 'my database' in the output log, and the EMPTY_USER and EMPTY_PASSWORD do not even show up (because they were never set). I'm not sure how to get them to evaluate to empty, but I thought that would suffice. Since it did not, then I tried this: Property Id=EMPTY_USER Value=something / Property Id=EMPTY_PASSWORD Value=something / SetProperty Id=EMPTY_USER After=AppSearch Value= / SetProperty Id=EMPTY_PASSWORD After=AppSearch Value= / In the output log, I see the original property values, then when it sets them to empty it says it's Deleting the properties because their values are empty, and I still get the same error: ExecuteSqlStrings: Error 0x80040e4d: failed to connect to database: 'my database' I have a feeling I'm missing something simple. Additionally, I thought I would be able to set the User_ column of the SqlDatabase table to a NULL to try to get that to happen, but apparently you can't modify a value in the MSI database at runtime? Thanks in advance, Levi On Tue, Mar 11, 2014 at 11:42 AM, John Cooper jocoo...@jackhenry.com wrote: Yes. In your case, if SQL_ADMIN_USERNAME and SQL_ADMIN_PASSWORD both evaluate to empty-string
[WiX-users] ICE38 on per-user installs
Moving this to wix-users. I was asking if I should create a feature request to ignore ICE38 in per-user installs. But after I asked I found another thread on wix-users (see link below) that pointed out if the user has the ability to choose the install location then multiple users could install to a common (i.e. non-per-user) location. ICE38 would apply in that case. So looks like I answered my own question. Wes From: Rob Mensching [mailto:r...@firegiant.com] Sent: February-18-14 12:14 PM To: WiX toolset developer mailing list Subject: Re: [WiX-devs] ICE38 on per-user installs These questions are better suited for wix-users mailing list. ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: Tuesday, February 18, 2014 7:37 AM To: WiX toolset developer mailing list Subject: Re: [WiX-devs] ICE38 on per-user installs I just found this discussion: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-do-I-install-to-LocalAppData-folder-td7580065.html: This is my own, admittedly inexpert, understanding of per-user installations: [...] The ICE38 error is slightly misleading: since you have a per-user installation, it's safe to ignore as long as the user cannot pick an alternative installation location that is common to all users. ICE38 is checking for the situation where multiple users all install the same component to the same path. So maybe there is no way wix can tell at build time if it's safe to ignore ICE38. It's up to the developer to ignore or not. Funny I'm finding lots of info on per-user installs now. Wes From: Wesley Manning Sent: February-18-14 11:20 AM To: wix-d...@lists.sourceforge.netmailto:wix-d...@lists.sourceforge.net Subject: ICE38 on per-user installs I recently ran into ICE38 when trying to create a per-user install. One opinion was ICE38 is invalid and should only apply to per-machine installs. What do you guys think? Should I add a feature request for wix to ignore ICE38 if install set as per-user? Wes -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installation context issues when directory structure is defined in library project
What OS are you installing on? The ProgramFilesFolder redirection only works on Windows 7 and above. -Original Message- From: Thomas Brodersen [mailto:t...@sharecon.com] Sent: February-18-14 5:37 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Installation context issues when directory structure is defined in library project I am trying to create a perUser installation package for an application that will install to the ProgramFilesFolder (which should be something like %LocalAppData%\Programs for a perUser installation). This works fine when everything is defined in the installer project, but when I make an installer based on a WiX library project containing that directory structure referencing ProgramFilesFolder, the perUser setting (defined in the installer project) doesn't seem to take effect - the installer warns that it could not access the Program Files directory. Is this a bug or am I doing something wrong? Here are the files: Library.wxs (in ProductInstallerLibrary project): ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder Directory Id=INSTALLFOLDER Name=My Sample Application / /Directory /Directory /Fragment Fragment ComponentGroup Id=ProductComponents Directory=INSTALLFOLDER Component Id=ProductComponent Guid=699A9167-3AA0-49FF-919B-F1CE4DBBB2C3 RegistryValue KeyPath=yes Root=HKCU Key=SOFTWARE\SHARECON\MySampleApplication Name=InstallFolder Type=string Value=[INSTALLFOLDER] Action=write / File Source=$(var.MySampleApplication.TargetPath) / RemoveFolder Id=INSTALLFOLDER On=uninstall / /Component /ComponentGroup /Fragment /Wix Product.wxs (in ProductInstaller project, referencing the ProductInstallerLibrary project): ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Product Id=* Name=ProductInstaller Language=1033 Version=1.0.0.0 Manufacturer=Sharecon A/S UpgradeCode=105d31b7-6d08-44de-9b77-55588b58de87 Package InstallerVersion=200 Compressed=yes InstallScope=perUser / MajorUpgrade DowngradeErrorMessage=A newer version of [ProductName] is already installed. / MediaTemplate EmbedCab=yes / Feature Id=ProductFeature Title=ProductInstaller Level=1 ComponentGroupRef Id=ProductComponents / /Feature /Product /Wix Development environment: Visual Studio 2010, WiX 3.7. Thomas Magle Brodersen SHARECON A/S E-mail: t...@sharecon.com -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Launch third party application installation at front
Disclaimer: I never created my own BA. Here are a couple of links: http://www.wrightfully.com/part-1-of-writing-your-own-net-based-installer-with-wix-overview/ http://stackoverflow.com/questions/7840380/custom-wix-burn-bootstrapper-user-interface?rq=1 These are for creating .net BA. If you want to use C++ then it's similar I think. There's nothing built in that can do that but the BA is the GUI and you controller everything in the BA. Maybe you can find some trick. Wes -Original Message- From: karthikrangaraj [mailto:kranga...@dnpphoto.eu] Sent: February-13-14 1:06 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Launch third party application installation at front Is there any example? Is it possible create an interface and display the installation inside the interface? Thank you. - Wix 3.8 users -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Launch-third-party-application-installation-at-front-tp7592625p7592645.html Sent from the wix-users mailing list archive at Nabble.com. -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bundle packages in ARP
How about stopping the bundle acting like a product, i.e. not appearing in ARP and acting more like the older style of Bootstrapper from the Windows SDK? Can't do, check Rob's/Bob's blog on wixtoolset.org. Burn is meant as a unified experience. You question comes up quite a bit here but burn isn't meant as a fire and forget bootstraper. Wes -Original Message- From: GrahamAllwood [mailto:graham.allw...@live.co.uk] Sent: February-12-14 5:41 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bundle packages in ARP There is a mixture of MSI's and exe's. So for EXE's, there is no way to get them to appear in ARP? Pity! How about stopping the bundle acting like a product, i.e. not appearing in ARP and acting more like the older style of Bootstrapper from the Windows SDK? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-packages-in-ARP-tp7592597p7592606.html Sent from the wix-users mailing list archive at Nabble.com. -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bundle elevation error in WinXP
You can't do a per-user to per-machine upgrade at all. MSI doesn't allow it
from what I heard.
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: February-12-14 10:05 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Bundle elevation error in WinXP
This line:
[14DC:15A8][2014-02-12T11:51:39]i103: Detected related package:
{2DDC7E93-29AB-4260-A9DB-697F7FA88157}, scope: PerUser, version: 6.4.4.0,
language: 0 operation: MajorUpgrade
Makes me think something funky is going on. You are trying to upgrade a per
user MSI to a per machine MSI? I can't remember all the details, but I do know
that per user installs have their own problems and trying to switch between
them in an upgrade can cause headaches.
-Original Message-
From: Евгений Волошин [mailto:voloshin.evge...@yandex.ru]
Sent: Wednesday, February 12, 2014 5:30 AM
To: General discussion about the WiX toolset.
Subject: [WiX-users] Bundle elevation error in WinXP
Hello!
I've got some strage behavior of Burn (WiX v 3.7/3.8) in windows xp.
When I try to include msi installer in standart bundle setup pauses saying
Initializing... and after several minutes shows error message 0x800705b4.
When I open up logs I see that Burn failed to start installing msi that is
intented to be installed in PerMachine mode:
[14DC:15A8][2014-02-12T11:51:39]i001: Burn v3.8.1128.0, Windows v5.1 (Build
2600: Service Pack 3), path: D:\Documents and Settings\Administrator\My
Documents\SharpDevelop Projects\bundletest\bundletest\bin\Debug\bundletest.exe,
cmdline: ''
[14DC:15A8][2014-02-12T11:51:39]i000: Setting string variable 'WixBundleLog' to
value 'D:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\Setup_20140212115139.log'
[14DC:15A8][2014-02-12T11:51:39]i000: Setting string variable
'WixBundleOriginalSource' to value 'D:\Documents and Settings\Administrator\My
Documents\SharpDevelop Projects\bundletest\bundletest\bin\Debug\bundletest.exe'
[14DC:15A8][2014-02-12T11:51:39]i000: Setting string variable 'WixBundleName'
to value ''
[14DC:15A8][2014-02-12T11:51:39]i100: Detect begin, 1 packages
[14DC:15A8][2014-02-12T11:51:39]i103: Detected related package:
{2DDC7E93-29AB-4260-A9DB-697F7FA88157}, scope: PerUser, version: 6.4.4.0,
language: 0 operation: MajorUpgrade
[14DC:15A8][2014-02-12T11:51:39]i101: Detected package: testmsi, state: Absent,
cached: None
[14DC:15A8][2014-02-12T11:51:39]i199: Detect complete, result: 0x0
[14DC:0868][2014-02-12T11:51:41]i000: Setting numeric variable
'EulaAcceptCheckbox' to value 1
[14DC:0868][2014-02-12T11:51:45]i000: Setting numeric variable
'EulaAcceptCheckbox' to value 1
[14DC:15A8][2014-02-12T11:51:45]i200: Plan begin, 1 packages, action: Install
[14DC:15A8][2014-02-12T11:51:45]i000: Setting string variable
'WixBundleRollbackLog_testmsi' to value
'D:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\Setup_20140212115139_0_testmsi_rollback.log'
[14DC:15A8][2014-02-12T11:51:45]i000: Setting string variable
'WixBundleLog_testmsi' to value
'D:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\Setup_20140212115139_0_testmsi.log'
[14DC:15A8][2014-02-12T11:51:45]i201: Planned package: testmsi, state: Absent,
default requested: Present, ba requested: Present, execute: Install, rollback:
Uninstall, cache: Yes, uncache: No, dependency: Register
[14DC:15A8][2014-02-12T11:51:45]i299: Plan complete, result: 0x0
[14DC:15A8][2014-02-12T11:51:45]i300: Apply begin
[14DC:15A8][2014-02-12T11:54:46]e000: Error 0x800705b4: Failed to wait for
child to connect to pipe.
[14DC:15A8][2014-02-12T11:54:46]e000: Error 0x800705b4: Failed to connect to
elevated child process.
[14DC:15A8][2014-02-12T11:54:46]e000: Error 0x800705b4: Failed to actually
elevate.
[14DC:15A8][2014-02-12T11:54:46]e000: Error 0x800705b4: Failed to elevate.
[14DC:15A8][2014-02-12T11:54:46]i399: Apply complete, result: 0x800705b4,
restart: None, ba requested restart: No
Things I've tried:
1. Use ForcePerMachine key to tell Burn that I need elevation prior to
installing my msi.
2. Run bundle as common user and as admin user.
3. Run bundle in Win7 (Run as admin) - works as expected.
My bundle code:
?xml version=1.0?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi
xmlns:bal=http://schemas.microsoft.com/wix/BalExtension;
Bundle Version=1.0 Manufacturer=Man
UpgradeCode=6E06DEA1-6FF1-4E29-B3DC-A846DD804BF9
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.RtfLicense/
Chain
MsiPackage Id=testmsi Vital=yes SourceFile=D:\Documents and
Settings\Administrator\Desktop\mysql-connector-net-6.8.3.msi /
/Chain
/Bundle
/Wix
Please advise how can I avoid this strange behavior?
Best regards,
Evgeniy
--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.
Re: [WiX-users] Launch third party application installation at front
WixstBa doesn't have an option (the standard bootstrapper application (BA) you get by default). You might be able to write your own BA to do it but it's a significant amount of work. -Original Message- From: karthikrangaraj [mailto:kranga...@dnpphoto.eu] Sent: February-12-14 11:24 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Launch third party application installation at front I would like to launch a third party exe installer first so i referred this link http://stackoverflow.com/questions/19839600/wix-install-prerequisites-and-3rd-party-applications and I can launch the installer but it puts the `installer window behind the Wix installer dialog`. I have to bring the installer window `on top of the Wix installer dialog or to the front`. How can i do this with WIX 3.8? I referred the below link but I couldn't find any solution. http://stackoverflow.com/questions/21275749/needs-to-bring-sql-server-2008-r2-installation-window-in-front-of-wix-bootstrapp http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Application-launched-from-setup-is-displayed-in-background-td5960313.html http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7592625/Wix_Installation_StackOF.png My Bundle.WXS - Wix 3.8 users -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Launch-third-party-application-installation-at-front-tp7592625.html Sent from the wix-users mailing list archive at Nabble.com. -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bundle of Bundles,possible?
You have to use ExePackage and set Protocol=burn. Then the bundles will be inlined and you'll only see one gui. Wes -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: February-11-14 2:47 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bundle of Bundles,possible? Yes. -Original Message- From: tom [mailto:tomer.d...@intergraph.com] Sent: Monday, February 10, 2014 9:46 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bundle of Bundles,possible? Is it possible to chain several bundles in a single bundle such that each bundle will have ARP entry? I need to provide a unified UX for several products each of them use wix burn. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-of-Bundles-possible-tp7592513.html Sent from the wix-users mailing list archive at Nabble.com. -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using advertised shortcuts/progid in per user install
Can you use advertised shortcuts in a per user install that installs to a per
user location (e.g. LocalAppDataFolder). From my searching it doesn't appear
possible.
I asked this over a week ago but got no responses. I'll try one more time. :)
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: January-31-14 5:11 PM
To: General discussion about the WiX toolset.
Subject: [WiX-users] Using advertised shortcuts/progid in per user install
Is it possible to use advertised shortcuts/progid in a per user install. I'm
installing to the LocalAppDataFolder. I had to add a registry as keypath
because of ICE38. But now because the file is no longer the keypath I get
ICE19 and ICE50.
I don't know much about advertising. Is that a per machine thing?
Details on stackoverflow:
http://stackoverflow.com/questions/21490035/is-it-possible-to-have-advertised-shortcuts-and-progid-for-a-per-user-msi
Wes
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: January-31-14 4:43 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] XmlFile Failed to find node
Change your ElementPath to have the XPath without the /@value and add a Name
attribute to util:XmlFile with the value value. It should work.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: Jeremy [mailto:s6a9d6...@gmail.com]
Sent: Friday, January 31, 2014 2:34 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] XmlFile Failed to find node
Hello!
I am trying to use a couple XmlFile definitions to edit an app.config file
using the WiX 3.8 toolset. I got one XmlFile working perfectly, but am getting
a Failed to find node node error (-2147020584) with the others, but am a bit
stumped as to why. I am not an XPath pro but the failing XmlFile entries are
pretty much exactly like the working entry, I'm at a loss as to why one works
and the others don't.
Here is a stripped down version of the app.config. I'm trying to change that
appSettings/APIURL value element (working just fine), as well as the minlevel
element in those nlog/rules/logger entries.
configuration
configSections
section name=nlog type=NLog.Config.ConfigSectionHandler, NLog /
/configSections
nlog xmlns=http://www.nlog-project.org/schemas/NLog.xsd; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance;
targets
target name=console xsi:type=ColoredConsole layout=${longdate}
(${level}) [${callsite}]: ${message} /
target name=file xsi:type=File fileName=blah.log
layout=${longdate} (${level}) [${callsite}]: ${message} /
/targets
rules
logger name=* minlevel=Debug writeTo=file /
logger name=* minlevel=Debug writeTo=console /
/rules
/nlog
appSettings
add key=APIURL value=http://localhost/API/; /
/appSettings
/configuration
My transforms are relying on these properties if it makes any difference:
?if $(var.MyApp.Configuration) = Debug ?
Property Id=APIURL Value=http://api.test.com/; /
Property Id=NLOGLEVELFILE Value=Info /
Property Id=NLOGLEVELCONSOLE Value=Debug /
?else?
Property Id=APIURL Value=https://api.real.com/; /
Property Id=NLOGLEVELFILE Value=Warn /
Property Id=NLOGLEVELCONSOLE Value=Info /
?endif ?
Here is my first XmlFile transform which is working perfectly:
Util:XmlFile Id=UpdateApiUrl
Action=setValue
File=[MainInstallFolder]MainApp.exe.config
SelectionLanguage=XPath
Permanent=yes
PreserveModifiedDate=yes
ElementPath=/configuration/appSettings/add[\[]@key='APIURL'[\]]/@value
Value=[APIURL]
/
However when I try to target those NLog settings, these are causing the Failed
to find node errors. These three XmlFile entries are all in the same component
which contains my .exe.config file.
Util:XmlFile Id=UpdateNlogFileLogLevel
Action=setValue
File=[MainInstallFolder]MainApp.exe.config
SelectionLanguage=XPath
Permanent=yes
PreserveModifiedDate=yes
ElementPath=/configuration/nlog/rules/logger[\[]@writeTo='file'[\]]/@minlevel
Value=[NLOGLEVELFILE]
/
Util:XmlFile Id=UpdateNlogConsoleLogLevel
Action=setValue
File=[MainInstallFolder]MainApp.exe.config
SelectionLanguage=XPath
Permanent=yes
PreserveModifiedDate=yes
ElementPath=/configuration/nlog/rules/logger[\[]@writeTo='console'[\]]/@minlevel
Value=[NLOGLEVELCONSOLE]
/
I also even tried a simpler
ElementPath=/configuration/nlog/rules/logger/@minlevel but that also got
Failed to find node.
The XPath query does seem to be correct, at least a couple random online XPath
testing websites showed me I really was targeting what I'm trying
Re: [WiX-users] Bundle wxs file
Did you follow instructions here: http://wixtoolset.org/documentation/manual/v3/bundle/ ? You should have all MSIs in the Chain element in the bundle. Your right, there is no product element in burn. Did you try building it via visual studio first? -Original Message- From: GrahamAllwood [mailto:graham.allw...@live.co.uk] Sent: February-11-14 11:50 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bundle wxs file Hello. I'm tring to create a bundle and I have created my wxs file containing my Bundle element. I'm not sure what to do now! I want to use MSBUILD, but when I do, my wxs file compiles ok but LIGHT fails because it can't find a Product element. There is no Product element in my files as this is just a bundle. Should my wxs file (or one of them) contain my applications Product code as well? I think I am now a little confused as to where y bundle site in relation to my real msi product files. I thought my Bundle code would sit in a new msbuild project and just joins separate msi's and exe's together. Thanks Graham -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-wxs-file-tp7592562.html Sent from the wix-users mailing list archive at Nabble.com. -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bundle wxs file
I saw that SharpDevelop (open source version of visual studio) works with Wix. MSBuild may be good to know though. -Original Message- From: GrahamAllwood [mailto:graham.allw...@live.co.uk] Sent: February-11-14 12:39 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bundle wxs file Thanks for the reply. I did follow the docs yes, but I must have missed the two lines on the end, the ones that tell you how to compile it. I see from this I think I have missed out including the WixBalExtension. I only have VS Express so can't run Wix inside VS :( Thanks again. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-wxs-file-tp7592562p7592566.html Sent from the wix-users mailing list archive at Nabble.com. -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using advertised shortcuts/progid in per user install
I would think so too but I can't figure out how to get past the ICE warnings.
Since it's per user install in a per user location I can't have the file as the
keypath of the component I have to set a registry value as the key path or I
get ICE38. But once I do, I get ICE19 and ICE50.
To meet ICE38 I have the below but it causes the below errors:
ICE19 - 'settings' advertises component: 'CMP_Rapid'. This component cannot
be advertised because the KeyPath type disallows it
ICE19 - Shortcut: 'SHC_RunConfigExe' advertises component: 'CMP_Rapid'.
This component cannot be advertised because the KeyPath type disallows it.
ICE50 - Component 'CMP_Rapid' has an advertised shortcut, but the KeyPath
cannot be found.
DirectoryRef Id=INSTALL_FOLDER
Component Id=CMP_Rapid
Guid={9373A11C-5A3C-49E3-963D-C19B765A4285}
File Id=FILE_Rapid
Source=$(var.FilePath)\Dynagen Configurator.exe KeyPath=yes
/File
Shortcut Id=SHC_RunConfigExe
Name=DYNAGEN Configurator
Description=Opens DYNAGEN Configurator application.
Directory=ConfigShortCutDir
WorkingDirectory=INSTALL_FOLDER
Icon=ICO_RunConfigExe.exe
Advertise=yes/
ProgId Id=Rapid.drcS Icon=ICO_drcS.ico Advertise=yes
Extension Id=settings
Verb Id=Open Command=Open Argument=/so quot;%1quot; /
Verb Id=Edit Command=Edit Argument=/edit quot;%1quot;/
Verb Id=Program Command=Program Argument=/program
quot;%1quot;/
/Extension
/ProgId
RegistryValue Root=HKCU
Key=Software\Dynagen\DynagenConfigurator
Name=CMP_Rapid
Type=integer
Value=1
KeyPath=yes
/
/Component
/DirectoryRef
-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: February-11-14 2:52 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
I don't know why it wouldn't be possible. Advertised shortcuts are one of the
entry points for repair, and I'm pretty sure repair works fine on per user
installs.
The process is a potential repair - the shortcut checks that the component
target is there, and if not installs it and repairs the parent feature. If it
happens to have been a per machine install and another user is now using the
product, the repair will see that (for
example) a file in user's application data doesn't exist, so it gets installed
for that user, the install-on-demand thing.
---
Phil Wilson
On Tue, Feb 11, 2014 at 7:03 AM, Wesley Manning wmann...@dynagen.ca wrote:
Can you use advertised shortcuts in a per user install that installs to a per
user location (e.g. LocalAppDataFolder). From my searching it doesn't
appear possible.
I asked this over a week ago but got no responses. I'll try one more
time. :)
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: January-31-14 5:11 PM
To: General discussion about the WiX toolset.
Subject: [WiX-users] Using advertised shortcuts/progid in per user
install
Is it possible to use advertised shortcuts/progid in a per user install. I'm
installing to the LocalAppDataFolder. I had to add a registry as keypath
because of ICE38. But now because the file is no longer the keypath I get
ICE19 and ICE50.
I don't know much about advertising. Is that a per machine thing?
Details on stackoverflow:
http://stackoverflow.com/questions/21490035/is-it-possible-to-have-adv
ertised-shortcuts-and-progid-for-a-per-user-msi
Wes
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: January-31-14 4:43 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] XmlFile Failed to find node
Change your ElementPath to have the XPath without the /@value and add a Name
attribute to util:XmlFile with the value value. It should work.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.(r)
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: Jeremy [mailto:s6a9d6...@gmail.com]
Sent: Friday, January 31, 2014 2:34 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] XmlFile Failed to find node
Hello!
I am trying to use a couple XmlFile definitions to edit an app.config file
using the WiX 3.8 toolset. I got one XmlFile working perfectly, but am
getting a Failed to find node node error (-2147020584) with the others, but
am a bit stumped as to why. I am not an XPath pro but the failing XmlFile
entries are pretty much exactly like the working entry, I'm at a loss as to
why one works and the others don't.
Here
Re: [WiX-users] Using advertised shortcuts/progid in per user install
Rob,
The error's not because I made a registry entry the keypath in that component?
I know FILE_Rapid is not the KeyPath as the registry entry is. I had to do
that to meet ICE38 (every component being installed under the current user's
profile also specifies a registry key under the HKEY_CURRENT_USER root in the
KeyPath column of the Component table).
Wes
-Original Message-
From: Rob Mensching [mailto:r...@firegiant.com]
Sent: February-11-14 4:13 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
That error is saying the Component is the KeyPath (thus a Directory) not the
file. Something is causing FILE_Rapid to not be the KeyPath.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: Tuesday, February 11, 2014 11:32 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
I would think so too but I can't figure out how to get past the ICE warnings.
Since it's per user install in a per user location I can't have the file as the
keypath of the component I have to set a registry value as the key path or I
get ICE38. But once I do, I get ICE19 and ICE50.
To meet ICE38 I have the below but it causes the below errors:
ICE19 - 'settings' advertises component: 'CMP_Rapid'. This component cannot
be advertised because the KeyPath type disallows it
ICE19 - Shortcut: 'SHC_RunConfigExe' advertises component: 'CMP_Rapid'.
This component cannot be advertised because the KeyPath type disallows it.
ICE50 - Component 'CMP_Rapid' has an advertised shortcut, but the KeyPath
cannot be found.
DirectoryRef Id=INSTALL_FOLDER
Component Id=CMP_Rapid
Guid={9373A11C-5A3C-49E3-963D-C19B765A4285}
File Id=FILE_Rapid
Source=$(var.FilePath)\Dynagen Configurator.exe KeyPath=yes
/File
Shortcut Id=SHC_RunConfigExe
Name=DYNAGEN Configurator
Description=Opens DYNAGEN Configurator application.
Directory=ConfigShortCutDir
WorkingDirectory=INSTALL_FOLDER
Icon=ICO_RunConfigExe.exe
Advertise=yes/
ProgId Id=Rapid.drcS Icon=ICO_drcS.ico Advertise=yes
Extension Id=settings
Verb Id=Open Command=Open Argument=/so quot;%1quot; /
Verb Id=Edit Command=Edit Argument=/edit quot;%1quot;/
Verb Id=Program Command=Program Argument=/program
quot;%1quot;/
/Extension
/ProgId
RegistryValue Root=HKCU
Key=Software\Dynagen\DynagenConfigurator
Name=CMP_Rapid
Type=integer
Value=1
KeyPath=yes
/
/Component
/DirectoryRef
-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: February-11-14 2:52 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
I don't know why it wouldn't be possible. Advertised shortcuts are one of the
entry points for repair, and I'm pretty sure repair works fine on per user
installs.
The process is a potential repair - the shortcut checks that the component
target is there, and if not installs it and repairs the parent feature. If it
happens to have been a per machine install and another user is now using the
product, the repair will see that (for
example) a file in user's application data doesn't exist, so it gets installed
for that user, the install-on-demand thing.
---
Phil Wilson
On Tue, Feb 11, 2014 at 7:03 AM, Wesley Manning wmann...@dynagen.ca wrote:
Can you use advertised shortcuts in a per user install that installs to a per
user location (e.g. LocalAppDataFolder). From my searching it doesn't
appear possible.
I asked this over a week ago but got no responses. I'll try one more
time. :)
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: January-31-14 5:11 PM
To: General discussion about the WiX toolset.
Subject: [WiX-users] Using advertised shortcuts/progid in per user
install
Is it possible to use advertised shortcuts/progid in a per user install. I'm
installing to the LocalAppDataFolder. I had to add a registry as keypath
because of ICE38. But now because the file is no longer the keypath I get
ICE19 and ICE50.
I don't know much about advertising. Is that a per machine thing?
Details on stackoverflow:
http://stackoverflow.com/questions/21490035/is-it-possible-to-have-adv
ertised-shortcuts-and-progid-for-a-per-user-msi
Wes
-Original Message-
From: John Cooper [mailto:jocoo
Re: [WiX-users] Using advertised shortcuts/progid in per user install
Sorry I copied it after I was playing around with it. I did have the keypath
only set to the registry value.
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: February-11-14 5:15 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
If that is your intent, then the KeyPath element should be removed from the
File element. As it stands now, your authoring has both the File element and
the RegistryValue element as KeyPath's.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: Tuesday, February 11, 2014 3:10 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
Rob,
The error's not because I made a registry entry the keypath in that component?
I know FILE_Rapid is not the KeyPath as the registry entry is. I had to do
that to meet ICE38 (every component being installed under the current user's
profile also specifies a registry key under the HKEY_CURRENT_USER root in the
KeyPath column of the Component table).
Wes
-Original Message-
From: Rob Mensching [mailto:r...@firegiant.com]
Sent: February-11-14 4:13 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
That error is saying the Component is the KeyPath (thus a Directory) not the
file. Something is causing FILE_Rapid to not be the KeyPath.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: Tuesday, February 11, 2014 11:32 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
I would think so too but I can't figure out how to get past the ICE warnings.
Since it's per user install in a per user location I can't have the file as the
keypath of the component I have to set a registry value as the key path or I
get ICE38. But once I do, I get ICE19 and ICE50.
To meet ICE38 I have the below but it causes the below errors:
ICE19 - 'settings' advertises component: 'CMP_Rapid'. This component cannot
be advertised because the KeyPath type disallows it
ICE19 - Shortcut: 'SHC_RunConfigExe' advertises component: 'CMP_Rapid'.
This component cannot be advertised because the KeyPath type disallows it.
ICE50 - Component 'CMP_Rapid' has an advertised shortcut, but the KeyPath
cannot be found.
DirectoryRef Id=INSTALL_FOLDER
Component Id=CMP_Rapid
Guid={9373A11C-5A3C-49E3-963D-C19B765A4285}
File Id=FILE_Rapid
Source=$(var.FilePath)\Dynagen Configurator.exe KeyPath=yes
/File
Shortcut Id=SHC_RunConfigExe
Name=DYNAGEN Configurator
Description=Opens DYNAGEN Configurator application.
Directory=ConfigShortCutDir
WorkingDirectory=INSTALL_FOLDER
Icon=ICO_RunConfigExe.exe
Advertise=yes/
ProgId Id=Rapid.drcS Icon=ICO_drcS.ico Advertise=yes
Extension Id=settings
Verb Id=Open Command=Open Argument=/so quot;%1quot; /
Verb Id=Edit Command=Edit Argument=/edit quot;%1quot;/
Verb Id=Program Command=Program Argument=/program
quot;%1quot;/
/Extension
/ProgId
RegistryValue Root=HKCU
Key=Software\Dynagen\DynagenConfigurator
Name=CMP_Rapid
Type=integer
Value=1
KeyPath=yes
/
/Component
/DirectoryRef
-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: February-11-14 2:52 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
I don't know why it wouldn't be possible. Advertised shortcuts are one of the
entry points for repair, and I'm pretty sure repair works fine on per user
installs.
The process is a potential repair - the shortcut checks that the component
target is there, and if not installs it and repairs the parent feature. If it
happens to have been a per machine install and another user is now using the
product, the repair will see that (for
example) a file in user's application data doesn't exist, so it gets installed
for that user, the install-on-demand thing.
---
Phil Wilson
On Tue, Feb 11, 2014 at 7:03 AM, Wesley Manning wmann...@dynagen.ca wrote:
Can you use advertised shortcuts in a per user install
Re: [WiX-users] Using advertised shortcuts/progid in per user install
ICE38 is an error when I build in wix. Can you ignore ICE38 errors?
Error 1 ICE38: Component CMP_Rapid installs to user profile. It must
use a registry key under HKCU as its KeyPath, not a file. C:\Users\Wesley
Manning\Desktop\APP-0014, RapidCore Configurator\Installers\ShellSetup\Core.wxs
97 1 ShellSetup
I'm installing to the LocalAppDataFolder.
Wes
-Original Message-
From: Bryan Wolf [mailto:brw...@jackhenry.com]
Sent: February-11-14 6:15 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
Since that is the case, ICE38 is (in my opinion) incorrect and you will want to
ignore it. ICE38 implies you are installing per-user resources in the context
of a per-machine installation but never verifies that this is so.
Actually authoring a per-user install requires that you ignore ICE38 because it
won't ever be accurate for that world.
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: Tuesday, February 11, 2014 3:29 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
Sorry I copied it after I was playing around with it. I did have the keypath
only set to the registry value.
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: February-11-14 5:15 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
If that is your intent, then the KeyPath element should be removed from the
File element. As it stands now, your authoring has both the File element and
the RegistryValue element as KeyPath's.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: Tuesday, February 11, 2014 3:10 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
Rob,
The error's not because I made a registry entry the keypath in that component?
I know FILE_Rapid is not the KeyPath as the registry entry is. I had to do
that to meet ICE38 (every component being installed under the current user's
profile also specifies a registry key under the HKEY_CURRENT_USER root in the
KeyPath column of the Component table).
Wes
-Original Message-
From: Rob Mensching [mailto:r...@firegiant.com]
Sent: February-11-14 4:13 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
That error is saying the Component is the KeyPath (thus a Directory) not the
file. Something is causing FILE_Rapid to not be the KeyPath.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: Tuesday, February 11, 2014 11:32 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
I would think so too but I can't figure out how to get past the ICE warnings.
Since it's per user install in a per user location I can't have the file as the
keypath of the component I have to set a registry value as the key path or I
get ICE38. But once I do, I get ICE19 and ICE50.
To meet ICE38 I have the below but it causes the below errors:
ICE19 - 'settings' advertises component: 'CMP_Rapid'. This component cannot
be advertised because the KeyPath type disallows it
ICE19 - Shortcut: 'SHC_RunConfigExe' advertises component: 'CMP_Rapid'.
This component cannot be advertised because the KeyPath type disallows it.
ICE50 - Component 'CMP_Rapid' has an advertised shortcut, but the KeyPath
cannot be found.
DirectoryRef Id=INSTALL_FOLDER
Component Id=CMP_Rapid
Guid={9373A11C-5A3C-49E3-963D-C19B765A4285}
File Id=FILE_Rapid
Source=$(var.FilePath)\Dynagen Configurator.exe KeyPath=yes
/File
Shortcut Id=SHC_RunConfigExe
Name=DYNAGEN Configurator
Description=Opens DYNAGEN Configurator application.
Directory=ConfigShortCutDir
WorkingDirectory=INSTALL_FOLDER
Icon=ICO_RunConfigExe.exe
Advertise=yes/
ProgId Id=Rapid.drcS Icon=ICO_drcS.ico Advertise=yes
Extension Id=settings
Verb Id=Open Command=Open Argument=/so quot;%1quot; /
Verb Id=Edit Command=Edit Argument=/edit quot;%1quot;/
Verb Id=Program Command=Program Argument=/program
quot;%1quot;/
/Extension
/ProgId
RegistryValue Root=HKCU
Re: [WiX-users] Using advertised shortcuts/progid in per user install
According to here a HKCU keypath is important for self-healing:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/A-method-for-avoiding-ICE38-error-td712044.html.
So looks like not a good idea to ignore it.
Wes
-Original Message-
From: Bryan Wolf [mailto:brw...@jackhenry.com]
Sent: February-11-14 6:15 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
Since that is the case, ICE38 is (in my opinion) incorrect and you will want to
ignore it. ICE38 implies you are installing per-user resources in the context
of a per-machine installation but never verifies that this is so.
Actually authoring a per-user install requires that you ignore ICE38 because it
won't ever be accurate for that world.
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: Tuesday, February 11, 2014 3:29 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
Sorry I copied it after I was playing around with it. I did have the keypath
only set to the registry value.
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: February-11-14 5:15 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
If that is your intent, then the KeyPath element should be removed from the
File element. As it stands now, your authoring has both the File element and
the RegistryValue element as KeyPath's.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: Tuesday, February 11, 2014 3:10 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
Rob,
The error's not because I made a registry entry the keypath in that component?
I know FILE_Rapid is not the KeyPath as the registry entry is. I had to do
that to meet ICE38 (every component being installed under the current user's
profile also specifies a registry key under the HKEY_CURRENT_USER root in the
KeyPath column of the Component table).
Wes
-Original Message-
From: Rob Mensching [mailto:r...@firegiant.com]
Sent: February-11-14 4:13 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
That error is saying the Component is the KeyPath (thus a Directory) not the
file. Something is causing FILE_Rapid to not be the KeyPath.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: Tuesday, February 11, 2014 11:32 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
I would think so too but I can't figure out how to get past the ICE warnings.
Since it's per user install in a per user location I can't have the file as the
keypath of the component I have to set a registry value as the key path or I
get ICE38. But once I do, I get ICE19 and ICE50.
To meet ICE38 I have the below but it causes the below errors:
ICE19 - 'settings' advertises component: 'CMP_Rapid'. This component cannot
be advertised because the KeyPath type disallows it
ICE19 - Shortcut: 'SHC_RunConfigExe' advertises component: 'CMP_Rapid'.
This component cannot be advertised because the KeyPath type disallows it.
ICE50 - Component 'CMP_Rapid' has an advertised shortcut, but the KeyPath
cannot be found.
DirectoryRef Id=INSTALL_FOLDER
Component Id=CMP_Rapid
Guid={9373A11C-5A3C-49E3-963D-C19B765A4285}
File Id=FILE_Rapid
Source=$(var.FilePath)\Dynagen Configurator.exe KeyPath=yes
/File
Shortcut Id=SHC_RunConfigExe
Name=DYNAGEN Configurator
Description=Opens DYNAGEN Configurator application.
Directory=ConfigShortCutDir
WorkingDirectory=INSTALL_FOLDER
Icon=ICO_RunConfigExe.exe
Advertise=yes/
ProgId Id=Rapid.drcS Icon=ICO_drcS.ico Advertise=yes
Extension Id=settings
Verb Id=Open Command=Open Argument=/so quot;%1quot; /
Verb Id=Edit Command=Edit Argument=/edit quot;%1quot;/
Verb Id=Program Command=Program Argument=/program
quot;%1quot;/
/Extension
/ProgId
RegistryValue Root=HKCU
Key=Software\Dynagen\DynagenConfigurator
Name=CMP_Rapid
Type=integer
Value=1
Re: [WiX-users] Bundle packages in ARP
Are they MSI packages? If so set visible to true. The bundle will still appear in ARP. EXEpackages you can't do this. -Original Message- From: GrahamAllwood [mailto:graham.allw...@live.co.uk] Sent: February-11-14 6:45 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bundle packages in ARP Hi I have a Bundle that contains 4 Sql Server Components (SMO, RMO etc) and finally my own APP msi file. Is it possible to have all the 5 separate installs to appear in Add/Remove programs, or does my Bundle have to act as the parent to all of them, and it is only the Bundle that can appear in ARP? I'm using Bundles as a way of installing prerequisites to my own app. Maybe I should go back to using the older MSBuild SDK wayof creating a bootstrapping setup.exe? Thanks -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-packages-in-ARP-tp7592597.html Sent from the wix-users mailing list archive at Nabble.com. -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using advertised shortcuts/progid in per user install
It is a 100% pure per user install. :) I'm installing to AppData/Local.
Just testing the waters with per user installs since I only did per machine
before. Surprisingly not much guidance out there which surprises me since I
thought Microsoft encourages per user. I know they did put in better support
for Windows 7 and above (with the programfiles routing to appdata/programs.
But I have to support XP and Vista as well.
I will now try to ignore ICE38 and see if that fixes the issues.
Thanks.
Wes
-Original Message-
From: Bryan Wolf [mailto:brw...@jackhenry.com]
Sent: February-11-14 6:50 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
The issue involved in that requires you log in via another user, which is
impossible for a per-user installation. If you are installing per-machine then
ICE38 does, in fact, apply to you, you cannot use an advertised shortcut here,
and probably should seriously reconsider installing an executable file to
%appdata%.
The 64,000 question is: are you performing a per-user or per-machine
installation?
If it's the case where you are performing per-user installs then you can edit
your wixproj file to ignore certain ICE errors/warnings in the VS properties
page or with -sice {ice_id} command line parameter. ICE38 is incorrect in this
case.
If it's the case where you are performing per-machine installs then advertised
shortcuts to per-user resources won't be in your future.
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: Tuesday, February 11, 2014 4:44 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
According to here a HKCU keypath is important for self-healing:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/A-method-for-avoiding-ICE38-error-td712044.html.
So looks like not a good idea to ignore it.
Wes
-Original Message-
From: Bryan Wolf [mailto:brw...@jackhenry.com]
Sent: February-11-14 6:15 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
Since that is the case, ICE38 is (in my opinion) incorrect and you will want to
ignore it. ICE38 implies you are installing per-user resources in the context
of a per-machine installation but never verifies that this is so.
Actually authoring a per-user install requires that you ignore ICE38 because it
won't ever be accurate for that world.
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: Tuesday, February 11, 2014 3:29 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
Sorry I copied it after I was playing around with it. I did have the keypath
only set to the registry value.
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: February-11-14 5:15 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
If that is your intent, then the KeyPath element should be removed from the
File element. As it stands now, your authoring has both the File element and
the RegistryValue element as KeyPath's.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: Tuesday, February 11, 2014 3:10 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
Rob,
The error's not because I made a registry entry the keypath in that component?
I know FILE_Rapid is not the KeyPath as the registry entry is. I had to do
that to meet ICE38 (every component being installed under the current user's
profile also specifies a registry key under the HKEY_CURRENT_USER root in the
KeyPath column of the Component table).
Wes
-Original Message-
From: Rob Mensching [mailto:r...@firegiant.com]
Sent: February-11-14 4:13 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
That error is saying the Component is the KeyPath (thus a Directory) not the
file. Something is causing FILE_Rapid to not be the KeyPath.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: Tuesday, February 11, 2014 11:32 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
I would think so too but I can't figure out how
Re: [WiX-users] Using advertised shortcuts/progid in per user install
Ignoring ICE38 worked. I also ignored ICE91 as well but that was just a
warning anyways.
-Original Message-
From: Bryan Wolf [mailto:brw...@jackhenry.com]
Sent: February-11-14 7:33 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
I also love the idea of per-user installations, but they aren't the best
supported thing from an authoring perspective that's for-sure. From having used
MSI at varying levels for a number of years, the only two rules I have come up
with is anything that is easy isn't and that I/we/they probably forgot about
rollback.
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: Tuesday, February 11, 2014 5:00 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
It is a 100% pure per user install. :) I'm installing to AppData/Local.
Just testing the waters with per user installs since I only did per machine
before. Surprisingly not much guidance out there which surprises me since I
thought Microsoft encourages per user. I know they did put in better support
for Windows 7 and above (with the programfiles routing to appdata/programs.
But I have to support XP and Vista as well.
I will now try to ignore ICE38 and see if that fixes the issues.
Thanks.
Wes
-Original Message-
From: Bryan Wolf [mailto:brw...@jackhenry.com]
Sent: February-11-14 6:50 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
The issue involved in that requires you log in via another user, which is
impossible for a per-user installation. If you are installing per-machine then
ICE38 does, in fact, apply to you, you cannot use an advertised shortcut here,
and probably should seriously reconsider installing an executable file to
%appdata%.
The 64,000 question is: are you performing a per-user or per-machine
installation?
If it's the case where you are performing per-user installs then you can edit
your wixproj file to ignore certain ICE errors/warnings in the VS properties
page or with -sice {ice_id} command line parameter. ICE38 is incorrect in this
case.
If it's the case where you are performing per-machine installs then advertised
shortcuts to per-user resources won't be in your future.
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: Tuesday, February 11, 2014 4:44 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
According to here a HKCU keypath is important for self-healing:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/A-method-for-avoiding-ICE38-error-td712044.html.
So looks like not a good idea to ignore it.
Wes
-Original Message-
From: Bryan Wolf [mailto:brw...@jackhenry.com]
Sent: February-11-14 6:15 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
Since that is the case, ICE38 is (in my opinion) incorrect and you will want to
ignore it. ICE38 implies you are installing per-user resources in the context
of a per-machine installation but never verifies that this is so.
Actually authoring a per-user install requires that you ignore ICE38 because it
won't ever be accurate for that world.
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: Tuesday, February 11, 2014 3:29 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
Sorry I copied it after I was playing around with it. I did have the keypath
only set to the registry value.
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: February-11-14 5:15 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
If that is your intent, then the KeyPath element should be removed from the
File element. As it stands now, your authoring has both the File element and
the RegistryValue element as KeyPath's.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: Tuesday, February 11, 2014 3:10 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Using advertised shortcuts/progid in per user install
Rob,
The error's not because I made a registry entry the keypath in that component?
I know FILE_Rapid is not the KeyPath as the registry entry is. I had to do
that to meet ICE38 (every component being installed under the current user's
profile also specifies a registry key under
[WiX-users] Bundle doesn't disable system restore on sub-bundles
Hi, Burn disables system restore on MSIs but it doesn't on Bundles it appears. I confirmed in the log. Would this be a feature request or bug? My main bundle installs three add-on bundles. It takes at least 1 to 2 minutes per bundle for system restore. I'd like to skip system restore since the main bundle does it already. These add-ons may be installed outside the main bundle so I don't want to set DisableSystemRestore on the chain. Wes -- Androi apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bundle doesn't disable system restore on sub-bundles
Ok added it to that issue: http://wixtoolset.org/issues/3693/. Wes -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: February-10-14 5:23 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bundle doesn't disable system restore on sub-bundles Feature request. Probably something to include with the BundlePackage feature request. -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: Monday, February 10, 2014 12:21 PM To: General discussion about the WiX toolset. Subject: [WiX-users] Bundle doesn't disable system restore on sub-bundles Hi, Burn disables system restore on MSIs but it doesn't on Bundles it appears. I confirmed in the log. Would this be a feature request or bug? My main bundle installs three add-on bundles. It takes at least 1 to 2 minutes per bundle for system restore. I'd like to skip system restore since the main bundle does it already. These add-ons may be installed outside the main bundle so I don't want to set DisableSystemRestore on the chain. Wes -- Androi apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bundle doesn't disable system restore on sub-bundles
Looks like I haven't setup my ExePackages elements correctly. So you need to set a detect condition on ExePackage if it's a bundle and even if Protocol=burn is set? Just wanted to confirm. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: February-10-14 5:23 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bundle doesn't disable system restore on sub-bundles Feature request. Probably something to include with the BundlePackage feature request. -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: Monday, February 10, 2014 12:21 PM To: General discussion about the WiX toolset. Subject: [WiX-users] Bundle doesn't disable system restore on sub-bundles Hi, Burn disables system restore on MSIs but it doesn't on Bundles it appears. I confirmed in the log. Would this be a feature request or bug? My main bundle installs three add-on bundles. It takes at least 1 to 2 minutes per bundle for system restore. I'd like to skip system restore since the main bundle does it already. These add-ons may be installed outside the main bundle so I don't want to set DisableSystemRestore on the chain. Wes -- Androi apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn bundle - mix of per-user and per-machine MSIs
FYI: I just tested this and it does the upgrade no problem. Background: My bundle is composed of a per user MSI which installs my application and three per machine MSIs which installs two drivers and a certificate to prevent the do you want to allow this driver from unknown company popup. I do have a problem where multiple users install the bundle. If one user goes to uninstall it, the bundle uninstalls the per machine MSIs for all users. I found Bug 3540 | Error when upgrading a bundle with mixed privilege packages that said this is by design: Due to cross-scope scenarios that could be broken - like installing per-macine packages like VC runtime or .NET followed by per-user packages for your apps - we've had to limit the ref-counting feature to a single scope. I.e., if the bundle is a per-machine scope (all per-machine packages or a per-user scope, it will work. But if there is even one per-user package - even if you're not installing it - only per-user packages will be able to use the ref-counting scenario. This at least enables the runtime scenarios mentioned above. I could see how .net or VC runtime could mess up ref counting. Would it be a good feature request to default to no ref-counting for per machine packages and allow the user to specify which per machine packages would get reference counting? And/or don't do ref counting on permanent bundles but do so on all other per machine bundles? I imagine .net and VC runtime would be marked as permanent. I don't get the error listed in the bug though so that's good. One solution is I could mark the driver installers permanent and let the user uninstall them manually. Wes -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: October-31-13 10:07 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Burn bundle - mix of per-user and per-machine MSIs Will have to do a test... -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: October-31-13 12:42 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Burn bundle - mix of per-user and per-machine MSIs I honestly don't remember... -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: Wednesday, October 30, 2013 12:22 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Burn bundle - mix of per-user and per-machine MSIs Thanks. That makes sense. I'm installing drivers so need to have both. Can a per-user bundle upgrade or uninstall a per-machine bundle via relatedbundle element's attribute Action set to Upgrade? I have a per-machine bundle now. Thinking of switching my app to per-user. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: October-30-13 4:12 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Burn bundle - mix of per-user and per-machine MSIs Yes. Note: the presence of a per-user package makes the bundle per-user. -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: Wednesday, October 30, 2013 12:10 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Burn bundle - mix of per-user and per-machine MSIs Hi, Can burn handle a mix of per-machine and per-user MSI packages? I thought I read somewhere it can't but can't find it. Wes -Original Message- From: Phil Wilson [mailto:phildgwil...@gmail.com] Sent: August-23-13 3:43 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Fallback when not getting admin rights I forget what the DropBox install experience was, but when I look at those shell extensions they are all in HKCU, so they are per-user and not per-system. That might work for you too. Phil Wilson On Fri, Aug 23, 2013 at 1:59 AM, Trond Andersen trond.ander...@gmail.comwrote: I have an application which uses Shell extensions to add a menu in Windows Explorer, however I would like the installer to have a fallback if the user is not able to give the installer admin rights in which the user can access the functionality without using menus/toolbar in Windows Explorer. The Dropbox installer does the same thing. Does anyone have an example or other resources which could help me getting this working. For information - I'm using WIX 3.7 and Burn bootstrapper. Is this something the bootstrapper should handle? Will the Burn bootstrapper be able to do this or do I have to use a different bootstrapper/modify Burn? -- Trond -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.c lktrk
[WiX-users] Using advertised shortcuts/progid in per user install
Is it possible to use advertised shortcuts/progid in a per user install. I'm
installing to the LocalAppDataFolder. I had to add a registry as keypath
because of ICE38. But now because the file is no longer the keypath I get
ICE19 and ICE50.
I don't know much about advertising. Is that a per machine thing?
Details on stackoverflow:
http://stackoverflow.com/questions/21490035/is-it-possible-to-have-advertised-shortcuts-and-progid-for-a-per-user-msi
Wes
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: January-31-14 4:43 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] XmlFile Failed to find node
Change your ElementPath to have the XPath without the /@value and add a Name
attribute to util:XmlFile with the value value. It should work.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: Jeremy [mailto:s6a9d6...@gmail.com]
Sent: Friday, January 31, 2014 2:34 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] XmlFile Failed to find node
Hello!
I am trying to use a couple XmlFile definitions to edit an app.config file
using the WiX 3.8 toolset. I got one XmlFile working perfectly, but am getting
a Failed to find node node error (-2147020584) with the others, but am a bit
stumped as to why. I am not an XPath pro but the failing XmlFile entries are
pretty much exactly like the working entry, I'm at a loss as to why one works
and the others don't.
Here is a stripped down version of the app.config. I'm trying to change that
appSettings/APIURL value element (working just fine), as well as the minlevel
element in those nlog/rules/logger entries.
configuration
configSections
section name=nlog type=NLog.Config.ConfigSectionHandler, NLog /
/configSections
nlog xmlns=http://www.nlog-project.org/schemas/NLog.xsd; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance;
targets
target name=console xsi:type=ColoredConsole layout=${longdate}
(${level}) [${callsite}]: ${message} /
target name=file xsi:type=File fileName=blah.log
layout=${longdate} (${level}) [${callsite}]: ${message} /
/targets
rules
logger name=* minlevel=Debug writeTo=file /
logger name=* minlevel=Debug writeTo=console /
/rules
/nlog
appSettings
add key=APIURL value=http://localhost/API/; /
/appSettings
/configuration
My transforms are relying on these properties if it makes any difference:
?if $(var.MyApp.Configuration) = Debug ?
Property Id=APIURL Value=http://api.test.com/; /
Property Id=NLOGLEVELFILE Value=Info /
Property Id=NLOGLEVELCONSOLE Value=Debug /
?else?
Property Id=APIURL Value=https://api.real.com/; /
Property Id=NLOGLEVELFILE Value=Warn /
Property Id=NLOGLEVELCONSOLE Value=Info /
?endif ?
Here is my first XmlFile transform which is working perfectly:
Util:XmlFile Id=UpdateApiUrl
Action=setValue
File=[MainInstallFolder]MainApp.exe.config
SelectionLanguage=XPath
Permanent=yes
PreserveModifiedDate=yes
ElementPath=/configuration/appSettings/add[\[]@key='APIURL'[\]]/@value
Value=[APIURL]
/
However when I try to target those NLog settings, these are causing the Failed
to find node errors. These three XmlFile entries are all in the same component
which contains my .exe.config file.
Util:XmlFile Id=UpdateNlogFileLogLevel
Action=setValue
File=[MainInstallFolder]MainApp.exe.config
SelectionLanguage=XPath
Permanent=yes
PreserveModifiedDate=yes
ElementPath=/configuration/nlog/rules/logger[\[]@writeTo='file'[\]]/@minlevel
Value=[NLOGLEVELFILE]
/
Util:XmlFile Id=UpdateNlogConsoleLogLevel
Action=setValue
File=[MainInstallFolder]MainApp.exe.config
SelectionLanguage=XPath
Permanent=yes
PreserveModifiedDate=yes
ElementPath=/configuration/nlog/rules/logger[\[]@writeTo='console'[\]]/@minlevel
Value=[NLOGLEVELCONSOLE]
/
I also even tried a simpler
ElementPath=/configuration/nlog/rules/logger/@minlevel but that also got
Failed to find node.
The XPath query does seem to be correct, at least a couple random online XPath
testing websites showed me I really was targeting what I'm trying to target. I
also removed the name=* from those logger lines in the xml config, thinking
maybe that was throwing off the parsing somehow, but that didn't make any
difference either. I also tried re-ordering the XmlFile entries thinking maybe
the first one would work for some strange reason and all extra ones never will
work, but that didn't help either.
Thanks for any and all assistance!
Best wishes
Jeremy
Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper
I'm not writing a per user package. I was just curious. -Original Message- From: Blair Murri [mailto:os...@live.com] Sent: January-28-14 6:05 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper If your MSI package is always per-user, why wouldn’t you just retrieve and use the path of FOLDERID_UserProgramFiles instead of ProgramFilesFolder? Blair From: Sascha Sertel Sent: Monday, January 27, 2014 10:58 AM To: General discussion for Windows Installer XML toolset. With MSIINSTALLPERUSER=1 on Windows 7 and above the ProgramFilesFolder location gets automatically rerouted to LocalAppDataFolder if running a per-User install. This MSDN article shows where all the folder locations point to in per-machine vs. per-user installs: http://msdn.microsoft.com/en-us/library/windows/desktop/dd765197(v=vs.85).aspx // Sascha On Mon, Jan 27, 2014 at 8:46 AM, Rob Mensching r...@robmensching.com wrote: No. That's a per-machine location. -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: Monday, January 27, 2014 7:54 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper So per users can installer to C:\Program Files\ ? -Original Message- From: Sascha Sertel [mailto:sascha.ser...@gmail.com] Sent: January-24-14 6:45 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper No I did not set ALLUSERS directly. On Fri, Jan 24, 2014 at 2:32 PM, Rob Mensching r...@robmensching.com wrote: Did you have ALLUSERS set the whole time as well? -Original Message- From: Sascha Sertel [mailto:sascha.ser...@gmail.com] Sent: Friday, January 24, 2014 2:21 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper I always had Package/@InstallScope='perUser', that never changed. But the key thing for me to get it to work was MSIINSTALLPERUSER=1, without it I kept getting the insufficient privileges error both in the bundle and when running the stand-alone MSI. // Sascha On Fri, Jan 24, 2014 at 1:34 PM, Rob Mensching r...@robmensching.com wrote: Burn does lots of work to make this scenario work (per-machine prerequisites and one or more per-user packages). It's unique among bootstrappers because it does it in all the right user contexts and all that. I saw a follow up email from you on a fork of this thread that found the most important thing: You need to make sure your per-user package is truly per-user. The easiest way to do that is to use: Package/@InstallScope='perUser'. -Original Message- From: Sascha Sertel [mailto:sascha.ser...@gmail.com] Sent: Friday, January 24, 2014 12:18 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper Let me clarify a bit to tell you what I'm trying to do, what I've tried, and what I thought isn't currently working: Goal: Build a WiX installer for my software which installs .NET Framework 4.5.1 if needed, C++ Runtime if needed, and my software. My software needs to be installed per-user, i.e. it should go into AppData\Local, not Program Files. My understanding is - To accomplish my goal I need three components: .NET Framework 4.5.1 package (provided by NetFx extension), C++ Runtime merge module, and MSI for my software - The two prerequisites needs to be installed on a per-machine (elevated) level, my software on a per-user level This is what I've tried: Attempt 1. Created a WiX bundle with two packages inside the Chain element: A PackageGroupRef for NetFx451Web, and an MsiPackage that includes my software as well as the C++ merge module. Problem: This wouldn't build because my software Package had InstallScope perUser but apparently the C++ merge module forced ALLUSERS=1 which conflicted with the perUser setting. This problem went away when I took the merge module out of the package. Attempt 2: Created a WiX bundle with three packages inside the Chain element: A PackageGroupRef for NetFx451Web, an MsiPackage for my C++ Runtime merge module (InstallScope perMachine), and an MsiPackage for my software (InstallScope perUser). Problem: When running the resulting bundle it would prompt for elevation (which is fine), then install .NET Framework fine, then install the merge module fine, but throw an error for my perUser package: The installer has insufficient privileges to access this directory: C:\Program Files\product. The installation cannot continue. Log on as administrator or contact your system
Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper
So per users can installer to C:\Program Files\ ? -Original Message- From: Sascha Sertel [mailto:sascha.ser...@gmail.com] Sent: January-24-14 6:45 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper No I did not set ALLUSERS directly. On Fri, Jan 24, 2014 at 2:32 PM, Rob Mensching r...@robmensching.com wrote: Did you have ALLUSERS set the whole time as well? -Original Message- From: Sascha Sertel [mailto:sascha.ser...@gmail.com] Sent: Friday, January 24, 2014 2:21 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper I always had Package/@InstallScope='perUser', that never changed. But the key thing for me to get it to work was MSIINSTALLPERUSER=1, without it I kept getting the insufficient privileges error both in the bundle and when running the stand-alone MSI. // Sascha On Fri, Jan 24, 2014 at 1:34 PM, Rob Mensching r...@robmensching.com wrote: Burn does lots of work to make this scenario work (per-machine prerequisites and one or more per-user packages). It's unique among bootstrappers because it does it in all the right user contexts and all that. I saw a follow up email from you on a fork of this thread that found the most important thing: You need to make sure your per-user package is truly per-user. The easiest way to do that is to use: Package/@InstallScope='perUser'. -Original Message- From: Sascha Sertel [mailto:sascha.ser...@gmail.com] Sent: Friday, January 24, 2014 12:18 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper Let me clarify a bit to tell you what I'm trying to do, what I've tried, and what I thought isn't currently working: Goal: Build a WiX installer for my software which installs .NET Framework 4.5.1 if needed, C++ Runtime if needed, and my software. My software needs to be installed per-user, i.e. it should go into AppData\Local, not Program Files. My understanding is - To accomplish my goal I need three components: .NET Framework 4.5.1 package (provided by NetFx extension), C++ Runtime merge module, and MSI for my software - The two prerequisites needs to be installed on a per-machine (elevated) level, my software on a per-user level This is what I've tried: Attempt 1. Created a WiX bundle with two packages inside the Chain element: A PackageGroupRef for NetFx451Web, and an MsiPackage that includes my software as well as the C++ merge module. Problem: This wouldn't build because my software Package had InstallScope perUser but apparently the C++ merge module forced ALLUSERS=1 which conflicted with the perUser setting. This problem went away when I took the merge module out of the package. Attempt 2: Created a WiX bundle with three packages inside the Chain element: A PackageGroupRef for NetFx451Web, an MsiPackage for my C++ Runtime merge module (InstallScope perMachine), and an MsiPackage for my software (InstallScope perUser). Problem: When running the resulting bundle it would prompt for elevation (which is fine), then install .NET Framework fine, then install the merge module fine, but throw an error for my perUser package: The installer has insufficient privileges to access this directory: C:\Program Files\product. The installation cannot continue. Log on as administrator or contact your system administrator. My software package uses a folder underneath ProgramFilesFolder as the target folder and I was expecting that on Win7 and up in a per-user install it automatically translates to LocalAppDataFolder instead. I thought from what I had gathered in this thread is that once the bundle gets elevated permissions it will also try to run my software package in forced per machine mode but without elevation, and therefore fails when trying to access the Program Files directory. Your last remark sounds though as if this should work. Please help me understand what I'm doing wrong. // Sascha On Fri, Jan 24, 2014 at 11:14 AM, Rob Mensching r...@robmensching.com wrote: If you package is per-user then Burn handles that correctly. It will elevate only if necessary (i.e installing per-machine prerequisites) and install your per-user package. Burn is *designed* to handle that correctly. -Original Message- From: Sascha [mailto:sascha.ser...@gmail.com] Sent: Friday, January 24, 2014 10:51 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper I just ran into this exact same issue and have been trying to find a suitable solution. I need to install the .NET Framework and also a newer C++ runtime as per-machine
Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper
Peruser can't install to C:\Program Files\. That's a per machine location. -Original Message- From: Sascha Sertel [mailto:sascha.ser...@gmail.com] Sent: January-24-14 4:18 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper Let me clarify a bit to tell you what I'm trying to do, what I've tried, and what I thought isn't currently working: Goal: Build a WiX installer for my software which installs .NET Framework 4.5.1 if needed, C++ Runtime if needed, and my software. My software needs to be installed per-user, i.e. it should go into AppData\Local, not Program Files. My understanding is - To accomplish my goal I need three components: .NET Framework 4.5.1 package (provided by NetFx extension), C++ Runtime merge module, and MSI for my software - The two prerequisites needs to be installed on a per-machine (elevated) level, my software on a per-user level This is what I've tried: Attempt 1. Created a WiX bundle with two packages inside the Chain element: A PackageGroupRef for NetFx451Web, and an MsiPackage that includes my software as well as the C++ merge module. Problem: This wouldn't build because my software Package had InstallScope perUser but apparently the C++ merge module forced ALLUSERS=1 which conflicted with the perUser setting. This problem went away when I took the merge module out of the package. Attempt 2: Created a WiX bundle with three packages inside the Chain element: A PackageGroupRef for NetFx451Web, an MsiPackage for my C++ Runtime merge module (InstallScope perMachine), and an MsiPackage for my software (InstallScope perUser). Problem: When running the resulting bundle it would prompt for elevation (which is fine), then install .NET Framework fine, then install the merge module fine, but throw an error for my perUser package: The installer has insufficient privileges to access this directory: C:\Program Files\product. The installation cannot continue. Log on as administrator or contact your system administrator. My software package uses a folder underneath ProgramFilesFolder as the target folder and I was expecting that on Win7 and up in a per-user install it automatically translates to LocalAppDataFolder instead. I thought from what I had gathered in this thread is that once the bundle gets elevated permissions it will also try to run my software package in forced per machine mode but without elevation, and therefore fails when trying to access the Program Files directory. Your last remark sounds though as if this should work. Please help me understand what I'm doing wrong. // Sascha On Fri, Jan 24, 2014 at 11:14 AM, Rob Mensching r...@robmensching.comwrote: If you package is per-user then Burn handles that correctly. It will elevate only if necessary (i.e installing per-machine prerequisites) and install your per-user package. Burn is *designed* to handle that correctly. -Original Message- From: Sascha [mailto:sascha.ser...@gmail.com] Sent: Friday, January 24, 2014 10:51 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper I just ran into this exact same issue and have been trying to find a suitable solution. I need to install the .NET Framework and also a newer C++ runtime as per-machine prerequisites but my software on a per-user basis. Would using the managed bootstrapper help get around this issue by any chance? My understanding is that using the managed bootstrapper means there are actually two bootstrappers, one that takes care of installing .NET Framework if needed, and then the managed one that gets launched after. If the inner managed bootstrapper is capable of doing a regular per-user install after the outer native bootstrapper installs the .NET Framework, that would solve most of this issue. I say most because I also need to install the C++ runtime, but for now I could resort to deploy the C++ DLLs locally with my app instead of using the merge module. I'm looking at some of the managed bootstrapper tutorials and blob posts right now and will slap something together to try out this theory, but if anybody already knows the answer that would be even better. I'll post another reply with my findings once I'm done. The only other alternative I see is using some other means like a simple batch file to execute multiple bundles in series, that way I would have one bundle with .NET and C++ runtime in it which would run per-machine or just the MSIs for those without a bundle, and then another bundle with my per-user software MSI. Not ideal especially for issues and error conditions, but better than asking my end-user to run a couple of MSIs manually. // Sascha -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/dual-pur
Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper
My software package uses a folder underneath ProgramFilesFolder as the target folder and I was expecting that on Win7 and up in a per-user install it automatically translates to LocalAppDataFolder instead. I think Vista maybe but I think windows 7 doesn't do that. Don't quote me. I just vaguely remember reading something about that. Maybe someone else can chime in. Wes -Original Message- From: Sascha Sertel [mailto:sascha.ser...@gmail.com] Sent: January-24-14 4:18 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper Let me clarify a bit to tell you what I'm trying to do, what I've tried, and what I thought isn't currently working: Goal: Build a WiX installer for my software which installs .NET Framework 4.5.1 if needed, C++ Runtime if needed, and my software. My software needs to be installed per-user, i.e. it should go into AppData\Local, not Program Files. My understanding is - To accomplish my goal I need three components: .NET Framework 4.5.1 package (provided by NetFx extension), C++ Runtime merge module, and MSI for my software - The two prerequisites needs to be installed on a per-machine (elevated) level, my software on a per-user level This is what I've tried: Attempt 1. Created a WiX bundle with two packages inside the Chain element: A PackageGroupRef for NetFx451Web, and an MsiPackage that includes my software as well as the C++ merge module. Problem: This wouldn't build because my software Package had InstallScope perUser but apparently the C++ merge module forced ALLUSERS=1 which conflicted with the perUser setting. This problem went away when I took the merge module out of the package. Attempt 2: Created a WiX bundle with three packages inside the Chain element: A PackageGroupRef for NetFx451Web, an MsiPackage for my C++ Runtime merge module (InstallScope perMachine), and an MsiPackage for my software (InstallScope perUser). Problem: When running the resulting bundle it would prompt for elevation (which is fine), then install .NET Framework fine, then install the merge module fine, but throw an error for my perUser package: The installer has insufficient privileges to access this directory: C:\Program Files\product. The installation cannot continue. Log on as administrator or contact your system administrator. My software package uses a folder underneath ProgramFilesFolder as the target folder and I was expecting that on Win7 and up in a per-user install it automatically translates to LocalAppDataFolder instead. I thought from what I had gathered in this thread is that once the bundle gets elevated permissions it will also try to run my software package in forced per machine mode but without elevation, and therefore fails when trying to access the Program Files directory. Your last remark sounds though as if this should work. Please help me understand what I'm doing wrong. // Sascha On Fri, Jan 24, 2014 at 11:14 AM, Rob Mensching r...@robmensching.comwrote: If you package is per-user then Burn handles that correctly. It will elevate only if necessary (i.e installing per-machine prerequisites) and install your per-user package. Burn is *designed* to handle that correctly. -Original Message- From: Sascha [mailto:sascha.ser...@gmail.com] Sent: Friday, January 24, 2014 10:51 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper I just ran into this exact same issue and have been trying to find a suitable solution. I need to install the .NET Framework and also a newer C++ runtime as per-machine prerequisites but my software on a per-user basis. Would using the managed bootstrapper help get around this issue by any chance? My understanding is that using the managed bootstrapper means there are actually two bootstrappers, one that takes care of installing .NET Framework if needed, and then the managed one that gets launched after. If the inner managed bootstrapper is capable of doing a regular per-user install after the outer native bootstrapper installs the .NET Framework, that would solve most of this issue. I say most because I also need to install the C++ runtime, but for now I could resort to deploy the C++ DLLs locally with my app instead of using the merge module. I'm looking at some of the managed bootstrapper tutorials and blob posts right now and will slap something together to try out this theory, but if anybody already knows the answer that would be even better. I'll post another reply with my findings once I'm done. The only other alternative I see is using some other means like a simple batch file to execute multiple bundles in series, that way I would have one bundle with .NET and C++ runtime in it which would run per-machine or just the MSIs for those without a bundle, and then another bundle with my per-user
Re: [WiX-users] best way to handle su8pporting files
Why can't you just compile the source code beforehand and place the binary in the installer? It's because of the integration; you are compiling both together? Usually you can compile your software into an intermediate library that the user can use and compile with their software. Any change on doing that? -Original Message- From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] Sent: January-19-14 7:16 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] best way to handle su8pporting files Importance: High Hi All, I'm in a situation where I'm doing some work for a client integrating some software we have written in to a piece of software they use. They haven't paid for the source, so leaving this behind is not an option. What I need to do is to copy the source file to the target machine, compile this file and then remove the source file leaving the compiled binary. Given that RemoveFiles comes before InstallFiles in the InstallExecute sequence what is the best way of doing this? Is there a mechanism for some form of support files in windows installer that are copied to the users machine but not actually installed? Any help appreciated. Cheers Sean. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Install exe package conditionally in bundle
There's a predefined exepackage in wix; put this in chain: PackageGroupRef Id=NetFx40ClientRedist/ This installs silently with progress in same window. Or if you want to create your own exe package use Protocol=netfx4 and I think InstallCommand to specify command line parameters like quiet mode. -Original Message- From: Goran Malovic [mailto:malov...@yahoo.com] Sent: January-17-14 12:57 AM To: General discussion about the WiX toolset. Subject: [WiX-users] Install exe package conditionally in bundle Hi, I need to install both .net framework and one exe package (update to .net framework). When bundle starts installing .net framework, following messageis displayed: Processing: Microsoft .NET Framework 4.0 After framework is installed, a new installation is started (new window), installing the update for framework. However, bundle still displays the same message. Questions: 1) is it possible to display new message, like: Processing: .Update 4.0.3 for .NET Framework 4.0 (NDP40-KB2600211-x86-x64) 2) is it possible for ExePackage (NDP40-KB2600211-x86-x64.exe) to be shown on the setup window (bundle), and use bundle progress bar, just like .net framework and application? Regards, Goran -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Install exe package conditionally in bundle
Sorry I thought you were talking about 4.0. Did not read carefully. -Original Message- From: Goran Malovic [mailto:malov...@yahoo.com] Sent: January-17-14 10:49 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Install exe package conditionally in bundle Thanks. It seems that we can treat 4.0.3 update in similar manner as netfx4. First tests show that it is working as expected. On Friday, January 17, 2014 1:56 PM, Wesley Manning wmann...@dynagen.ca wrote: There's a predefined exepackage in wix; put this in chain: PackageGroupRef Id=NetFx40ClientRedist/ This installs silently with progress in same window. Or if you want to create your own exe package use Protocol=netfx4 and I think InstallCommand to specify command line parameters like quiet mode. -Original Message- From: Goran Malovic [mailto:malov...@yahoo.com] Sent: January-17-14 12:57 AM To: General discussion about the WiX toolset. Subject: [WiX-users] Install exe package conditionally in bundle Hi, I need to install both .net framework and one exe package (update to .net framework). When bundle starts installing .net framework, following messageis displayed: Processing: Microsoft .NET Framework 4.0 After framework is installed, a new installation is started (new window), installing the update for framework. However, bundle still displays the same message. Questions: 1) is it possible to display new message, like: Processing: .Update 4.0.3 for .NET Framework 4.0 (NDP40-KB2600211-x86-x64) 2) is it possible for ExePackage (NDP40-KB2600211-x86-x64.exe) to be shown on the setup window (bundle), and use bundle progress bar, just like .net framework and application? Regards, Goran -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Install exe package conditionally in bundle
What OSs do you support? If Vista and above maybe you can install .net 4.5 or 4.5.1. Although more computers would have .net 4.0 and above than 4.5 and I think you need to have SP2 on Vista (SP1 for .net 4.0) and SP1 on Windows 7. Or if you need to support XP also you could just install the 4.0.3 on XP and then 4.5 on Vista and above. Wes -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: January-17-14 10:55 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Install exe package conditionally in bundle Sorry I thought you were talking about 4.0. Did not read carefully. -Original Message- From: Goran Malovic [mailto:malov...@yahoo.com] Sent: January-17-14 10:49 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Install exe package conditionally in bundle Thanks. It seems that we can treat 4.0.3 update in similar manner as netfx4. First tests show that it is working as expected. On Friday, January 17, 2014 1:56 PM, Wesley Manning wmann...@dynagen.ca wrote: There's a predefined exepackage in wix; put this in chain: PackageGroupRef Id=NetFx40ClientRedist/ This installs silently with progress in same window. Or if you want to create your own exe package use Protocol=netfx4 and I think InstallCommand to specify command line parameters like quiet mode. -Original Message- From: Goran Malovic [mailto:malov...@yahoo.com] Sent: January-17-14 12:57 AM To: General discussion about the WiX toolset. Subject: [WiX-users] Install exe package conditionally in bundle Hi, I need to install both .net framework and one exe package (update to .net framework). When bundle starts installing .net framework, following messageis displayed: Processing: Microsoft .NET Framework 4.0 After framework is installed, a new installation is started (new window), installing the update for framework. However, bundle still displays the same message. Questions: 1) is it possible to display new message, like: Processing: .Update 4.0.3 for .NET Framework 4.0 (NDP40-KB2600211-x86-x64) 2) is it possible for ExePackage (NDP40-KB2600211-x86-x64.exe) to be shown on the setup window (bundle), and use bundle progress bar, just like .net framework and application? Regards, Goran -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https
Re: [WiX-users] Multiple entries in ARP, while upgrading an installation.
I got it from the mailing list and wix book. It would be on the MSI MSDN somewhere but I don't know where. From: Shehnaz Khan [mailto:shehnaz_k...@persistent.co.in] Sent: January-16-14 4:26 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Multiple entries in ARP, while upgrading an installation. Is there any documentation which would explain this behavior? It would be of great help. Thanks, Shehnaz -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: Wednesday, January 15, 2014 6:18 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Multiple entries in ARP, while upgrading an installation. It's a MSI package? MSI doesn't look at fourth position in version. So it only see's 4.0.0 when upgrading. -Original Message- From: Shehnaz Khan [mailto:shehnaz_k...@persistent.co.in] Sent: January-15-14 6:57 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Multiple entries in ARP, while upgrading an installation. Hi, I created the installer for my application using Wix. The version of that application was like 4.0.1.0. I need to upgrade that app to another version say 4.0.1.1. I created another installer for it keeping Upgrade code same as before, different product and package codes. After completing installation i am seeing both the versions entries in ARP. Please tell where i am going wrong? Regards, Shehnaz Khan 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. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users 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. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Multiple entries in ARP, while upgrading an installation.
It's a MSI package? MSI doesn't look at fourth position in version. So it only see's 4.0.0 when upgrading. -Original Message- From: Shehnaz Khan [mailto:shehnaz_k...@persistent.co.in] Sent: January-15-14 6:57 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Multiple entries in ARP, while upgrading an installation. Hi, I created the installer for my application using Wix. The version of that application was like 4.0.1.0. I need to upgrade that app to another version say 4.0.1.1. I created another installer for it keeping Upgrade code same as before, different product and package codes. After completing installation i am seeing both the versions entries in ARP. Please tell where i am going wrong? Regards, Shehnaz Khan 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. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn not uninstalling MSI downloaded from URL
So you mean set SuppressSignatureVerification=yes in the MSIPackage, ExePackage,... ? Looks like I'm going to have to make a change although I don't do this and had no problem so far. . Wes -Original Message- From: Blair Murri [mailto:os...@live.com] Sent: January-08-14 7:10 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Burn not uninstalling MSI downloaded from URL This speaks to the best practice of always setting up your bundles so that they use the package hashes instead of signatures to validate that the correct package was retrieved. From: dan.mad...@quanser.com To: wix-users@lists.sourceforge.net Date: Tue, 7 Jan 2014 12:22:13 -0500 Subject: Re: [WiX-users] Burn not uninstalling MSI downloaded from URL Hi Rob, I recognize that System Restore isn't a magic bullet, but it has been working fairly well for me in this case. It turns out that the package cache was not in a dirty state. Instead, I found out the wrong MSI was put online. The file sizes were the same as was the Summary Information in Orca and UpgradeCode so it wasn't immediately evident. The bootstrapper would download the online version and then fail to register it because it was trying to register the ProductCode GUID used when it was built while the downloaded MSI had a different ProductCode. Hence, the registration failed because it could not find the ProductCode in the list of installed products. However, it continued with the install anyways without any warning given to the user. The net effect of this failed registration did not turn up until I attempted to uninstall, in which case it decided (I think) that the product was not installed (since it was using the wrong GUID) so no action was required other than removing the cached MSI and bootstrapper. So the uninstall also succeeded even though the product was actually left installed. Again, no feedback to the user indicating failure and the ARP entry was removed, while the files were left on the system. Moral of the story: always make sure the online MSI and local MSI used as the SourceFile for the MsiPackage are absolutely identical. Obvious, but mistakes are quite costly, potentially leaving users with no way to uninstall the product from their machine without technical support. Thanks for your help. Dan -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Monday, January 06, 2014 4:39 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Burn not uninstalling MSI downloaded from URL System Restore isn't a system reset. I've never seen it work terribly well. If you want system reset, use a VM and snapshots. The messages you are seeing are pretty suspect. They suggest the package cache is constantly in a dirty state which shouldn't be happening with normal install/uninstall. Anyway, the bundle log file should show why a package is not being uninstalled. -Original Message- From: Daniel Madill [mailto:dan.mad...@quanser.com] Sent: Monday, January 6, 2014 1:27 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Burn not uninstalling MSI downloaded from URL Hi, I don't think so. I don't have the packages as part of any other bundle. Also, I can always install and uninstall fine if I put the MSIs on the local filesystem, but never when it has to download the MSI from the URL. I've also been using System Restore to put my system back in its original state. I searched for the package code of the MSI in the registry after uninstall but could not find it. However, just in case I did not look properly, where should I expect to find the reference counts for the packages in the registry and should I be looking for the package code from the summary information of the MSI, the upgrade code or the component GUIDS (of which there are probably 13000 so I hope not). If I have the MSIs on the local filesystem then I do not get the Unable to register source directory warning in the install log, nor do I get the Detected partially cached package in the uninstall log. It is only when it has to download the MSI from the URL that I get these warnings in the logs. I added Cache='yes' and 'CacheId' values but that didn't help. Is the fact I use a relative path as part of the Name attribute a problem for downloaded packages? It does appear to download and cache the MSI in the C:\ProgramData\Package Cache folder after downloading it so I'm surprised by the Detected partially cached package warning in the uninstall log. Is there anything else I can do to better debug the problem? Thanks. Dan -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Monday, January 06, 2014 3:36 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Burn not uninstalling MSI downloaded from URL First guess: maybe
Re: [WiX-users] Uninstall by Installer not removing the path created if that path is open on the system
Did you use CreateFolder to create this directory? If so I think you need to use RemoveFolder to remove the folder. Not sure about that though. -Original Message- From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in] Sent: December-16-13 12:37 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Uninstall by Installer not removing the path created if that path is open on the system Hey Wesley, checked it on a reboot, that does not work. The structure is still there. Any others suggestions guys? Regards, SuvraJyoti On 13-12-2013 20:13, Wesley Manning wrote: It might be removed on a reboot. If you had folder open, then windows installer can't uninstall it. But I think it marks it for removal. I know for sure files have this behaviour but I'm not sure about folders. -Original Message- From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in] Sent: December-13-13 1:48 AM To: General discussion about the WiX toolset. Subject: [WiX-users] Uninstall by Installer not removing the path created if that path is open on the system Hi All, I just saw this behaviour. My installer creates the following :C:\Energy Solutions International\PFWService\config, if this path is open and i run the uninstall from control panel, then the path remains(C:\Energy Solutions International\PFWService\config) although files under it is removed. Is it expected behavior or incorrect. If incorrect what is the workaround for the same. Regards, SuvraJyoti -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Where is wixstdba.dll ?!!
It's under src/ext/BalExtension/wixstba. You don't need to change the dll. There's a theme file (theme.xml) and a corresponding culture file (has a .wxl extension). You can change the .wxl file to Chinese. Although if you look under Resources/1028 under the wixstba folder you see the Chinese wxl file. The only problem is if there is an error wixstba returns a link to the burn log files. That log file would still be in English AFAIK. Here is how you tie it into your bundle: BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.HyperlinkLicense bal:WixStandardBootstrapperApplication LicenseUrl=http://www.dynagen.ca; SuppressOptionsUI=yes ThemeFile=Theme\DynagenTheme.xml LocalizationFile=Theme\DynagenTheme.wxl / Wes -Original Message- From: 郭龙仓 [mailto:guolongcang.w...@gmail.com] Sent: December-12-13 11:19 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Where is wixstdba.dll ?!! I have installed WiX Toolset 3.8 on my windows ,But I cannot find wixstdba.dll 。 Because the bootstrapperApplication only have English Resource Now , I wanna find wixstdba.dll and change the english string to chinese . Thank you !!! -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to build wix toolset from source ?
If you are going to dive into the source code there is another wix mailing list, Wix-devs, you might want to sign up for. You are lucky thought as someone just recently asked a similar question on wix-devs. Here was one response: 1) Read this: http://wixtoolset.org/documentation/manual/v3/wixdev/wixdev_getting_started.html 2) Ask on this list for the assignment agreement, Rob will respond and then send you mail separately to get the ball rolling. 3) .Net Framework 3.5, recent versions of Visual Studio (2010 or newer), build and install the DevBundle branch (you can remove the DevBundle installer if you wish, all the components it installs are marked permanent). If you install multiple versions of VS, it is recommended to install them in chronological order (personal experience) with their latest service packs. 4) Build instructions are (more-or-less) described here (the prerequisites described are most easily obtained by following my previous two instructions): http://wixtoolset.org/documentation/manual/v3/wixdev/building_wix.html The biggest missing piece from the above documentation pages is that tools\OneTimeWixBuildInitialization.proj must be built using MSBuild from an elevated command prompt at least once on any given build/dev box before you can build the rest of the toolset (otherwise you will get build errors starting early on). Also, it is best to build the entire toolset from the root of the sources (after having built that one project file elevated) before you descend into sub directories to work/build individual portions. Running the developer command prompts for Visual Studio usually isn't necessary, although MSBuild isn't usually in the path. You'll need the v4 MSBuild, which you can add your path yourself, use the developer command prompt, prepend the MSBuild calls with the path to the tool, or create your own alias/batch file to call the tool. 5) Welcome to the group! We are glad to have you join us. -Blair Date: Sun, 1 Dec 2013 09:54:31 -0500 From: yellowjacketl...@gmail.com To: wix-d...@lists.sourceforge.net Subject: [WiX-devs] Requesting information to add feature to WiX code base... I'd like to add a feature to WiX's codebase (add LogEventOnRecycle bitmask to an AppPool). Please let me know what I need to do to proceed (send me the Outercurve agreement to sign, dev tools required, etc.). -- Tony -Original Message- From: 郭龙仓 [mailto:guolongcang.w...@gmail.com] Sent: December-12-13 11:37 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] How to build wix toolset from source ? I need to do some change of the wix source code , But do not know exactly how to rebuild it . -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall by Installer not removing the path created if that path is open on the system
It might be removed on a reboot. If you had folder open, then windows installer can't uninstall it. But I think it marks it for removal. I know for sure files have this behaviour but I'm not sure about folders. -Original Message- From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in] Sent: December-13-13 1:48 AM To: General discussion about the WiX toolset. Subject: [WiX-users] Uninstall by Installer not removing the path created if that path is open on the system Hi All, I just saw this behaviour. My installer creates the following :C:\Energy Solutions International\PFWService\config, if this path is open and i run the uninstall from control panel, then the path remains(C:\Energy Solutions International\PFWService\config) although files under it is removed. Is it expected behavior or incorrect. If incorrect what is the workaround for the same. Regards, SuvraJyoti -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to avoid bundle registration as installed
Burn isn't a bootstrapper really. Why do you want to use burn and not a bootstrapper like dotNetInstaller? -Original Message- From: Hamlet [mailto:hakobyan...@yahoo.com] Sent: November-25-13 5:36 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How to avoid bundle registration as installed Thank you for replay, but it is not my option. I have dual-purpose package which works fine. Now I want to install prerequisites if necessary. What I want that the burn must install prerequisites if necessary, then run the msi dual-purpose package. No need to cache or register the bundle and so. Just install prerequisites and starts msi package. Msi will control the behavior when it must installs or uninstalls. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-avoid-bundle-registration-as-installed-tp7590928p7590946.html Sent from the wix-users mailing list archive at Nabble.com. -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Why do i need to add RelatedBundle in the 'main' bundle?
Also I don’t understand why the 'main' bundle should have Related Bundle element?: Main bundle needs a related bundle element set to detect with the GUID attribute in that element set to the same GUID of the related bundle element GUID attribute in all the patch or addon related bundles. Detect tells the main bundle to look for related bundles with this GUID and perform the appropriate action on them (as specified by the related bundles action attribute). You could use the main bundle upgrade code for the related bundle GUID in the patch or add-on bundles but I found a bug where this causes problems. Wes -Original Message- From: tom [mailto:tomer.d...@intergraph.com] Sent: November-17-13 12:43 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Why do i need to add RelatedBundle in the 'main' bundle? Hi I am trying to support 'sequencing' of a bundle such that the user will not be able to install HF1 on top of HF2 When I use same UpgradeCode for all the bundles and remove 'main' bundle it does not remove other bundles When I use different UpgdraeCode then when installing HF1 on top of HF2 I don’t get the expected OnDetectRelatedBundle event (I need 2 one for HF2 and the second for the 'main') Also I don’t understand why the 'main' bundle should have Related Bundle element? (Mentioned by Rob) Thanks in advance -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Why-do-i-need-to-add-RelatedBundle-in-the-main-bundle-tp7590702.html Sent from the wix-users mailing list archive at Nabble.com. -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Why do i need to add RelatedBundle in the 'main' bundle?
No the other way around. Detect goes into main bundle. Patch goes in patch
bundle.
By upgrade code what are you referring to? The upgrade code of the main bundle?
-Original Message-
From: tom [mailto:tomer.d...@intergraph.com]
Sent: November-18-13 1:33 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Why do i need to add RelatedBundle in the 'main'
bundle?
So in the main bundle i need to add
RelatedBundle Id={0E206C2C-82FC-420D-AFA6-FA347F3FDA14} Action=Patch/
Where ={0E206C2C-82FC-420D-AFA6-FA347F3FDA14} is the upgrade code
And in patch I need to add
RelatedBundle Id={0E206C2C-82FC-420D-AFA6-FA347F3FDA14}
Action=Detect/
In order to make sure correct sequence?
(I will catch the OnRelatedBundle event...)
Thanks in advance
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Why-do-i-need-to-add-RelatedBundle-in-the-main-bundle-tp7590702p7590733.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Shape the Mobile Experience: Free Subscription Software experts and developers:
Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations that shape the rapidly evolving mobile landscape. Sign up now.
http://pubads.g.doubleclick.net/gampad/clk?id=63431311iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations that shape the rapidly evolving mobile landscape. Sign up now.
http://pubads.g.doubleclick.net/gampad/clk?id=63431311iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Why do i need to add RelatedBundle in the 'main' bundle?
I never used the patch feature, only the add-on feature. So can't help you on patch behaviour. I also only use the standard BA. FYI: IIRC, you don't need a detect element in the main bundle if you use the main bundle upgrade code. You don't need to use the upgrade code. It can be any unique GUID. In this case you need the Detect element in the main bundle (so it knows to look for related bundles of that GUID). I would recommend this approach. Rob here (one of developers) also recommends this approach so you can easily tell your major upgrade apart from your related bundles in your custom BA. Reason I recommend this is when I started out using related bundles I used the upgrade code at first but during testing I found a bug where during a major upgrade of the main bundle the add-on bundles would sometimes not uninstall when they were supposed to or would be uninstalled when they should have remained. See bug 3865. Wes -Original Message- From: tom [mailto:tomer.d...@intergraph.com] Sent: November-18-13 1:50 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Why do i need to add RelatedBundle in the 'main' bundle? Yes, the upgrade code of the main bundle -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Why-do-i-need-to-add-RelatedBundle-in-the-main-bundle-tp7590702p7590735.html Sent from the wix-users mailing list archive at Nabble.com. -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] LGHT0306 Error - less than 30K files
http://wixtoolset.org/issues/ -Original Message- From: fiddler mikey [mailto:fiddlermi...@gmail.com] Sent: November-14-13 7:00 PM To: wix-users Subject: Re: [WiX-users] LGHT0306 Error - less than 30K files Unfortunately it wasn't that easy. Because the whole process is automated and the files and media entries are created at the same time, I couldn't just remove the media entry without light complaining about missing media references. I did resolve my issue and found that the error was entirely related to cab size and not because of the number of files, as originally suggested by the error message. I created some scripts to filter and copy the files from their source to the destination media location and then determined that 1 single cab contained around 3gb of data, most of them binary, which would definitely not compress to 2gb. Therefore the error was misleading and your suggestion was very helpful. The app I developed to create the wxs file has been updated to separate the files into more cabs and that's okay for this stage of development. Thanks for the helpful suggestions. I hope this post helps someone else. Where do I file a bug or feature request on this issue? mikey Date: Thu, 31 Oct 2013 17:02:09 -0500 From: ecyo...@grandecom.net Subject: Re: [WiX-users] LGHT0306 Error - less than 30K files To: wix-users@lists.sourceforge.net Message-ID: 20131031170209.14443tqlj1u1y...@webmail.mygrande.net Content-Type: text/plain; charset=ISO-8859-1; DelSp=Yes; format=flowed Put in Each Cab you took out then comment out all the Cabss in the media list, one at at a time. If the first one suceeds, add the second until you get down to the nth one where 1 n 31. The one you uncomment last will be the one that can't be built, assuming you start at the top. That means the offending cab will have something in it that WiX doesn't like etc. This method will also rule out the Cab Files that work. Quoting fiddler mikey fiddlermi...@gmail.com: Thanks for the response. There is no AV software on that machine and it is very unlikely that any single cab would be over 2gb, but impossible to say without trying to manually create each of the 31 cabs. I have removed references to a couple of the largest files in what could be the largest cabs (~1.5gb expected) and still receive the same error. I was under the impression that there is a different error message when trying to build a cab file over 2gb. Any other suggestions? Date: Thu, 31 Oct 2013 18:14:19 + From: Hoover, Jacob jacob.hoo...@greenheck.com Subject: Re: [WiX-users] LGHT0306 Error - less than 30K files To: General discussion about the WiX toolset. wix-users@lists.sourceforge.net Message-ID: 61d0a1ed0452f744bd7fe991abc2196f906bc...@exbox2.greenops.com Content-Type: text/plain; charset=us-ascii I'm currently building a MSI with over 30k files in it (25 CABS) without issue, though I've been using 3.7/3.8. By chance do you have any AV software running on your build machine? What is the overall size of the files being put into the CAB's (would any single CAB be over 2GB)? -Original Message- From: fiddler mikey [mailto:fiddlermi...@gmail.com] Sent: Wednesday, October 30, 2013 7:01 PM To: wix-users Subject: [WiX-users] LGHT0306 Error - less than 30K files I believe I am getting an erroneous failure message when building a rather large Wix project. The project contains a total of 27,654 files in it, divided among 31 different cabs. However, after candle/light on the project, I get a failure after about 6 minutes and no output files are built. (No .cab, msi, etc) The error is: An error (E_FAIL) was returned while finalizing a CAB file. This most commonly happens when creating a CAB file with more than 65535 files in it. Either reduce the number of files in your installation package or split your installation package's files into more than one CAB file using the Media element. I have tried WiX toolset 3.5 and 3.6, from VS2010 and command line builds, with the same error message. Has anyone else run into this error before? Any tips for troubleshooting? Is this a bug? Is there a workaround? Thanks, mikey http://bit.ly/fiddlermikey On Thu, Oct 31, 2013 at 12:29 PM, fiddler mikey fiddlermi...@gmail.comwrote: Thanks for the response. There is no AV software on that machine and it is very unlikely that any single cab would be over 2gb, but impossible to say without trying to manually create each of the 31 cabs. I have removed references to a couple of the largest files in what could be the largest cabs (~1.5gb expected) and still receive the same error. I was under the impression that there is a different error message when trying to build a cab file over 2gb. Any other suggestions? Date: Thu, 31 Oct 2013 18:14:19 + From: Hoover, Jacob jacob.hoo...@greenheck.com Subject: Re: [WiX-users]
Re: [WiX-users] Burn bundle - mix of per-user and per-machine MSIs
Will have to do a test... -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: October-31-13 12:42 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Burn bundle - mix of per-user and per-machine MSIs I honestly don't remember... -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: Wednesday, October 30, 2013 12:22 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Burn bundle - mix of per-user and per-machine MSIs Thanks. That makes sense. I'm installing drivers so need to have both. Can a per-user bundle upgrade or uninstall a per-machine bundle via relatedbundle element's attribute Action set to Upgrade? I have a per-machine bundle now. Thinking of switching my app to per-user. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: October-30-13 4:12 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Burn bundle - mix of per-user and per-machine MSIs Yes. Note: the presence of a per-user package makes the bundle per-user. -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: Wednesday, October 30, 2013 12:10 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Burn bundle - mix of per-user and per-machine MSIs Hi, Can burn handle a mix of per-machine and per-user MSI packages? I thought I read somewhere it can't but can't find it. Wes -Original Message- From: Phil Wilson [mailto:phildgwil...@gmail.com] Sent: August-23-13 3:43 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Fallback when not getting admin rights I forget what the DropBox install experience was, but when I look at those shell extensions they are all in HKCU, so they are per-user and not per-system. That might work for you too. Phil Wilson On Fri, Aug 23, 2013 at 1:59 AM, Trond Andersen trond.ander...@gmail.comwrote: I have an application which uses Shell extensions to add a menu in Windows Explorer, however I would like the installer to have a fallback if the user is not able to give the installer admin rights in which the user can access the functionality without using menus/toolbar in Windows Explorer. The Dropbox installer does the same thing. Does anyone have an example or other resources which could help me getting this working. For information - I'm using WIX 3.7 and Burn bootstrapper. Is this something the bootstrapper should handle? Will the Burn bootstrapper be able to do this or do I have to use a different bootstrapper/modify Burn? -- Trond -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android is increasing
Re: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens second burn's window.
Is it your own customer action?
If it is, If your driver is inf based you can use
DifxAppExtension: xmlns:difx=http://schemas.microsoft.com/wix/DifxAppExtension;
Then add the Driver element in same component as your inf file.
Component Id=CMP_DfuDriver2 Guid={...}
difx:Driver AddRemovePrograms=yes DeleteFiles=no
PlugAndPlayPrompt=no ForceInstall=no Legacy=no/
File Id=... Source=... Vital=yes KeyPath=yes/
/Component
You would need 32bit and 64bit MSIs if supporting both 32 and 64bit.
If MSI is a Major upgrade (e.g. MajorUpgrade element) make sure to schedule
after afterInstallValidate. There was discussion on this mailing list about
(rare?) problems otherwise.
Wes
-Original Message-
From: Tobias Erichsen [mailto:i...@tobias-erichsen.de]
Sent: October-14-13 1:03 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn installation with Aladdin eToken driver (msi)
opens second burn's window.
Hi everyone,
I do have the same problem with my burn-package which first installs an MSI
with a driver (using custom-action DLL) and then the application MSI.
This only happens on Windows XP, not on Windows 7 or 8.
If I replace the driver-install CA in the first MSI by a special diagnosis
Sleep-CA which takes about the same time, this does not happen
It seems like the burn-bootstrapper restarts itself due to something happening
during the driver-installation...
I could provide logs, source-code for the msi-packages for the burn-package...
Best regards,
Tobias
Von: Alexey Larsky-RUS [alexey.lar...@jeppesen.com]
Gesendet: Sonntag, 13. Oktober 2013 08:26
Bis: wix-users@lists.sourceforge.net
Betreff: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens
second burn's window.
Dear Colleagues,
During setup burn based installer with Aladdin's eToken Pro drivers 3.66(RTE
3.66.msi) or 5.1 (PKIClient-x32-5.1.msi) opens second installer window.
OS: Windows XP SP3 х32
Burn: release 3.7, 3.8.1007.0
MSI:
http://www.isecurity.info/downloads/PKI_RTE_5.1_SP1_For_XP_Vista_Win_7_32_Bit.zip
or http://www.isecurity.info/downloads/rte.msi (3.65)
Phisical eToken dongle is not need for bug reproduction.
Test sample, screenshoots and logs are attached.
Yours sincerely.
--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60134071iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens second burn's window.
Sorry I just read it's not your drivers. Does it come with the inf drivers?
-Original Message-
From: Wesley Manning
Sent: October-31-13 10:22 AM
To: General discussion for Windows Installer XML toolset.
Subject: RE: [WiX-users] Burn installation with Aladdin eToken driver (msi)
opens second burn's window.
Is it your own customer action?
If it is, If your driver is inf based you can use
DifxAppExtension: xmlns:difx=http://schemas.microsoft.com/wix/DifxAppExtension;
Then add the Driver element in same component as your inf file.
Component Id=CMP_DfuDriver2 Guid={...}
difx:Driver AddRemovePrograms=yes DeleteFiles=no
PlugAndPlayPrompt=no ForceInstall=no Legacy=no/
File Id=... Source=... Vital=yes KeyPath=yes/
/Component
You would need 32bit and 64bit MSIs if supporting both 32 and 64bit.
If MSI is a Major upgrade (e.g. MajorUpgrade element) make sure to schedule
after afterInstallValidate. There was discussion on this mailing list about
(rare?) problems otherwise.
Wes
-Original Message-
From: Tobias Erichsen [mailto:i...@tobias-erichsen.de]
Sent: October-14-13 1:03 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn installation with Aladdin eToken driver (msi)
opens second burn's window.
Hi everyone,
I do have the same problem with my burn-package which first installs an MSI
with a driver (using custom-action DLL) and then the application MSI.
This only happens on Windows XP, not on Windows 7 or 8.
If I replace the driver-install CA in the first MSI by a special diagnosis
Sleep-CA which takes about the same time, this does not happen
It seems like the burn-bootstrapper restarts itself due to something happening
during the driver-installation...
I could provide logs, source-code for the msi-packages for the burn-package...
Best regards,
Tobias
Von: Alexey Larsky-RUS [alexey.lar...@jeppesen.com]
Gesendet: Sonntag, 13. Oktober 2013 08:26
Bis: wix-users@lists.sourceforge.net
Betreff: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens
second burn's window.
Dear Colleagues,
During setup burn based installer with Aladdin's eToken Pro drivers 3.66(RTE
3.66.msi) or 5.1 (PKIClient-x32-5.1.msi) opens second installer window.
OS: Windows XP SP3 х32
Burn: release 3.7, 3.8.1007.0
MSI:
http://www.isecurity.info/downloads/PKI_RTE_5.1_SP1_For_XP_Vista_Win_7_32_Bit.zip
or http://www.isecurity.info/downloads/rte.msi (3.65)
Phisical eToken dongle is not need for bug reproduction.
Test sample, screenshoots and logs are attached.
Yours sincerely.
--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60134071iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn Question
The patch attribute goes in the patch bundle with a unique guid. Then add a detect attribute to main bundle with detect. I never did a patch bundle but I do use addon bundles and that's what you do. Wes -Original Message- From: Christopher Painter [mailto:chr...@iswix.com] Sent: October-31-13 9:49 AM To: General discussion about the WiX toolset.; General discussion about the WiX toolset.; General discussion about the WiX toolset. Subject: Re: [WiX-users] Burn Question I've also found the RelatedBundle element with the Patch action attribute but it's not clear to me how to make the relationship. (I'm still getting two entries in ARP.) Also, am I correct in predicting that when implemented correctly that the removal of a patch will not only uninstall the v2 of B.MSI but will also instruct the parent bundle to reinstall the original v1 of B.MSI and in effect being a removable patch? If so, that's really impressive. From: Christopher Painter chr...@iswix.com Sent: Thursday, October 31, 2013 7:34 AM To: General discussion about the WiX toolset. wix-users@lists.sourceforge.net, General discussion about the WiX toolset. wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Burn Question Rob, Regarding #2, what makes a bundle a patch bundle? Is this something to do with the UpgradeCode, Tag and/or ParentName attributes on the Bundle element? I don't usually ask for samples but if someone could kick me into the right direction, I would greatly appreciate it. I'll be working on it myself but I think I'm stumbling in the dark at this point. Thanks, Chris From: Rob Mensching r...@robmensching.com Sent: Wednesday, October 30, 2013 1:14 PM To: General discussion about the WiX toolset. wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Burn Question Yes. Two options one does as you describe, the other maybe less so (but might work better): 1. Bundle v1.1 is an upgrade of v1.0. Bundle v1.1 will need to know about the other 19 packages but you don't have to ship them. Burn will skip all the stuff that is already present on the machine. However, you'll want to consider the case that if something goes wrong and one of the original packages goes missing, Bundle v1.1 will need some way to find it (or tell Burn to ignore it, but not sure what that means for your app). 2. Bundle v1.1 is a patch bundle that registers in Installed Updates. It won't show up in main ARP, it'll show up in the other ARP for updates. Here Bundle v1.1 only has to take care of that which it owns and all operations (repair/uninstall) on Bundle v1.0 will also be applied to Bundle v1.1. -Original Message- From: Christopher Painter [mailto:chr...@iswix.com] Sent: Wednesday, October 30, 2013 6:51 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Burn Question I would like to know if Burn could handle the following scenario. Consider the old pre-burn WiX single MSI distribution. Now consider the way it is today with small micropackges for wix, votive, sdk and son on. Now imagine the sum of those packages 1GB are call it the Big product. Let's say I chunked Big into a couple dozen micropackages. Could Burn support a story: Release 1.0: ( Full Download - Not Web Download ) 1GB Chain together 24 packages and present a single entry in Add/Remove Programs for uninstall Release 1.1 ( Full Download - Not Web Download ) 50MB Complain if 1.0 is not installed Chain 5 packages and perform a major upgrade on each of them Present a single entry in Add/Remove Programs for uninstall that removes all 24 packages ( 19 from 1.0 and 5 from 1.0 ) If burn can't do this, I'd love to hear alternative design suggestions. One approach would be that 1.1 is a web download installer that contains all 25 packages but will only download 5 of them. I'm not sure if Big product will buy into this or not though. Thanks, Chris -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure.
Re: [WiX-users] Burn Question
I should add there is some forward planning required as you have to add a detect guid in the main bundle. Technically you can use the main bundle upgrade code as the patch guid. But I found bug where in certain cases it wouldn't work correctly (at least for addon bundles). That reminds me, I have to contribute a test case for that issue. -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: October-31-13 11:39 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Burn Question The patch attribute goes in the patch bundle with a unique guid. Then add a detect attribute to main bundle with detect. I never did a patch bundle but I do use addon bundles and that's what you do. Wes -Original Message- From: Christopher Painter [mailto:chr...@iswix.com] Sent: October-31-13 9:49 AM To: General discussion about the WiX toolset.; General discussion about the WiX toolset.; General discussion about the WiX toolset. Subject: Re: [WiX-users] Burn Question I've also found the RelatedBundle element with the Patch action attribute but it's not clear to me how to make the relationship. (I'm still getting two entries in ARP.) Also, am I correct in predicting that when implemented correctly that the removal of a patch will not only uninstall the v2 of B.MSI but will also instruct the parent bundle to reinstall the original v1 of B.MSI and in effect being a removable patch? If so, that's really impressive. From: Christopher Painter chr...@iswix.com Sent: Thursday, October 31, 2013 7:34 AM To: General discussion about the WiX toolset. wix-users@lists.sourceforge.net, General discussion about the WiX toolset. wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Burn Question Rob, Regarding #2, what makes a bundle a patch bundle? Is this something to do with the UpgradeCode, Tag and/or ParentName attributes on the Bundle element? I don't usually ask for samples but if someone could kick me into the right direction, I would greatly appreciate it. I'll be working on it myself but I think I'm stumbling in the dark at this point. Thanks, Chris From: Rob Mensching r...@robmensching.com Sent: Wednesday, October 30, 2013 1:14 PM To: General discussion about the WiX toolset. wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Burn Question Yes. Two options one does as you describe, the other maybe less so (but might work better): 1. Bundle v1.1 is an upgrade of v1.0. Bundle v1.1 will need to know about the other 19 packages but you don't have to ship them. Burn will skip all the stuff that is already present on the machine. However, you'll want to consider the case that if something goes wrong and one of the original packages goes missing, Bundle v1.1 will need some way to find it (or tell Burn to ignore it, but not sure what that means for your app). 2. Bundle v1.1 is a patch bundle that registers in Installed Updates. It won't show up in main ARP, it'll show up in the other ARP for updates. Here Bundle v1.1 only has to take care of that which it owns and all operations (repair/uninstall) on Bundle v1.0 will also be applied to Bundle v1.1. -Original Message- From: Christopher Painter [mailto:chr...@iswix.com] Sent: Wednesday, October 30, 2013 6:51 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Burn Question I would like to know if Burn could handle the following scenario. Consider the old pre-burn WiX single MSI distribution. Now consider the way it is today with small micropackges for wix, votive, sdk and son on. Now imagine the sum of those packages 1GB are call it the Big product. Let's say I chunked Big into a couple dozen micropackages. Could Burn support a story: Release 1.0: ( Full Download - Not Web Download ) 1GB Chain together 24 packages and present a single entry in Add/Remove Programs for uninstall Release 1.1 ( Full Download - Not Web Download ) 50MB Complain if 1.0 is not installed Chain 5 packages and perform a major upgrade on each of them Present a single entry in Add/Remove Programs for uninstall that removes all 24 packages ( 19 from 1.0 and 5 from 1.0 ) If burn can't do this, I'd love to hear alternative design suggestions. One approach would be that 1.1 is a web download installer that contains all 25 packages but will only download 5 of them. I'm not sure if Big product will buy into this or not though. Thanks, Chris -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu
Re: [WiX-users] Fwd: GUI for wix
On wixtoolset.org there is a link to a book on wix. I recommend that and the tutorial at wix.tramontana.co.hu. -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: October-29-13 6:36 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Fwd: GUI for wix Nope, it is all XML based, Here are a few websites that can help: http://wix.tramontana.co.hu/ http://wixtoolset.org/documentation/manual/v3/main%5Cwix_learning.html http://stackoverflow.com/questions/310418/good-resources-for-learning-how-to-create-msi-installers-from-wix these should help you out :) Steve -Original Message- From: Александр Смагин [mailto:smagin.alexan...@gmail.com] Sent: October-29-13 5:26 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Fwd: GUI for wix HI Steve, Could you provide tutorial how to use wix in VS2012? I modify already created project in VS2012 and they used wix as installation. in my version of VS, just xml is opened. there is no any interface to create/modify it more easily. I'm beginner in VS, sorry Thanks. Alex. -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn Question
Right. Any packages that are beside the bundle exe will be used automatically and not be downloaded. It's good as allows me to use same bundle as both a web installer and an offline installer just by including the packages or not. -Original Message- From: Nicolás Alvarez [mailto:nicolas.alva...@gmail.com] Sent: October-30-13 3:38 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Burn Question 2013/10/30 Christopher Painter chr...@iswix.com: One approach would be that 1.1 is a web download installer that contains all 25 packages but will only download 5 of them. I'm not sure if Big product will buy into this or not though. As far as I know, shipping packages in the bundle vs downloading them is not all-or-nothing. You can ship some packages in the bundle and download others on demand. In this case, you can ship those 5 packages in the bundle, and leave the others to be downloaded, which in most cases they won't be. -- Nicolás -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn bundle - mix of per-user and per-machine MSIs
Hi, Can burn handle a mix of per-machine and per-user MSI packages? I thought I read somewhere it can't but can't find it. Wes -Original Message- From: Phil Wilson [mailto:phildgwil...@gmail.com] Sent: August-23-13 3:43 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Fallback when not getting admin rights I forget what the DropBox install experience was, but when I look at those shell extensions they are all in HKCU, so they are per-user and not per-system. That might work for you too. Phil Wilson On Fri, Aug 23, 2013 at 1:59 AM, Trond Andersen trond.ander...@gmail.comwrote: I have an application which uses Shell extensions to add a menu in Windows Explorer, however I would like the installer to have a fallback if the user is not able to give the installer admin rights in which the user can access the functionality without using menus/toolbar in Windows Explorer. The Dropbox installer does the same thing. Does anyone have an example or other resources which could help me getting this working. For information - I'm using WIX 3.7 and Burn bootstrapper. Is this something the bootstrapper should handle? Will the Burn bootstrapper be able to do this or do I have to use a different bootstrapper/modify Burn? -- Trond -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn bundle - mix of per-user and per-machine MSIs
Thanks. That makes sense. I'm installing drivers so need to have both. Can a per-user bundle upgrade or uninstall a per-machine bundle via relatedbundle element's attribute Action set to Upgrade? I have a per-machine bundle now. Thinking of switching my app to per-user. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: October-30-13 4:12 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Burn bundle - mix of per-user and per-machine MSIs Yes. Note: the presence of a per-user package makes the bundle per-user. -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: Wednesday, October 30, 2013 12:10 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Burn bundle - mix of per-user and per-machine MSIs Hi, Can burn handle a mix of per-machine and per-user MSI packages? I thought I read somewhere it can't but can't find it. Wes -Original Message- From: Phil Wilson [mailto:phildgwil...@gmail.com] Sent: August-23-13 3:43 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Fallback when not getting admin rights I forget what the DropBox install experience was, but when I look at those shell extensions they are all in HKCU, so they are per-user and not per-system. That might work for you too. Phil Wilson On Fri, Aug 23, 2013 at 1:59 AM, Trond Andersen trond.ander...@gmail.comwrote: I have an application which uses Shell extensions to add a menu in Windows Explorer, however I would like the installer to have a fallback if the user is not able to give the installer admin rights in which the user can access the functionality without using menus/toolbar in Windows Explorer. The Dropbox installer does the same thing. Does anyone have an example or other resources which could help me getting this working. For information - I'm using WIX 3.7 and Burn bootstrapper. Is this something the bootstrapper should handle? Will the Burn bootstrapper be able to do this or do I have to use a different bootstrapper/modify Burn? -- Trond -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Setup Testing
So you are using MSI? If you are using burn you can use ExePackage element. Have burn run your MSI using MsiPackage to install service/etc and then run your exe using ExePackage. Not an expert in what you're trying to do but a thought. Wes -Original Message- From: Rob Emanuele [mailto:robert.emanu...@rackspace.com] Sent: October-24-13 3:56 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Setup Testing Hi Blair, I wish it was that simple. It isn't a GUI application, it is a service (which you can control from the command line). It has no GUI. We can write one, but hoped we could just use the easy to develop GUI in the installer using WiX to configure the service's config file. On top of that we hoped to validate the credentials supplied. This is for the Rackspace Monitoring Agent, an on-host agent, which we are looking to improve the installation and configuring process for our Windows users. My work-in-progress on revising this installer: https://github.com/racker/virgo-base/blob/b46ff4e8f004654ecd07a3f2f5742c80337aee8a/pkg/windows/virgo.wxs The service's exe can create the setup file and validate it exiting with a non-zero error code on failure. What I am asking is can a WiX created installer execute an installed exe and act on its return code. This may not be as simple as I hoped. My initial research looks like there are ways to run an exe but not interpret its return code. Other options look like I can use WcaUtil to hook into a wrapper. It doesn't look simple either way, maybe someone will either tell me I'm wrong or give me another way to look it. Thank you for your help, Rob From: Blair Murri [os...@live.com] Sent: Wednesday, October 23, 2013 8:35 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Setup Testing I'm not sure I understand what you are asking. The simple answer is: install the app, then run the app passing the supplied credentials on the command line. It seems to me that it would be easier to not involve the installer in the credentials because there isn't much difference between that and simply installing and launching and letting the application ask for the credentials. Every other possibility requires knowing more details about your application and your need/goals in having the installer gather the credentials in the first place. Blair Rob Emanuele robert.emanu...@rackspace.com wrote: Hi! We're creating an installer and would like the user to enter their account credentials into the installer. I have a dialog to do that and that part is looking good. I'd like use those credentials to run a test of our application in the installer. Can I run my application and act on the return code within the installer? Thank you, Rob -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk
Re: [WiX-users] WiX v3.8 RTM release date
http://www.joyofsetup.com/2013/10/12/wix-v3-8-acceleration/ -Original Message- From: Ronald Kanagy [mailto:ron.kan...@gmail.com] Sent: October-24-13 10:18 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] WiX v3.8 RTM release date Hello, What is the projected RTM release date for WiX v3.8? Thanks, Ron Kanagy -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Id for programdata folder
No, there is a standard Id: DirectoryRef Id=TARGETDIR Directory Id=CommonAppDataFolder Note: on windows xp this folder is located somewhere else which you probably know. -Original Message- From: Sander Obdeijn [mailto:i...@sanderobdeijn.nl] Sent: October-11-13 12:33 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Id for programdata folder Hi guys and gals I have just started using wix. And i'm impressed, at first it seemed quite daunting but i'm getting the hang of it. One thing i'm stuck on atm I have to copy a file into the c:/programdata/ folder. Is there a standard id for this folder? Or do I have to treat it as a custom folder. I'm using wix 3.7. I have seached on internet and found the same question but no answer. Thanks upfront for any help you can offer. Kind regards, Sander Obdeijn -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134071iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134071iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Exe output required without bootstrapper
Could also embed msi in a custom exe that calls the msi and closes? -Original Message- From: Phil Wilson [mailto:phildgwil...@gmail.com] Sent: October-09-13 12:45 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Exe output required without bootstrapper You wouldn't choose Windows Installer as an install engine if you want a pure exe installer. That said, it depends why exactly an exe is a requirement. You could use something like WinZip or IExpress to wrap the MSI file into an executable that would run, extract the MSI and start it, but it's still an MSI file setup and may or may not satisfy the requirement. Phil Wilson On Wed, Oct 9, 2013 at 2:55 AM, Blair Murri os...@live.com wrote: Currently in WiX 3.x only Windows Installer is supported as the underlying installation engine. There was a previous attempt to support ClickThrough but that effort was deferred to 4.x, as are any other other installation engine ideas that may be raised. There are other non-MSI systems out there, but none offer the robustness (nor, in many cases, the complexity) of Windows Installer/MSI. If you wish to have the advantages of MSI in the form of an EXE then you will need to bootstrap it. The WiX Burn bundle does offer several advantages over raw MSI, so even if you aren't requiring a bootstrapper it may still be advantageous to use it. Date: Wed, 9 Oct 2013 09:56:19 +0530 From: onlynit...@gmail.com To: wix-users@lists.sourceforge.net Subject: [WiX-users] Exe output required without bootstrapper Hi Experts, I have a requirement to keep the installer as a single exe instead of msi. Is there a way other than creating a bootstrapper to get exe. As there is no other/ additional action required from a bootstrapper. I am looking of a simple soution like selecting to generate exe instead of msi in the compile command. Any help to simplify the solution will be of great help. Thanks. -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134071iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134071iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134071iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134071iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [SPAM] Re: [SPAM] Re: Bootstrapper -- Can it be UI-less?
I thinks it's learning to use the API of C++ burn that’s the hurdle. Especially since an installer is fairly important to get right. I've been putting off creating a custom BA because of lack of docs.Eventually I will and at that time I can provide a tutorial if it's still useful. Even with a tutorial there is a lot of info and best practices that you miss. Creating installers is a small part of my job unfortunately. But I can understand why Rob encourages contributors to code/docs it wouldn't be economic to produce a book I think. Wes -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: September-18-13 4:42 PM To: afor...@cmu.edu; General discussion for Windows Installer XML toolset. Subject: [WiX-users] [SPAM] Re: [SPAM] Re: Bootstrapper -- Can it be UI-less? On my 5 year old machine it takes 5 minutes to build all of the WiX toolset source. That isn't *that* long is it? Seems like a reasonable amount of time to build a project of our size. There is documentation in the WiX.chm with instructions how to build. On Wed, Sep 18, 2013 at 12:29 PM, Alain Forget afor...@cmu.edu wrote: Is there a tutorial somewhere on where to get the stock BA's source, and how to make various changes to it? The only tutorial I found involved cracking open Visual Studio, and seemed to involve recompiling the whole source and...yeah, a big hurdle to jump. -Original Message- From: Nicolás Alvarez [mailto:nicolas.alva...@gmail.com] Sent: Wednesday, September 18, 2013 15:25 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] [SPAM] Re: Bootstrapper -- Can it be UI-less? The stock BA is open source. You don't need to start from scratch, just modify the stock one. -- Nicolás 2013/9/18 Alain Forget afor...@cmu.edu: It just seems like going from the stock BA to rolling your own custom BA just to either get rid of the UI or add a single text box, radio button, or window/step seems extremely costly in time and effort for what seems like a minor modification. -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Wednesday, September 18, 2013 12:40 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset. Subject: RE: [WiX-users] [SPAM] Re: Bootstrapper -- Can it be UI-less? I believe the mantra is don't use installer UI's, use a BA UI. As such, if you need a custom UI then generate a BA to give the look and feel that you want. The reasoning behind having a BA UI is so you can have a single unified installation experience. Having a chain of 5 MSI's all exposing their own UI's would result in a choppy and subpar user experience. That being said, WiX is open source, so anyone is free to contribute enhancements. -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: Wednesday, September 18, 2013 11:31 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] [SPAM] Re: Bootstrapper -- Can it be UI-less? There seems to be a lot of demand for more control over installer and bootstrapper UIs. Just out of curiosity, is this being worked on for future WiX releases? -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, September 18, 2013 12:27 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] [SPAM] Re: Bootstrapper -- Can it be UI-less? Yes. You'd need to create a custom BA. On Wed, Sep 18, 2013 at 2:27 AM, nkshirsagar nkshirsa...@gmail.com wrote: Hi Rob and others on the mailing list! I'm wondering the same thing. I have a minimal UI msi that I've customised slightly with logos and banners. I want this UI to run immediately instead of the first screen that the botstrapper UI shows. (licence agreement, etc). The licence agreement gets shown twice as that screen is already in my MSI UI. All I need the bootstrapper for, is to install .net 4.5 if its not already present and then kick off my msi. Is there any way to achieve this ? -- LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials
Re: [WiX-users] [SPAM] Re: Bootstrapper -- Can it be UI-less?
What do you mean by minor changes? I do that using the stdba by changing the templates. But my minor changes are adding graphics, adding installer version, changing text size, etc. -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: September-18-13 5:02 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] [SPAM] Re: Bootstrapper -- Can it be UI-less? Which I think reinforces my point. It's not clear to me why it needs to take lots of time and effort just to suppress a UI, or make minor changes to an existing UI. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, September 18, 2013 15:58 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] [SPAM] Re: Bootstrapper -- Can it be UI-less? It's not trivial to create a custom BA. It takes time and effort. On Wed, Sep 18, 2013 at 12:51 PM, Alain Forget afor...@cmu.edu wrote: I don't mean compile and setup time. I mean time and effort for someone completely unfamiliar with the WiX source and whatever may be involved in rolling a custom bootstrapper (like myself and most other people on here who ask how to do what doesn't seem like a complex request). Sure, for you and other WiX pros working on it for years, building the code and rolling your own custom BA is trivial. But for the rest of us non-WiX devs, especially those of us relatively new to it, it's far from trivial, and it seems like a lot (read: too much) to learn and figure out just a little UI change, like removing the UI, or adding a field, checkbox, label, or window/wizard step. My point is that you might want to consider making WiX-built installers' UIs easier for developers to customise without having to crack open and customise the source code (which I can only imagine can create problems when trying to keep up with updates to the main code). Alain -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, September 18, 2013 15:42 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] [SPAM] Re: Bootstrapper -- Can it be UI-less? On my 5 year old machine it takes 5 minutes to build all of the WiX toolset source. That isn't *that* long is it? Seems like a reasonable amount of time to build a project of our size. There is documentation in the WiX.chm with instructions how to build. On Wed, Sep 18, 2013 at 12:29 PM, Alain Forget afor...@cmu.edu wrote: Is there a tutorial somewhere on where to get the stock BA's source, and how to make various changes to it? The only tutorial I found involved cracking open Visual Studio, and seemed to involve recompiling the whole source and...yeah, a big hurdle to jump. -Original Message- From: Nicolás Alvarez [mailto:nicolas.alva...@gmail.com] Sent: Wednesday, September 18, 2013 15:25 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] [SPAM] Re: Bootstrapper -- Can it be UI-less? The stock BA is open source. You don't need to start from scratch, just modify the stock one. -- Nicolás 2013/9/18 Alain Forget afor...@cmu.edu: It just seems like going from the stock BA to rolling your own custom BA just to either get rid of the UI or add a single text box, radio button, or window/step seems extremely costly in time and effort for what seems like a minor modification. -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Wednesday, September 18, 2013 12:40 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset. Subject: RE: [WiX-users] [SPAM] Re: Bootstrapper -- Can it be UI-less? I believe the mantra is don't use installer UI's, use a BA UI. As such, if you need a custom UI then generate a BA to give the look and feel that you want. The reasoning behind having a BA UI is so you can have a single unified installation experience. Having a chain of 5 MSI's all exposing their own UI's would result in a choppy and subpar user experience. That being said, WiX is open source, so anyone is free to contribute enhancements. -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: Wednesday, September 18, 2013 11:31 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] [SPAM] Re: Bootstrapper -- Can it be UI-less? There seems to be a lot of demand for more control over installer and bootstrapper UIs. Just out of curiosity, is this being worked on for future WiX releases? -Original Message-
Re: [WiX-users] [SPAM] Re: Bootstrapper -- Can it be UI-less?
You can do a text field/check box using Niel's wixstba if using 3.7, it's in 3.8 I believe. A new window needs a custom BA. -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: September-18-13 5:35 PM To: Wesley Manning; 'General discussion for Windows Installer XML toolset.' Subject: RE: [WiX-users] [SPAM] Re: Bootstrapper -- Can it be UI-less? Minor changes = adding a text field, a check box, a window in the wizard steps, something like that. I never figured out how to do that without needing a custom BA, at which point, I gave up (thankfully, because apparently it's very time and effort intensive!). -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: Wednesday, September 18, 2013 16:22 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset. Subject: RE: [WiX-users] [SPAM] Re: Bootstrapper -- Can it be UI-less? What do you mean by minor changes? I do that using the stdba by changing the templates. But my minor changes are adding graphics, adding installer version, changing text size, etc. -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: September-18-13 5:02 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] [SPAM] Re: Bootstrapper -- Can it be UI-less? Which I think reinforces my point. It's not clear to me why it needs to take lots of time and effort just to suppress a UI, or make minor changes to an existing UI. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, September 18, 2013 15:58 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] [SPAM] Re: Bootstrapper -- Can it be UI-less? It's not trivial to create a custom BA. It takes time and effort. On Wed, Sep 18, 2013 at 12:51 PM, Alain Forget afor...@cmu.edu wrote: I don't mean compile and setup time. I mean time and effort for someone completely unfamiliar with the WiX source and whatever may be involved in rolling a custom bootstrapper (like myself and most other people on here who ask how to do what doesn't seem like a complex request). Sure, for you and other WiX pros working on it for years, building the code and rolling your own custom BA is trivial. But for the rest of us non-WiX devs, especially those of us relatively new to it, it's far from trivial, and it seems like a lot (read: too much) to learn and figure out just a little UI change, like removing the UI, or adding a field, checkbox, label, or window/wizard step. My point is that you might want to consider making WiX-built installers' UIs easier for developers to customise without having to crack open and customise the source code (which I can only imagine can create problems when trying to keep up with updates to the main code). Alain -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, September 18, 2013 15:42 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] [SPAM] Re: Bootstrapper -- Can it be UI-less? On my 5 year old machine it takes 5 minutes to build all of the WiX toolset source. That isn't *that* long is it? Seems like a reasonable amount of time to build a project of our size. There is documentation in the WiX.chm with instructions how to build. On Wed, Sep 18, 2013 at 12:29 PM, Alain Forget afor...@cmu.edu wrote: Is there a tutorial somewhere on where to get the stock BA's source, and how to make various changes to it? The only tutorial I found involved cracking open Visual Studio, and seemed to involve recompiling the whole source and...yeah, a big hurdle to jump. -Original Message- From: Nicolás Alvarez [mailto:nicolas.alva...@gmail.com] Sent: Wednesday, September 18, 2013 15:25 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] [SPAM] Re: Bootstrapper -- Can it be UI-less? The stock BA is open source. You don't need to start from scratch, just modify the stock one. -- Nicolás 2013/9/18 Alain Forget afor...@cmu.edu: It just seems like going from the stock BA to rolling your own custom BA just to either get rid of the UI or add a single text box, radio button, or window/step seems extremely costly in time and effort for what seems like a minor modification. -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Wednesday, September 18, 2013 12:40 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset. Subject: RE: [WiX-users] [SPAM] Re: Bootstrapper -- Can it be UI-less? I believe the mantra is don't use installer UI's, use a BA UI. As such, if you need a custom UI then generate
Re: [WiX-users] [Wix]: Create silent MSI using Wix
Technically that dialog is not part of MSI, its part of OS msiexec. -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: August-23-13 2:59 PM To: 'Bruce Cran'; 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] [Wix]: Create silent MSI using Wix When I was following the tutorial, I don't remember seeing anything. That said, maybe the installation was so brief that it didn't display. In a heavier installer, you may be right that some kind of progress bar (maybe with a cancel button) displays. Alain -Original Message- From: Bruce Cran [mailto:br...@cran.org.uk] Sent: Friday, August 23, 2013 13:51 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] [Wix]: Create silent MSI using Wix On 23/08/2013 15:20, Alain Forget wrote: Don't WiX-built MSIs have no UI by default? See the second paragraph of http://wix.tramontana.co.hu/tutorial/user-interface So just follow the steps of the Getting Started tutorial, and don't do anything in the UI section? I think there's a single noninteractive dialog that pops up that I suspect you can't avoid other than by using /quiet. -- Bruce -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Chain/MsiPackge/@bal:Overridable=yes yeilds strange error
You have to create an account and log in and then you see button to create a bug. IIRC. Wes -Original Message- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: August-02-13 3:36 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Chain/MsiPackge/@bal:Overridable=yes yeilds strange error I'm sorry, I have looked at the bug tracking page (and other tabs) and I don't see how to file the bug. I would like to understand how to do it. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chain-MsiPackge-bal-Overridable-yes-yeilds-strange-error-tp7587767p7587795.html Sent from the wix-users mailing list archive at Nabble.com. -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn Addons - reevalulate and uninstall addon bundle on main bundle install
Yes, OK, thanks. I did that and was getting confused because my test was: --- clean machine: install old addon --- install new (incompatible) main bundle I thought the addon should be removed (but it won't be since it's not related to the new bundle). So then I thought I need to use an install condition on addon. I was making things too complicated. I just have to prevent the addon(s) being installed if the correct bundle is not installed. Then I will have no problems. Wes -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: July-26-13 1:03 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn Addons - reevalulate and uninstall addon bundle on main bundle install Actually, if your addon's aren't backwards compatible any longer it sounds like you should change the addon related id. That way, when the old version of the main bundle is removed, it will take the old addons with it since the new main bundle says it isn't related to them. On Thu, Jul 25, 2013 at 8:50 PM, Wesley Manning wmann...@dynagen.ca wrote: Sorry, I didn't explain it well enough. Most of the time I want the addon bundles to act like an addons: gets uninstalled when main bundle is uninstalled, etc. But there are times when upgrading the main bundle, older addons are no longer valid. Then I want to remove them. Reason is I would like to use addons to install features that extend our main software. Then customers can pick and choose functionality. There are times when our main software changes such that older addons will no longer work so I like to remove those on an upgrade (or on a new install if user has incompatible addons installed). Any comments on this scenario? Looks like I can't get both behaviours unless I use custom BA? Maybe this is like an addon and an upgrade in one. :) Am I abusing the addon feature? Wes -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: July 25, 2013 5:46 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn Addons - reevalulate and uninstall addon bundle on main bundle install Addons (and patch) bundles follow the main bundle (more written here: https://support.firegiant.com/entries/24024208-Bundle-chain-execution- order- ). To get the behavior you want, you'd need an upgrade relationship. I think a custom BA could override the default behaviors without using an upgrade relationship but I'd try to use the upgrade relationship first. On Thu, Jul 25, 2013 at 1:32 PM, Wesley Manning wmann...@dynagen.ca wrote: I'm using wixstba and I have a addon bundle that I want to uninstall when a certain version of my main bundle is installed (and prevent install if this main bundle is present). I'm using a registry search and bal:condition in the addon to do this. Looks like the bal:condition does not do the job. It works to block install when I try to install the addon when the main bundle is already installed. But does not uninstall the addon when the main bundle it installed. Any idea on what I do to have the addon uninstall when the main bundle installs? I'm using RTM version of Wix 3.7. Wes -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg .c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists
[WiX-users] Burn Addons - reevalulate and uninstall addon bundle on main bundle install
I'm using wixstba and I have a addon bundle that I want to uninstall when a certain version of my main bundle is installed (and prevent install if this main bundle is present). I'm using a registry search and bal:condition in the addon to do this. Looks like the bal:condition does not do the job. It works to block install when I try to install the addon when the main bundle is already installed. But does not uninstall the addon when the main bundle it installed. Any idea on what I do to have the addon uninstall when the main bundle installs? I'm using RTM version of Wix 3.7. Wes -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn Addons - reevalulate and uninstall addon bundle on main bundle install
Sorry, I didn't explain it well enough. Most of the time I want the addon bundles to act like an addons: gets uninstalled when main bundle is uninstalled, etc. But there are times when upgrading the main bundle, older addons are no longer valid. Then I want to remove them. Reason is I would like to use addons to install features that extend our main software. Then customers can pick and choose functionality. There are times when our main software changes such that older addons will no longer work so I like to remove those on an upgrade (or on a new install if user has incompatible addons installed). Any comments on this scenario? Looks like I can't get both behaviours unless I use custom BA? Maybe this is like an addon and an upgrade in one. :) Am I abusing the addon feature? Wes -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: July 25, 2013 5:46 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn Addons - reevalulate and uninstall addon bundle on main bundle install Addons (and patch) bundles follow the main bundle (more written here: https://support.firegiant.com/entries/24024208-Bundle-chain-execution-order-). To get the behavior you want, you'd need an upgrade relationship. I think a custom BA could override the default behaviors without using an upgrade relationship but I'd try to use the upgrade relationship first. On Thu, Jul 25, 2013 at 1:32 PM, Wesley Manning wmann...@dynagen.ca wrote: I'm using wixstba and I have a addon bundle that I want to uninstall when a certain version of my main bundle is installed (and prevent install if this main bundle is present). I'm using a registry search and bal:condition in the addon to do this. Looks like the bal:condition does not do the job. It works to block install when I try to install the addon when the main bundle is already installed. But does not uninstall the addon when the main bundle it installed. Any idea on what I do to have the addon uninstall when the main bundle installs? I'm using RTM version of Wix 3.7. Wes -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [wix-users] Impact of installed burn?
If the bundle exe is uninstalled it would uninstall the msi. So you can install the standalone msi again after. If you try to install msi after installing bundle exe the msi will not install as the bundle already installed it. If you install MSI and then install bundle exe then you'll see two entries in ARP. There are other effects too such as if you install a newer version of the MSI with the bundle exe already installed it will upgrade the MSI. Not sure if this will present a problem other than aesthetics. Should really use a MSI alone or burn alone and not mix the two. Wes -Original Message- From: Tomas Köhn [mailto:tomas.k...@cellavision.se] Sent: July-23-13 6:09 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] [wix-users] Impact of installed burn? Thanks, Will this impact future installs of .msi files which has been part of bundle before (but has been uninstalled)? / Tomas -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: den 22 juli 2013 14:40 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] [wix-users] Impact of installed burn? Users will have no way to uninstall burn package AFAIK. See http://www.joyofsetup.com/2013/07/05/burn-zero-one-or-n/ . Wes -Original Message- From: Tomas Köhn [mailto:tomas.k...@cellavision.se] Sent: July-22-13 8:20 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] [wix-users] Impact of installed burn? We need to support installation from both .exe and .msi (for remote program distribution). As I understand, burn can't be used without installing into ARP. We want the program installation to be the same from both .exe and .msi. If I set DisableModify=yes DisableRemove=yes, the bundle (burn) application will not be visible in Program Feature. What will be stored in ARP and how will this impact the installed .msi? Regards Tomas -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [wix-users] Impact of installed burn?
Users will have no way to uninstall burn package AFAIK. See http://www.joyofsetup.com/2013/07/05/burn-zero-one-or-n/ . Wes -Original Message- From: Tomas Köhn [mailto:tomas.k...@cellavision.se] Sent: July-22-13 8:20 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] [wix-users] Impact of installed burn? We need to support installation from both .exe and .msi (for remote program distribution). As I understand, burn can't be used without installing into ARP. We want the program installation to be the same from both .exe and .msi. If I set DisableModify=yes DisableRemove=yes, the bundle (burn) application will not be visible in Program Feature. What will be stored in ARP and how will this impact the installed .msi? Regards Tomas -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Start application after WIX bundle installation
Are you using wixstba? If so can use a wix variable LaunchTarget like this: Variable Name=LaunchTarget Value=path to exe/. This will show a launch button on finish that the user can click. Wes -Original Message- From: andreas.paetz...@btc-ag.com [mailto:andreas.paetz...@btc-ag.com] Sent: July-19-13 6:16 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Start application after WIX bundle installation Hi together, ist there any possibility to start an application after successful bundle installation? Already spent hours with google to find a working solution but it seems that there isn't any... Thanks for your help. Kind regards, Andreas -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Convert from MSI to EXE
That's to create a custom bootstrapper application (BA). Easiest thing is to use the premade or standard one with WIX: wixstba at least at first to learn. On wixtoolset.org there is link to a book on wix and I suggest starting with that. Also link to a manual and blogs on burn which are useful too. -Original Message- From: Rahul V [mailto:rahul8...@gmail.com] Sent: July-19-13 10:42 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Convert from MSI to EXE Please read this example, this will answer all your questions. http://bryanpjohnston.com/2012/09/28/custom-wix-managed-bootstrapper-application/ Regards, Rahul On Thu, Jul 18, 2013 at 11:49 PM, Mamidi, Balasubrahmanyam balu.mam...@flightsafety.com wrote: Thanks for reply steve. not clear what you're saying.. Let me reframe what I want.. When I compile my project I want .exe to be generated. I do not want .msi file to be generated. Is it possible using WIX? -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: Thursday, July 18, 2013 1:00 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Convert from MSI to EXE [P] Classification: Public Hi Balu, You can use burn (bootstrapper) (which is an EXE) to launch your MSI's Steve -Original Message- From: Mamidi, Balasubrahmanyam [mailto:balu.mam...@flightsafety.com] Sent: July-18-13 1:52 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Convert from MSI to EXE Hi, currently we are creating our product to MSI file (using wix ), now client is asking convert all products to EXE's. How much effort to do this and give me some idea please? Is something change output file extension to from *.msi to *.exe Thanks, Balu -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users This message has been marked as Public by Steven Ogilvie on July-18-13 1:59:37 PM. The above classification labels were added to the message by TITUS Message Classification. For more information visit www.titus.com. -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Convert from MSI to EXE
The MSI file is a database that gets run by msiexec.exe which is part of windows to do the install. Can't just convert it to exe. Would need to create a bootstrapper exe. Burn is the wix version of a bootstrapper. -Original Message- From: Mamidi, Balasubrahmanyam [mailto:balu.mam...@flightsafety.com] Sent: July-18-13 3:20 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Convert from MSI to EXE Thanks for reply steve. not clear what you're saying.. Let me reframe what I want.. When I compile my project I want .exe to be generated. I do not want .msi file to be generated. Is it possible using WIX? -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: Thursday, July 18, 2013 1:00 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Convert from MSI to EXE [P] Classification: Public Hi Balu, You can use burn (bootstrapper) (which is an EXE) to launch your MSI's Steve -Original Message- From: Mamidi, Balasubrahmanyam [mailto:balu.mam...@flightsafety.com] Sent: July-18-13 1:52 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Convert from MSI to EXE Hi, currently we are creating our product to MSI file (using wix ), now client is asking convert all products to EXE's. How much effort to do this and give me some idea please? Is something change output file extension to from *.msi to *.exe Thanks, Balu -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users This message has been marked as Public by Steven Ogilvie on July-18-13 1:59:37 PM. The above classification labels were added to the message by TITUS Message Classification. For more information visit www.titus.com. -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bundle within bundle uncompressed MSIs
I'm trying out the addon bundle feature again. Each of my addons have an external MSI file (compressed attribute set to no). I'm added my addons to my main bundle using ExePackage elements as I want them installed by default with my application. When I build my main bundle it copies over the addon EXEs to the release/debug folder but does not copy the MSIs of each addon. Can I add a payload element as a child to the ExePackage with compressed=no in my main bundle to copy them to my main bundle release/debug folder? Wanted to know best thing to do as thinking can also use a MSBuild copy task to do it as well. Wes -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn: Related Package ID
Happens to me as well. Burn is not smart enough to get the name.
Wes
-Original Message-
From: Adam Roper [mailto:adam.ro...@guidance.eu.com]
Sent: July-02-13 9:46 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Burn: Related Package ID
Hi,
I have a Burn bundle that incorporates 9 other MSI packages and everything
works remarkably well, other than one thing.
During installation the names of the included packages is displayed on the
installation screen as they are installed in turn. However I have noticed that
when I install a new version of the compiled Burn package over the top of an
existing package, then following what I think should be the final package there
is an extra notification to say that package {GUID} is being installed, where
the GUID is a real GUID of course. I believe that this 'anonymous' may
actually be the encompassing package, but the bundle has an ID so I can't think
why it would be displaying this.
I've searched through the registry for this GUID but it doesn't exist. This is
completely reproducible, at least with my bundle. Any ideas?
Cheers
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn: Related Package ID
Yeah, shouldn't have said burn.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: July-02-13 11:45 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn: Related Package ID
Burn doesn't do things that the BA can do easily to avoid bloating the engine
(and the BA interface) with lots of stuff to maintain. In WiX v3.8 the wixstdba
looks up the display name for the related bundle and displays that.
On Tue, Jul 2, 2013 at 6:40 AM, Wesley Manning wmann...@dynagen.ca wrote:
Happens to me as well. Burn is not smart enough to get the name.
Wes
-Original Message-
From: Adam Roper [mailto:adam.ro...@guidance.eu.com]
Sent: July-02-13 9:46 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Burn: Related Package ID
Hi,
I have a Burn bundle that incorporates 9 other MSI packages and
everything works remarkably well, other than one thing.
During installation the names of the included packages is displayed on
the installation screen as they are installed in turn. However I have
noticed that when I install a new version of the compiled Burn package
over the top of an existing package, then following what I think
should be the final package there is an extra notification to say that
package {GUID} is being installed, where the GUID is a real GUID of
course. I believe that this 'anonymous' may actually be the
encompassing package, but the bundle has an ID so I can't think why it would
be displaying this.
I've searched through the registry for this GUID but it doesn't exist.
This is completely reproducible, at least with my bundle. Any ideas?
Cheers
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Suppress options in bundle
You need xmlns:bal=http://schemas.microsoft.com/wix/BalExtension; in the Wix element. And then: bal:WixStandardBootstrapperApplication SuppressOptionsUI=yes ... / -Original Message- From: Blair Murri [mailto:os...@live.com] Sent: June-18-13 6:04 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Suppress options in bundle I haven't played around with the standard BA much but wouldn't changing the theme work? Blair From: davidm...@omprompt.com To: wix-users@lists.sourceforge.net Date: Thu, 13 Jun 2013 13:15:41 +0100 Subject: [WiX-users] Suppress options in bundle Hi all, I am trying to hide the options button on my bundle install as the install folder is fixed and cannot be changed. I am having trouble getting the SuppressOptionUI=yes to work. I am using WiX 3.7 and here is my bundle.wxs from my VS2010 solution. Any help would be greatly appreciated. ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Bundle Name=Document Converters Version=$(var.Version) Manufacturer=OmPrompt UpgradeCode=e2e24e5c-5fef-4c16-9b5d-469b67b269a7 Condition=((VersionNT = v5.1) AND (ServicePackLevel = 3)) OR ((VersionNT = v5.2) AND (ServicePackLevel = 2)) OR (VersionNT = v6.0) BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.HyperlinkLicense WixStandardBootstrapperApplication SuppressOptionsUI=yes / /BootstrapperApplicationRef WixVariable Id=WixStdbaLogo Value=Resource\logo.png / WixVariable Id=WixStdbaLicenseUrl Value= / Variable Name=InstallFolder Type=string Value=[ProgramFilesFolder]Omprompt\Document Converters / Variable Name=LaunchTarget Value=[InstallFolder]\ConverterController.exe/ Chain PackageGroupRef Id=NetFx40Redist / RollbackBoundary / MsiPackage Id=WIXConverterInstaller Compressed=yes SourceFile=$(var.WIXConverterInstaller.TargetPath) Vital=yes /MsiPackage /Chain /Bundle /Wix Thanks in advance, Dave Moss -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Java Program Installer
AFAIK you can have 64bit MSI install 32bit components. But a 32bit MSI can't install 64bit components. There is a 64bit attribute on the component to say if its 32bit or 64bit... Just from memory, never had to do this. -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: June-18-13 12:48 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Java Program Installer As far as I am aware, it is not possible/supported to install 32 bit components in a 64 bit MSI. There are unsupported hacks out there, but they would fail ICE validation and wouldn't be Logo certified. If you already have a 64 bit and 32bit MSI, and the 64 bit MSI installs only 64bit components, then it would be near trivial to setup a Bundle to do the registry searches you previously wanted to do in a MSI and conditionally install either the 32 bit or 64 bit MSI on a 64 bit machine. In addition, this same bundle can be deployed to a 32 bit machine. -Original Message- From: Tim Hawes [mailto:haw...@anx.com] Sent: Tuesday, June 18, 2013 9:58 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Java Program Installer My understanding is that a 64bit installer can install 32bit binaries? I am using this just for 64bit systems. I am already building a separate 32bit installer for 32bit systems (which only needs to test for JRE version). The problem I describe below is a 64bit installer which must determine which JRE is installed on the system, since it is possible to install both a 32bit JRE and a 64bit JRE. If I need separate installer for this, then forget it. It will just have to fail if it doesn't find the 64bit JRE. Hoover, Jacob writes: You need 2 MSI packages, one for the 64 bit components and one for the x86 components. You can utilize burn to do the bitness of the OS test and then decide which installer to invoke. -Original Message- From: Tim Hawes [mailto:haw...@anx.com] Sent: Tuesday, June 18, 2013 8:38 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Java Program Installer I have a product that will use a 64bit installer. It uses an exe wrapper for the jar files so that the programs can be entered as Windows services and the config programs can run from the Start menu. The wrapper requires different binaries for the type of JVM installed, 32bit executables for runnning the jars under a 32bit JVM, and 64bit executables for running the same jars under a 64bit JVM. The requirements for the 64bit installer is to detect which JVM is installed. If it finds the 64bit JRE, it stops there and installs the 64bit exe's (and the associated jar files) under ProgramFiles64Folder, upon failing that, it should search for the 32bit JRE, and then install the 32bit exe's (and associated jar files) under ProgramFilesFolder. Here is the WiX snippet I have: Property Id=JRE64 RegistrySearch Id=J64REVER Type=raw Root=HKLM Key=Software\JavaSoft\Java Runtime Environment\CurrentVersion Name=JavaVersion / /Property Property Id=JRE32 RegistrySearch Id=J32REVER Type=raw Root=HKLM Key=Wow6432Node\JavaSoft\Java Runtime Environment\CurrentVersion Name=JavaVersion / /Property Condition Message=This application requires Java Version 7 or higher ![CDATA[ (Installed OR JRE32 OR JRE64) AND JRE32 1.7 AND JRE64 1.7 ]] /Condition I don't think my condition is right. What I want it to say, in pseudo code, is: IF ( (NOT JRE32 OR JRE32 1.7) AND (NOT JRE64 OR JRE64 1.7) ) THEN stop install with the message. Since it is possible to have both an 32bit JRE and 64bit JRE installed on a 64bit system, it is important to check for both, but default to the 64bit JRE if it is up-to-date and available. Thanks! -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net
Re: [WiX-users] Java Program Installer
Curiosity got better of me. It seems that for a 64bit MSI Win64=yes is assumed so you only need to set the Win64 attribute (= no) for the 32bit components. -Original Message- From: Daniel Madill [mailto:dan.mad...@quanser.com] Sent: June-18-13 3:23 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Java Program Installer I install 32-bit components using a 64-bit MSI all the time in order to have a single MSI that provides support for our APIs to both 32-bit and 64-bit applications running on a 64-bit O/S. It works just fine. I use WiX preprocessor directives to build a pure 32-bit MSI for 32-bit platforms and a mixed 64-bit MSI for 64-bit platforms from the same WiX source. Daniel Madill -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: June-18-13 2:17 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Java Program Installer AFAIK you can have 64bit MSI install 32bit components. But a 32bit MSI can't install 64bit components. There is a 64bit attribute on the component to say if its 32bit or 64bit... Just from memory, never had to do this. -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: June-18-13 12:48 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Java Program Installer As far as I am aware, it is not possible/supported to install 32 bit components in a 64 bit MSI. There are unsupported hacks out there, but they would fail ICE validation and wouldn't be Logo certified. If you already have a 64 bit and 32bit MSI, and the 64 bit MSI installs only 64bit components, then it would be near trivial to setup a Bundle to do the registry searches you previously wanted to do in a MSI and conditionally install either the 32 bit or 64 bit MSI on a 64 bit machine. In addition, this same bundle can be deployed to a 32 bit machine. -Original Message- From: Tim Hawes [mailto:haw...@anx.com] Sent: Tuesday, June 18, 2013 9:58 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Java Program Installer My understanding is that a 64bit installer can install 32bit binaries? I am using this just for 64bit systems. I am already building a separate 32bit installer for 32bit systems (which only needs to test for JRE version). The problem I describe below is a 64bit installer which must determine which JRE is installed on the system, since it is possible to install both a 32bit JRE and a 64bit JRE. If I need separate installer for this, then forget it. It will just have to fail if it doesn't find the 64bit JRE. Hoover, Jacob writes: You need 2 MSI packages, one for the 64 bit components and one for the x86 components. You can utilize burn to do the bitness of the OS test and then decide which installer to invoke. -Original Message- From: Tim Hawes [mailto:haw...@anx.com] Sent: Tuesday, June 18, 2013 8:38 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Java Program Installer I have a product that will use a 64bit installer. It uses an exe wrapper for the jar files so that the programs can be entered as Windows services and the config programs can run from the Start menu. The wrapper requires different binaries for the type of JVM installed, 32bit executables for runnning the jars under a 32bit JVM, and 64bit executables for running the same jars under a 64bit JVM. The requirements for the 64bit installer is to detect which JVM is installed. If it finds the 64bit JRE, it stops there and installs the 64bit exe's (and the associated jar files) under ProgramFiles64Folder, upon failing that, it should search for the 32bit JRE, and then install the 32bit exe's (and associated jar files) under ProgramFilesFolder. Here is the WiX snippet I have: Property Id=JRE64 RegistrySearch Id=J64REVER Type=raw Root=HKLM Key=Software\JavaSoft\Java Runtime Environment\CurrentVersion Name=JavaVersion / /Property Property Id=JRE32 RegistrySearch Id=J32REVER Type=raw Root=HKLM Key=Wow6432Node\JavaSoft\Java Runtime Environment\CurrentVersion Name=JavaVersion / /Property Condition Message=This application requires Java Version 7 or higher ![CDATA[ (Installed OR JRE32 OR JRE64) AND JRE32 1.7 AND JRE64 1.7 ]] /Condition I don't think my condition is right. What I want it to say, in pseudo code, is: IF ( (NOT JRE32 OR JRE32 1.7) AND (NOT JRE64 OR JRE64 1.7) ) THEN stop install with the message. Since it is possible to have both an 32bit JRE and 64bit JRE installed on a 64bit system, it is important to check for both, but default to the 64bit JRE if it is up-to-date and available. Thanks
Re: [WiX-users] Can we package html files?
Go here: http://www.wixtoolset.org/ Under documentation there is a book you can buy and/or a link to a tutorial. When I started I got the book. Trying to do it without is painful. The tutorial is pretty good as well. -Original Message- From: Nitin Sharma [mailto:onlynit...@gmail.com] Sent: June-13-13 10:44 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Can we package html files? Hey,thats great news.i kept looking the internet but found nothing that could help.can you please point me to any tutorials.thanks in advance. Nitin On 13-Jun-2013 7:05 PM, John Cooper jocoo...@jackhenry.com wrote: Yes. All but one of my installers supports a web-based WCF service. One of these services also deploys a significant amount of HTML, jScript, and CSS. Payload is payload. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.(r) Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Nitin Sharma [mailto:onlynit...@gmail.com] Sent: Thursday, June 13, 2013 1:11 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Can we package html files? Hi Experts, My second day using WiX and I ran into this challenge. I have a bunch of html,css and js files (200+) organized in nested folder structure. Is it possible to use wix for packaging these files and then run this setup on another machine to install the same folder structure and files? Your expert guidance will be much appreciated. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Can wix monitor child process ?
I don't think so. Other people here have created their own custom executable that wraps the installer in weird cases like this. Your wrapper would have to handle install, uninstall, and modify command line args. -Original Message- From: Benjamin Mayrargue [mailto:benja...@vapolia.fr] Sent: June-05-13 6:50 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Can wix monitor child process ? Hi, i have an ExePackage in which the exe uncompresses some files, then run an installer and returns without waiting for this installer to finish. Is there an option to set in wix, where it would monitor the child processes created by the exe in the ExePackage and wait for them to finish before going to the next step ? Thks, Benjamin. -- How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Can wix monitor child process ?
Actually burn wouldn't be able to do that anyways because it has to know if the installer failed so it can rollback the changes. Unless the package is not vital in which case you specify Vital=no. Burn expects an exitcode (exitcode element) from exe to indicate success/failure. I never used exepackage so maybe others can help. -Original Message- From: Benjamin Mayrargue [mailto:benja...@vapolia.fr] Sent: June-05-13 6:50 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Can wix monitor child process ? Hi, i have an ExePackage in which the exe uncompresses some files, then run an installer and returns without waiting for this installer to finish. Is there an option to set in wix, where it would monitor the child processes created by the exe in the ExePackage and wait for them to finish before going to the next step ? Thks, Benjamin. -- How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] *Package Permanent attribute
Just means burn will not try to uninstall it. The package will also appear in ARP. -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: May-31-13 4:37 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] *Package Permanent attribute Can someone please clarify the effect of the Permanent attribute for a package (e.g. MsiPackage, ExePackage)? The documentation (http://wix.sourceforge.net/manual-wix3/wix_xsd_msipackage.htm) says, Specifies whether the package can be uninstalled. The default is 'no'. Making a package impossible to uninstall seems extremely frustrating for a user, and in my own MsiPackage, when Permanent='yes', I can still uninstall it, so...I don't think I understand what it does. Alain *** Alain Forget, Ph.D. Postdoctoral Researcher CyLab, Carnegie Mellon University afor...@cmu.edu http://cups.cs.cmu.edu/~aforget/ *** -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] *Package Permanent attribute
Correct. I should be more precise. A bundle contains burn engine and packages. From: Edwin Castro [mailto:egca...@gmail.com] Sent: May-31-13 4:51 PM To: afor...@cmu.edu; General discussion for Windows Installer XML toolset. Cc: Wesley Manning Subject: Re: [WiX-users] *Package Permanent attribute My understanding is that a Bundle is processed by the burn engine. ARP == Add/Remove Programs On Fri, May 31, 2013 at 12:44 PM, Alain Forget afor...@cmu.edumailto:afor...@cmu.edu wrote: By burn, you mean what I'm referring to as the Bundle? And by ARP, you mean Add/Remove Programs? Just making sure I understand. :-) Alain -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.camailto:wmann...@dynagen.ca] Sent: May 31, 2013 15:41 To: afor...@cmu.edumailto:afor...@cmu.edu; General discussion for Windows Installer XML toolset. Subject: RE: [WiX-users] *Package Permanent attribute Just means burn will not try to uninstall it. The package will also appear in ARP. -Original Message- From: Alain Forget [mailto:afor...@cmu.edumailto:afor...@cmu.edu] Sent: May-31-13 4:37 PM To: wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Subject: [WiX-users] *Package Permanent attribute Can someone please clarify the effect of the Permanent attribute for a package (e.g. MsiPackage, ExePackage)? The documentation (http://wix.sourceforge.net/manual-wix3/wix_xsd_msipackage.htm) says, Specifies whether the package can be uninstalled. The default is 'no'. Making a package impossible to uninstall seems extremely frustrating for a user, and in my own MsiPackage, when Permanent='yes', I can still uninstall it, so...I don't think I understand what it does. Alain *** Alain Forget, Ph.D. Postdoctoral Researcher CyLab, Carnegie Mellon University afor...@cmu.edumailto:afor...@cmu.edu http://cups.cs.cmu.edu/~aforget/ *** -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 ___ WiX-users mailing list WiX-users@lists.sourceforge.netmailto:WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 ___ WiX-users mailing list WiX-users@lists.sourceforge.netmailto:WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Edwin G. Castro -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Including UtilExtension a Fragment
Not if you are embedding exe in msi. The other way around maybe. -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: May-30-13 4:55 PM To: 'John Cooper'; 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Including UtilExtension a Fragment Hm, I've just been using Candle and Light thus far. Since I'm now including an EXE in my MSI, I take it I now need to use Burn? If so, is there a Burn tutorial somewhere? I've been unable to find one. Alain -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: May 30, 2013 15:39 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset. Subject: RE: [WiX-users] Including UtilExtension a Fragment Do you have the Util extension added as a reference to your Burn project? -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: Thursday, May 30, 2013 2:27 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Including UtilExtension a Fragment I can't figure out why Candle doesn't seem to find the RegistrySearch element in the util namespace, as it throws this error: Fragment element contains an unhandled extension element 'util:RegistrySearch'. Please ensure that the extension for elements in the 'http://schemas.microsoft. com/wix/UtilExtension' namespace has been provided. Maybe I'm not using the Fragment as it is intended? Any advice would be appreciated. This is what my source looks like: Wix xmlns='http://schemas.microsoft.com/wix/2006/wi' xmlns:util=http://schemas.microsoft.com/wix/UtilExtension; Fragment util:RegistrySearch Id=Java7FamilyVersion Root=HKLM Key=SOFTWARE\JavaSoft\Java Runtime Environment Value=Java7FamilyVersion Variable=Java7FamilyVersion / util:RegistrySearch Root=HKLM Key=SOFTWARE\JavaSoft\Java Runtime Environment\[Java7FamilyVersion]\MSI Value=PRODUCTVERSION Variable=JavaProductVersion After=Java7FamilyVersion Condition=Java7FamilyVersion / PackageGroup Id=Java7Runtime ExePackage Id=Java7Runtime DisplayName=Java Runtime Version 7 Cache=no Compressed=yes PerMachine=yes Permanent=yes Vital=yes Name=lib\jre-7u21-windows-i586.exe SourceFile=\lib\jre-7u21-windows-i586.exe InstallCommand=/s ADDLOCAL=jrecore IEXPLORER=1 MOZILLA=1 JAVAUPDATE=0 JU=0 SYSTRAY=0 AUTOUPDATECHECK=0 REBOOT=Suppress /L*v quot;[WixBundleLog_Java7Runtime]quot; DetectCondition=Java7FamilyVersion AND (JavaProductVersion gt;= v7.0.210) /ExePackage /PackageGroup /Fragment Product... Alain -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: May 30, 2013 14:17 To: 'Neil Sleightholm' Subject: RE: [WiX-users] Download and install Java Oh interesting, so I don't even need to define WixBundleLog_Java7Runtime? Another issue: candle couldn't recognise the util prefix for the util:RegistrySearch elements, so I added xmlns:util=http://schemas.microsoft.com/wix/UtilExtension; to my top-level Wix element, but I'm now getting the following candle error: Fragment element contains an unhandled extension element 'util:RegistrySearch'. Please ensure that the extension for elements in the 'http://schemas.microsoft. com/wix/UtilExtension' namespace has been provided. Any idea what I might be missing? Alain -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: May 30, 2013 14:03 To: afor...@cmu.edu Subject: RE: [WiX-users] Download and install Java Yes WixBundleLog_Java7Runtime is the log file, WiX creates this variable for you and is WixBundleLog with your ExePackage/@Id appended e.g. %temp%\YouBundleName_20130430071941_0_Java7Runtime.log. Neil -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: 30 May 2013 18:50 To: Neil Sleightholm; 'General discussion for Windows Installer XML toolset.' Subject: RE: [WiX-users] Download and install Java A perfect, I understand now, thanks. And I assume [WixBundleLog_Java7Runtime] is the location you want the Java installer log to output. Alain -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: May 30, 2013 13:43 To: afor...@cmu.edu; 'General discussion for Windows Installer XML toolset.' Subject: RE: [WiX-users] Download and install Java 1.7.0_21 is not a normal version number that WiX can compare so
Re: [WiX-users] Including UtilExtension a Fragment
Burn is for the bootstrapper only (creates bootstrapper exe) but I think you knew that? If you are using MSI only then I think you can embed exe in the MSI like any other file. Never did that to run install so others would have to comment on how to get it to run. Wes -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: May-30-13 5:07 PM To: Wesley Manning; 'General discussion for Windows Installer XML toolset.'; 'John Cooper' Subject: RE: [WiX-users] Including UtilExtension a Fragment Now I'm really confused. :-) So to explain a bit more, the EXE is the Java Runtime Environment installer, and the MSI is my installer. So I want to include the EXE in my MSI, and (silently) run the JRE EXE if it isn't already installed (determined by util:RegistrySearch elements), before the stuff in my installer starts getting unpacked and run. So...if you're suggesting I put my MSI in the EXE, that's not possible, because I can't (or at least don't think) I can or should put my MSI in the JRE EXE. Did you have something else in mind? Alain -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: May 30, 2013 16:01 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset.; 'John Cooper' Subject: RE: [WiX-users] Including UtilExtension a Fragment Not if you are embedding exe in msi. The other way around maybe. -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: May-30-13 4:55 PM To: 'John Cooper'; 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Including UtilExtension a Fragment Hm, I've just been using Candle and Light thus far. Since I'm now including an EXE in my MSI, I take it I now need to use Burn? If so, is there a Burn tutorial somewhere? I've been unable to find one. Alain -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: May 30, 2013 15:39 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset. Subject: RE: [WiX-users] Including UtilExtension a Fragment Do you have the Util extension added as a reference to your Burn project? -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: Thursday, May 30, 2013 2:27 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Including UtilExtension a Fragment I can't figure out why Candle doesn't seem to find the RegistrySearch element in the util namespace, as it throws this error: Fragment element contains an unhandled extension element 'util:RegistrySearch'. Please ensure that the extension for elements in the 'http://schemas.microsoft. com/wix/UtilExtension' namespace has been provided. Maybe I'm not using the Fragment as it is intended? Any advice would be appreciated. This is what my source looks like: Wix xmlns='http://schemas.microsoft.com/wix/2006/wi' xmlns:util=http://schemas.microsoft.com/wix/UtilExtension; Fragment util:RegistrySearch Id=Java7FamilyVersion Root=HKLM Key=SOFTWARE\JavaSoft\Java Runtime Environment Value=Java7FamilyVersion Variable=Java7FamilyVersion / util:RegistrySearch Root=HKLM Key=SOFTWARE\JavaSoft\Java Runtime Environment\[Java7FamilyVersion]\MSI Value=PRODUCTVERSION Variable=JavaProductVersion After=Java7FamilyVersion Condition=Java7FamilyVersion / PackageGroup Id=Java7Runtime ExePackage Id=Java7Runtime DisplayName=Java Runtime Version 7 Cache=no Compressed=yes PerMachine=yes Permanent=yes Vital=yes Name=lib\jre-7u21-windows-i586.exe SourceFile=\lib\jre-7u21-windows-i586.exe InstallCommand=/s ADDLOCAL=jrecore IEXPLORER=1 MOZILLA=1 JAVAUPDATE=0 JU=0 SYSTRAY=0 AUTOUPDATECHECK=0 REBOOT=Suppress /L*v quot;[WixBundleLog_Java7Runtime]quot; DetectCondition=Java7FamilyVersion AND (JavaProductVersion gt;= v7.0.210) /ExePackage /PackageGroup /Fragment Product... Alain -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: May 30, 2013 14:17 To: 'Neil Sleightholm' Subject: RE: [WiX-users] Download and install Java Oh interesting, so I don't even need to define WixBundleLog_Java7Runtime? Another issue: candle couldn't recognise the util prefix for the util:RegistrySearch elements, so I added xmlns:util=http://schemas.microsoft.com/wix/UtilExtension; to my top-level Wix element, but I'm now
Re: [WiX-users] Including UtilExtension a Fragment [P]
There's a book (only one I know) that you can buy here: http://www.packtpub.com/windows-installer-xml-3-6-developers-guide/book. Might want to get that to get up to speed quick. It was updated for burn. Yes use burn to group them together in one installer exe. This exe can contain your packages to install and the install engine. By default burn hides the MSI gui. Best practice really is to do GUI all in burn and just pass properties to MSI to configure it although depending on what you need that may be a lot of work. You can use the standard GUI (bootloading application (BA) it's called, more specifically wixstba) or write your own BA. Wixstba has some customizability via xml that you can embed as a payload. Writing your own BA would be a fair amount of work. I use the wixstba. The order they appear in chain is order get installed and reverse order for uninstall (i.e. last one in chain is first one to get installed). Chain PackageGroupRef Id=package a/ PackageGroupRef Id=package b/ /Chain Wes -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: May-30-13 5:26 PM To: 'Steven Ogilvie'; 'General discussion for Windows Installer XML toolset.'; Wesley Manning; 'John Cooper' Subject: RE: [WiX-users] Including UtilExtension a Fragment [P] I think creating a bundle is what I need to do. I've just never used Burn before, so I'm just learning now how it works. If I understand correctly, I Candle and Light my own installer into an MSI as usual, but then use Burn to package the MSI and JRE EXE together? And there will be some way to state that the JRE EXE should run before my MSI? I'm also not sure what happens to the license agreement and UI stuff from my MSI, but...I guess I'm about to find out. :-) Ideally, I'd like only one license agreement to show up, rather than two (one from the bundle, and one from my MSI). Alain -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: May 30, 2013 16:18 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset.; 'Wesley Manning'; 'John Cooper' Subject: RE: [WiX-users] Including UtilExtension a Fragment [P] Classification: Public Why don't you create a bundle and have the JRE installed first then your MSI? -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: May-30-13 4:07 PM To: 'Wesley Manning'; 'General discussion for Windows Installer XML toolset.'; 'John Cooper' Subject: Re: [WiX-users] Including UtilExtension a Fragment Now I'm really confused. :-) So to explain a bit more, the EXE is the Java Runtime Environment installer, and the MSI is my installer. So I want to include the EXE in my MSI, and (silently) run the JRE EXE if it isn't already installed (determined by util:RegistrySearch elements), before the stuff in my installer starts getting unpacked and run. So...if you're suggesting I put my MSI in the EXE, that's not possible, because I can't (or at least don't think) I can or should put my MSI in the JRE EXE. Did you have something else in mind? Alain -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: May 30, 2013 16:01 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset.; 'John Cooper' Subject: RE: [WiX-users] Including UtilExtension a Fragment Not if you are embedding exe in msi. The other way around maybe. -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: May-30-13 4:55 PM To: 'John Cooper'; 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Including UtilExtension a Fragment Hm, I've just been using Candle and Light thus far. Since I'm now including an EXE in my MSI, I take it I now need to use Burn? If so, is there a Burn tutorial somewhere? I've been unable to find one. Alain -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: May 30, 2013 15:39 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset. Subject: RE: [WiX-users] Including UtilExtension a Fragment Do you have the Util extension added as a reference to your Burn project? -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: Thursday, May 30, 2013 2:27 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Including UtilExtension a Fragment I can't figure out why Candle doesn't seem to find the RegistrySearch element in the util namespace, as it throws this error: Fragment element contains an unhandled extension element 'util:RegistrySearch'. Please ensure that the extension for elements in the 'http://schemas.microsoft. com/wix/UtilExtension' namespace has been provided. Maybe I'm not using the Fragment as it is intended? Any advice would
Re: [WiX-users] Including UtilExtension a Fragment [P]
Sorry error. I meant: (i.e. last one in chain is first one to get uninstalled). The order they appear in chain is order get installed and reverse order for uninstall (i.e. last one in chain is first one to get installed). Chain PackageGroupRef Id=package a/ PackageGroupRef Id=package b/ /Chain -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: May-30-13 5:40 PM To: afor...@cmu.edu; 'Steven Ogilvie'; 'General discussion for Windows Installer XML toolset.'; 'John Cooper' Subject: Re: [WiX-users] Including UtilExtension a Fragment [P] There's a book (only one I know) that you can buy here: http://www.packtpub.com/windows-installer-xml-3-6-developers-guide/book. Might want to get that to get up to speed quick. It was updated for burn. Yes use burn to group them together in one installer exe. This exe can contain your packages to install and the install engine. By default burn hides the MSI gui. Best practice really is to do GUI all in burn and just pass properties to MSI to configure it although depending on what you need that may be a lot of work. You can use the standard GUI (bootloading application (BA) it's called, more specifically wixstba) or write your own BA. Wixstba has some customizability via xml that you can embed as a payload. Writing your own BA would be a fair amount of work. I use the wixstba. The order they appear in chain is order get installed and reverse order for uninstall (i.e. last one in chain is first one to get installed). Chain PackageGroupRef Id=package a/ PackageGroupRef Id=package b/ /Chain Wes -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: May-30-13 5:26 PM To: 'Steven Ogilvie'; 'General discussion for Windows Installer XML toolset.'; Wesley Manning; 'John Cooper' Subject: RE: [WiX-users] Including UtilExtension a Fragment [P] I think creating a bundle is what I need to do. I've just never used Burn before, so I'm just learning now how it works. If I understand correctly, I Candle and Light my own installer into an MSI as usual, but then use Burn to package the MSI and JRE EXE together? And there will be some way to state that the JRE EXE should run before my MSI? I'm also not sure what happens to the license agreement and UI stuff from my MSI, but...I guess I'm about to find out. :-) Ideally, I'd like only one license agreement to show up, rather than two (one from the bundle, and one from my MSI). Alain -Original Message- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: May 30, 2013 16:18 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset.; 'Wesley Manning'; 'John Cooper' Subject: RE: [WiX-users] Including UtilExtension a Fragment [P] Classification: Public Why don't you create a bundle and have the JRE installed first then your MSI? -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: May-30-13 4:07 PM To: 'Wesley Manning'; 'General discussion for Windows Installer XML toolset.'; 'John Cooper' Subject: Re: [WiX-users] Including UtilExtension a Fragment Now I'm really confused. :-) So to explain a bit more, the EXE is the Java Runtime Environment installer, and the MSI is my installer. So I want to include the EXE in my MSI, and (silently) run the JRE EXE if it isn't already installed (determined by util:RegistrySearch elements), before the stuff in my installer starts getting unpacked and run. So...if you're suggesting I put my MSI in the EXE, that's not possible, because I can't (or at least don't think) I can or should put my MSI in the JRE EXE. Did you have something else in mind? Alain -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: May 30, 2013 16:01 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset.; 'John Cooper' Subject: RE: [WiX-users] Including UtilExtension a Fragment Not if you are embedding exe in msi. The other way around maybe. -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: May-30-13 4:55 PM To: 'John Cooper'; 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Including UtilExtension a Fragment Hm, I've just been using Candle and Light thus far. Since I'm now including an EXE in my MSI, I take it I now need to use Burn? If so, is there a Burn tutorial somewhere? I've been unable to find one. Alain -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: May 30, 2013 15:39 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset. Subject: RE: [WiX-users] Including UtilExtension a Fragment Do you have the Util extension added as a reference to your Burn project? -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message
Re: [WiX-users] newbie: how to reference variables ? (the doc is confusing)
What is a fragment: you mean wix fragment? You say you have 4 exe to install so you are using ExePackage element in burn? -Original Message- From: Benjamin Mayrargue [mailto:benja...@vapolia.fr] Sent: May-29-13 8:08 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] newbie: how to reference variables ? (the doc is confusing) i think i misundestand something in wix philosophy. I have 4 exe to install. I've created a bundle and 4 fragments. All is working nicely. Now i want to conditonally add a registry key when one of the fragment is executed. So i added this to the fragment: DirectoryRef Id=TARGETDIR Component Id=RegistryEntries Guid=*Condition![CDATA[NETFRAMEWORK40CLIENT AND (VersionNT v6.0)]]/ConditionRegistryKey Root=HKCU Key=Software\Company\ProductName Action=create RegistryValue Type=integer Name=State Value=1 KeyPath=yes / /RegistryKey /Component/DirectoryRef Feature Id=NetFx40ClientWebSupplement ComponentRef Id=RegistryEntries //Feature But I don't know how to reference the feature, as i only have a bundle, not a product. Why would i do that ? I'm trying to detect in the managed bootstrapper if the prerequisite bootstrapper installed the .net framework or not (which is different of detecting if .net is installed). Why would i do that ? Because i'm trying to find a way to detect if another install is already in progress and requires a reboot. the only way i have found is read the PendingFileRenameOperations key. But the prerequisite bootstrapper sets this key after strarting the managed bootstrapper ... I'm stuck. 2013/5/29 John Ludlow john.ludlow...@gmail.com Well, the bundle will *take any MSIs or other packages specified in your Chain element** *and bootstrap them. It doesn't exactly create an MSI itself. It might be best if you give more details about what you're trying to achieve, and where you're trying to use the above Condition element? On 29 May 2013 11:36, Benjamin Mayrargue benja...@vapolia.fr wrote: 100% understood ! This means a 'bundle' creates a msi bootstrapped in an exe. B. 2013/5/29 John Ludlow john.ludlow...@gmail.com I think where you're getting confused is that there are more than one type of variable in WiX. Firstly, there are preprocessor variables and condition, which are referenced like this: $(var.VariableName) !(var.LateBoundVariableName) $(env.EnvironmentVariableName) !(loc.StringID) These are available at build time and are used in things like string paths and to conditionally include fragments of code based on your build configurations. (Check out this link: http://wix.sourceforge.net/manual-wix3/preprocessor.htm) Then there are the MSI properties and conditions, which use a different syntax, because it's defined by MSI and not WiX. These are avaiable at runtime and are used to perform logic in your install - conditionally performing an action based on the environment or feature selection, getting information, controlling your installation directories and stuff like that. (Check out this link: http://msdn.microsoft.com/en-us/library/windows/desktop/aa368012(v=vs. 85).aspx ) What you have there is an MSI condition, which looks like it's based on MainFeature being installed. To break this down: (MainFeature = 3) FeatureName gets the requested state of the feature. MainFeature = 3 means if MainFeature is selected for installation, return true. AND NOT Pretty standard boolean logic - if the left hand side is true, but the right hand side is false, this will return true. (!MainFeature = 3)] !FeatureName gets the *current state* of the feature, rather than the requested state. This means if MainFeature is *currently installed* for installation, return true. Put it all together, and what you get is this: If MainFeature is selected for installation, and it's NOT currently installed, return true. Hope that helps On 29 May 2013 09:46, Benjamin Mayrargue benja...@vapolia.fr wrote: Hi all, i have a noob question. In this snippet there is a and a ! before the variable MainFeature. what does that mean ? Condition![CDATA[(MainFeature = 3) AND NOT (!MainFeature = 3)]]/Condition In the wix chm, i found the list of Wix built-in variables. But i'm unable to reference them, either in the bundle, or in my managed bootstrapper. What is the correct way to make them available ? (i'm using only a bundle). thks :) -- Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application
Re: [WiX-users] newbie: how to reference variables ? (the doc is confusing)
A fragment is a general organization / import tool at design time. They are not executed. That's why it allowed you to do what you did below. But you can't use directoryref or component in a bundle, only in MSI. You are using a managed BA? I think burn takes care of reboot and recalling itself but not sure as I don't use a custom managed BA just the standard unmanaged BA that is default - referred here as wixstba. -Original Message- From: Benjamin Mayrargue [mailto:benja...@vapolia.fr] Sent: May-29-13 1:38 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] newbie: how to reference variables ? (the doc is confusing) Yes i have a Bundle with a Chain referencing 4 ExePackage using PackageGroupRef 2013/5/29 Wesley Manning wmann...@dynagen.ca What is a fragment: you mean wix fragment? You say you have 4 exe to install so you are using ExePackage element in burn? -Original Message- From: Benjamin Mayrargue [mailto:benja...@vapolia.fr] Sent: May-29-13 8:08 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] newbie: how to reference variables ? (the doc is confusing) i think i misundestand something in wix philosophy. I have 4 exe to install. I've created a bundle and 4 fragments. All is working nicely. Now i want to conditonally add a registry key when one of the fragment is executed. So i added this to the fragment: DirectoryRef Id=TARGETDIR Component Id=RegistryEntries Guid=*Condition![CDATA[NETFRAMEWORK40CLIENT AND (VersionNT v6.0)]]/ConditionRegistryKey Root=HKCU Key=Software\Company\ProductName Action=create RegistryValue Type=integer Name=State Value=1 KeyPath=yes / /RegistryKey /Component/DirectoryRef Feature Id=NetFx40ClientWebSupplement ComponentRef Id=RegistryEntries //Feature But I don't know how to reference the feature, as i only have a bundle, not a product. Why would i do that ? I'm trying to detect in the managed bootstrapper if the prerequisite bootstrapper installed the .net framework or not (which is different of detecting if .net is installed). Why would i do that ? Because i'm trying to find a way to detect if another install is already in progress and requires a reboot. the only way i have found is read the PendingFileRenameOperations key. But the prerequisite bootstrapper sets this key after strarting the managed bootstrapper ... I'm stuck. 2013/5/29 John Ludlow john.ludlow...@gmail.com Well, the bundle will *take any MSIs or other packages specified in your Chain element** *and bootstrap them. It doesn't exactly create an MSI itself. It might be best if you give more details about what you're trying to achieve, and where you're trying to use the above Condition element? On 29 May 2013 11:36, Benjamin Mayrargue benja...@vapolia.fr wrote: 100% understood ! This means a 'bundle' creates a msi bootstrapped in an exe. B. 2013/5/29 John Ludlow john.ludlow...@gmail.com I think where you're getting confused is that there are more than one type of variable in WiX. Firstly, there are preprocessor variables and condition, which are referenced like this: $(var.VariableName) !(var.LateBoundVariableName) $(env.EnvironmentVariableName) !(loc.StringID) These are available at build time and are used in things like string paths and to conditionally include fragments of code based on your build configurations. (Check out this link: http://wix.sourceforge.net/manual-wix3/preprocessor.htm) Then there are the MSI properties and conditions, which use a different syntax, because it's defined by MSI and not WiX. These are avaiable at runtime and are used to perform logic in your install - conditionally performing an action based on the environment or feature selection, getting information, controlling your installation directories and stuff like that. (Check out this link: http://msdn.microsoft.com/en-us/library/windows/desktop/aa368012(v=vs. 85).aspx ) What you have there is an MSI condition, which looks like it's based on MainFeature being installed. To break this down: (MainFeature = 3) FeatureName gets the requested state of the feature. MainFeature = 3 means if MainFeature is selected for installation, return true. AND NOT Pretty standard boolean logic - if the left hand side is true, but the right hand side is false, this will return true. (!MainFeature = 3)] !FeatureName gets the *current state* of the feature, rather than the requested state. This means if MainFeature is *currently installed* for installation, return true. Put it all together, and what you get
Re: [WiX-users] Addon Upgrades
Just FYI. I found issue where if I upgrade my main bundle, and then uninstall it, one of the addons would not uninstall. I had to go to the registry and remove the dependency. Then uninstall the addon. I was able to repeat this, but not 100% reproducible. Issue seems to be if I uninstall a latter version addon but do not repair the remainder addons, then upgrade, then uninstall the upgrade. Testing is an issue as it takes so long to install/uninstall. Next I'm going to try to create addons without the common MSI and test that. Wes -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: May-09-13 2:07 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Addon Upgrades OK thanks. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: May-09-13 2:01 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Addon Upgrades Yes, known issue. Very, very hard to fix. On Thu, May 9, 2013 at 9:26 AM, Wesley Manning wmann...@dynagen.ca wrote: Say you have two addon bundles. Bundle 1 contains: MSI A v1.0 MSI B Bundle 2 contains: MSI A v2.0 MSI C Install bundle 1 and 2. Everything good. Then uninstall bundle 2. MSI A is removed, not reverted to v1.0. A repair restored proper state of It seems to be same issue reported in bug #2555 Major upgrades with unrelated bundles fail. Known issue then? Wes -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
