Re: [WiX-users] Bootstrapper Feature Selection
On the MsiPackage element, you must set EnableFeatureSelection=yes ( http://wixtoolset.org/documentation/manual/v3/xsd/wix/msipackage.html) to get feature information in BootstrapperApplicationData.xml. On Tue, Jun 30, 2015 at 11:04 AM, Brian C Cooke tonic...@gmail.com wrote: How can I provide functionality for feature-level selection in my custom bootstrapper created by burn? This link ( http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-create-a-feature-tree-with-burn-td7579948.html ) seems to suggest I can do so by examining the BootstrapperApplicationData.xml file, but I don't see any feature level information here, only package information. The DetectMsiFeature and PlanMsiFeature events in BootstrapperApplication have a feature ID but not other information I would need to build a proper tree for the user like Feature Name, parent Feature, etc. What is the right way to accomplish this? Am I expected to directly read the .msi in my custom bootstrapper using .NET? Is there an easier way? Thanks, Brian -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrapper Feature Selection
How can I provide functionality for feature-level selection in my custom bootstrapper created by burn? This link ( http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-create-a-feature-tree-with-burn-td7579948.html) seems to suggest I can do so by examining the BootstrapperApplicationData.xml file, but I don't see any feature level information here, only package information. The DetectMsiFeature and PlanMsiFeature events in BootstrapperApplication have a feature ID but not other information I would need to build a proper tree for the user like Feature Name, parent Feature, etc. What is the right way to accomplish this? Am I expected to directly read the .msi in my custom bootstrapper using .NET? Is there an easier way? Thanks, Brian -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrapper repeats to load itself when it failed to install prerequisites
I am using WIX3.9. WixMbaPrereqPackageId in the burn wxs file points to a exe
package of my own. When the bootstrapper is launched in silent mode and the
prerequisite exe package failed, the bootstrapper will not fail. It shows
The prerequisites were successfully installed and repeat to load itself. I
hope the bootstrapper will fail when the prerequisite exe package fails.
does anyone have an idea on this?
prerequisites of exe package failed. the bootstrapper application repeat to
be reloaded.
Log:
[0B10:099C][2015-05-11T13:17:06]i301: Applying execute package:
SimplePrereqPackage, action: Install, path: C:\ProgramData\Package
Cache\FD2754490FD9047552091A739104578EA93BD988\ThirdParty\CVInstallThirdParty\CVInstallPrereqPackages.exe,
arguments: 'C:\ProgramData\Package
Cache\FD2754490FD9047552091A739104578EA93BD988\ThirdParty\CVInstallThirdParty\CVInstallPrereqPackages.exe
C:\CVMedia\'
[0B10:099C][2015-05-11T13:17:06]e000: Error 0x80070001: Process returned
error: 0x1
[0B10:099C][2015-05-11T13:17:06]e000: Error 0x80070001: Failed to execute
EXE package.
[08C0:0458][2015-05-11T13:17:06]e000: Error 0x80070001: Failed to configure
per-machine EXE package.
[08C0:0458][2015-05-11T13:17:06]i319: Applied execute package:
SimplePrereqPackage, result: 0x80070001, restart: None
[08C0:0458][2015-05-11T13:17:06]e000: Error 0x80070001: Failed to execute
EXE package.
[0B10:099C][2015-05-11T13:17:06]i330: Removed bundle dependency provider:
{c3892c68-1bd3-431f-9e9d-5019da735022}
[0B10:099C][2015-05-11T13:17:06]i352: Removing cached bundle:
{c3892c68-1bd3-431f-9e9d-5019da735022}, from path: C:\ProgramData\Package
Cache\{c3892c68-1bd3-431f-9e9d-5019da735022}\
[08C0:0458][2015-05-11T13:17:06]i399: Apply complete, result: 0x80070001,
restart: None, ba requested restart: No
[08C0:0458][2015-05-11T13:17:06]i500: Shutting down, exit code: 0x1
[08C0:0458][2015-05-11T13:17:06]i000: The prerequisites were successfully
installed. The bootstrapper application will be reloaded.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-repeats-to-load-itself-when-it-failed-to-install-prerequisites-tp7600328.html
Sent from the wix-users mailing list archive at Nabble.com.
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper - Initializing phase very long
Thnaks for your reply Phil. We'll try this. -Message d'origine- De : Phill Hogland [mailto:phogl...@rimage.com] Envoyé : mardi 12 mai 2015 19:00 À : wix-users@lists.sourceforge.net Objet : Re: [WiX-users] Bootstrapper - Initializing phase very long Based on other threads in this forum, (although I don't know that I could find them now) I have been using Chain/@DisableSystemRestore=yes. If the issue is related to a particular machine, you might try this and see if you can avoid the problem. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-Initializing-phase-very-long-tp7600296p7600304.html Sent from the wix-users mailing list archive at Nabble.com. -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper - Initializing phase very long
Nope, sorry we still have these 6 min of initialization. -Message d'origine- De : CALCEL Sebastien [mailto:sebastien.cal...@econocom-osiatis.com] Envoyé : mercredi 13 mai 2015 14:07 À : 'General discussion about the WiX toolset.' Objet : Re: [WiX-users] Bootstrapper - Initializing phase very long Thnaks for your reply Phil. We'll try this. -Message d'origine- De : Phill Hogland [mailto:phogl...@rimage.com] Envoyé : mardi 12 mai 2015 19:00 À : wix-users@lists.sourceforge.net Objet : Re: [WiX-users] Bootstrapper - Initializing phase very long Based on other threads in this forum, (although I don't know that I could find them now) I have been using Chain/@DisableSystemRestore=yes. If the issue is related to a particular machine, you might try this and see if you can avoid the problem. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-Initializing-phase-very-long-tp7600296p7600304.html Sent from the wix-users mailing list archive at Nabble.com. -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper - Initializing phase very long
Based on other threads in this forum, (although I don't know that I could find them now) I have been using Chain/@DisableSystemRestore=yes. If the issue is related to a particular machine, you might try this and see if you can avoid the problem. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-Initializing-phase-very-long-tp7600296p7600304.html Sent from the wix-users mailing list archive at Nabble.com. -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrapper - Initializing phase very long
Hi everyone,
We're struggling with a performance issue on our bootstrapper application.
Depends on the target machine (all with the same configuration), the init phase
(when Initializing... is displayed) can be quick or very, very long (up to 10
minutes !!)
This is odd, because we have another bootstrapper for another app, and
everything is fine...
We can't find anything about this on the mailing list, nor on google.
Here our wxs :
?xml version=1.0 encoding=UTF-8?
Wix
xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:bal=http://schemas.microsoft.com/wix/BalExtension;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;
?define version=5.0.0.0 ?
?define UpgradeCode={2B361216-3134-48D5-A0D3-FD12B47CF090} ? !--Upgrade
code to use for EVEN release version (NEVER CHANGE)--
!--?define UpgradeCode={2D355C2C-2A27-4203-83EE-8BA1186E1629} ?--
!--Upgrade code to use for ODD release version (ALWAYS CHANGE)--
Bundle Name=TheApp Version=$(var.version)
Manufacturer=TheManufacturer UpgradeCode=$(var.UpgradeCode)
IconSourceFile=$(var.SolutionDir)Path\icon.ico
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.RtfLicense
bal:WixStandardBootstrapperApplication SuppressDowngradeFailure=no
SuppressOptionsUI=yes ShowVersion=yes
LicenseFile=$(var.SolutionDir)TheApp\License.rtf
LogoFile=$(var.SolutionDir)TheApp\icon.ico/
/BootstrapperApplicationRef
Chain
PackageGroupRef Id=NetFx45Redist/
MsiPackage SourceFile=$(var.SolutionDir)ServiceSetup\ServiceSetup.msi
Permanent=yes DisplayInternalUI=no Visible=yes /
MsiPackage SourceFile=$(var.MultipleReportMsi.TargetDir)TheApp.msi
Permanent=no DisplayInternalUI=yes Visible=no /
/Chain
/Bundle
/Wix
If anyone could help us or at least give us a hint on where to search, that
would be great!
Thanks in advance,
Sébastien.
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper - Initializing phase very long
Bundle log file would be much more telling of where the delay is.
-Original Message-
From: CALCEL Sebastien [mailto:sebastien.cal...@econocom-osiatis.com]
Sent: Tuesday, May 12, 2015 7:58 AM
To: 'wix-users@lists.sourceforge.net'
Cc: BONNET Alexandre
Subject: [WiX-users] Bootstrapper - Initializing phase very long
Hi everyone,
We're struggling with a performance issue on our bootstrapper application.
Depends on the target machine (all with the same configuration), the init phase
(when Initializing... is displayed) can be quick or very, very long (up to 10
minutes !!)
This is odd, because we have another bootstrapper for another app, and
everything is fine...
We can't find anything about this on the mailing list, nor on google.
Here our wxs :
?xml version=1.0 encoding=UTF-8?
Wix
xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:bal=http://schemas.microsoft.com/wix/BalExtension;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;
?define version=5.0.0.0 ?
?define UpgradeCode={2B361216-3134-48D5-A0D3-FD12B47CF090} ? !--Upgrade
code to use for EVEN release version (NEVER CHANGE)--
!--?define UpgradeCode={2D355C2C-2A27-4203-83EE-8BA1186E1629} ?--
!--Upgrade code to use for ODD release version (ALWAYS CHANGE)--
Bundle Name=TheApp Version=$(var.version)
Manufacturer=TheManufacturer UpgradeCode=$(var.UpgradeCode)
IconSourceFile=$(var.SolutionDir)Path\icon.ico
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.RtfLicense
bal:WixStandardBootstrapperApplication SuppressDowngradeFailure=no
SuppressOptionsUI=yes ShowVersion=yes
LicenseFile=$(var.SolutionDir)TheApp\License.rtf
LogoFile=$(var.SolutionDir)TheApp\icon.ico/
/BootstrapperApplicationRef
Chain
PackageGroupRef Id=NetFx45Redist/
MsiPackage SourceFile=$(var.SolutionDir)ServiceSetup\ServiceSetup.msi
Permanent=yes DisplayInternalUI=no Visible=yes /
MsiPackage SourceFile=$(var.MultipleReportMsi.TargetDir)TheApp.msi
Permanent=no DisplayInternalUI=yes Visible=no /
/Chain
/Bundle
/Wix
If anyone could help us or at least give us a hint on where to search, that
would be great!
Thanks in advance,
Sébastien.
--
One dashboard for servers and applications across Physical-Virtual-Cloud Widest
out-of-the-box monitoring support with 50+ applications Performance metrics,
stats and reports that give you Actionable Insights Deep dive visibility with
transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper - Initializing phase very long
: WixBundleLog_TheApp.msi =
C:\Users\calcel\AppData\Local\Temp\TheApp_2015051219_0_TheApp.msi.log
[1E58:0ECC][2015-05-12T10:07:52]i410: Variable: WixBundleManufacturer = Company
[1E58:0ECC][2015-05-12T10:07:52]i410: Variable: WixBundleName = TheApp
[1E58:0ECC][2015-05-12T10:07:52]i410: Variable: WixBundleOriginalSource =
C:\Users\calcel\Desktop\TheApp.exe
[1E58:0ECC][2015-05-12T10:07:52]i410: Variable: WixBundleOriginalSourceFolder =
C:\Users\calcel\Desktop\
[1E58:0ECC][2015-05-12T10:07:52]i410: Variable: WixBundleProviderKey =
{97d962d5-a96c-460c-ba19-b07a4aa85227}
[1E58:0ECC][2015-05-12T10:07:52]i410: Variable: WixBundleRollbackLog_TheApp.msi
=
C:\Users\calcel\AppData\Local\Temp\TheApp_2015051219_0_TheApp.msi_rollback.log
[1E58:0ECC][2015-05-12T10:07:52]i410: Variable: WixBundleTag =
[1E58:0ECC][2015-05-12T10:07:52]i410: Variable: WixBundleVersion = 5.0.0.0
[1E58:0ECC][2015-05-12T10:07:52]i007: Exit code: 0x0, restarting: No
-Message d'origine-
De : Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Envoyé : mardi 12 mai 2015 16:30
À : General discussion about the WiX toolset.
Cc : BONNET Alexandre
Objet : Re: [WiX-users] Bootstrapper - Initializing phase very long
Bundle log file would be much more telling of where the delay is.
-Original Message-
From: CALCEL Sebastien [mailto:sebastien.cal...@econocom-osiatis.com]
Sent: Tuesday, May 12, 2015 7:58 AM
To: 'wix-users@lists.sourceforge.net'
Cc: BONNET Alexandre
Subject: [WiX-users] Bootstrapper - Initializing phase very long
Hi everyone,
We're struggling with a performance issue on our bootstrapper application.
Depends on the target machine (all with the same configuration), the init phase
(when Initializing... is displayed) can be quick or very, very long (up to 10
minutes !!)
This is odd, because we have another bootstrapper for another app, and
everything is fine...
We can't find anything about this on the mailing list, nor on google.
Here our wxs :
?xml version=1.0 encoding=UTF-8?
Wix
xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:bal=http://schemas.microsoft.com/wix/BalExtension;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;
?define version=5.0.0.0 ?
?define UpgradeCode={2B361216-3134-48D5-A0D3-FD12B47CF090} ? !--Upgrade
code to use for EVEN release version (NEVER CHANGE)--
!--?define UpgradeCode={2D355C2C-2A27-4203-83EE-8BA1186E1629} ?--
!--Upgrade code to use for ODD release version (ALWAYS CHANGE)--
Bundle Name=TheApp Version=$(var.version)
Manufacturer=TheManufacturer UpgradeCode=$(var.UpgradeCode)
IconSourceFile=$(var.SolutionDir)Path\icon.ico
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.RtfLicense
bal:WixStandardBootstrapperApplication SuppressDowngradeFailure=no
SuppressOptionsUI=yes ShowVersion=yes
LicenseFile=$(var.SolutionDir)TheApp\License.rtf
LogoFile=$(var.SolutionDir)TheApp\icon.ico/
/BootstrapperApplicationRef
Chain
PackageGroupRef Id=NetFx45Redist/
MsiPackage SourceFile=$(var.SolutionDir)ServiceSetup\ServiceSetup.msi
Permanent=yes DisplayInternalUI=no Visible=yes /
MsiPackage SourceFile=$(var.MultipleReportMsi.TargetDir)TheApp.msi
Permanent=no DisplayInternalUI=yes Visible=no /
/Chain
/Bundle
/Wix
If anyone could help us or at least give us a hint on where to search, that
would be great!
Thanks in advance,
Sébastien.
--
One dashboard for servers and applications across Physical-Virtual-Cloud Widest
out-of-the-box monitoring support with 50+ applications Performance metrics,
stats and reports that give you Actionable Insights Deep dive visibility with
transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
One dashboard for servers and applications across Physical-Virtual-Cloud Widest
out-of-the-box monitoring support with 50+ applications Performance metrics,
stats and reports that give you Actionable Insights Deep dive visibility with
transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm
Re: [WiX-users] Bootstrapper for multiple cultures
My comment was based primarily on this thread http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-td7596896.html where I detailed two concerns which I observed after using embedTransform.exe, in the maner described here http://wix.tramontana.co.hu/tutorial/transforms/morphing-installers , but I included these MSIs i my Bundle chain. The scenarios that I encountered are related to that fact that Burn fingerprints each MSI at build time, but at runtime when the embedded MSI transforms are applied they changed the ProductID (and possibly other details which Burn uses to fingerprint the MSI) causing the observed problems. Others in the forum indicated that this use of Burn is unsupported. I have seen this topic come up in other threads with similar indication that Burn does not currently support this scenario and that there may be an open feature request in this area. Also in thist thread http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-td7596896.html , linked above, Tobias that he adds the transforms to the Bundle chain rather than embeding them in the MSI. I did not try that approach, so I cannot provide more details on that approach. I am sure that there may be other approaches. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-for-multiple-cultures-tp7598840p7600115.html Sent from the wix-users mailing list archive at Nabble.com. -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper for multiple cultures
Sorry for reviving a fairly old thread, but I'm working on localizing the MSIs inside a bundle and the following made me a bit uneasy: I use a single localized bootstrapper and separate localized msi(s). All of my UX GUI is in the mba, except for a few status and error messages in the MSI. I used to try to embed the culture transforms into a single msi. That resulted in very subtle problems, and I was told that is not supported when using a Burn bootstrapper. I would not advise going down that path. Phill, are you saying that it's impossible to create a single MSI with multiple cultures? Do you happen to still have any references to the subtle problems that you mention? We're shipping a bundle exe for our product, but in certain situations, such as deployment via GPO, our end-users must use MSIs, which means we need to localize both the bundle *and* the MSI. I would very much want to avoid having to bundle 17 almost-identical MSIs in a bundle if possible... Thanks, Soren On Tue, Jan 13, 2015 at 7:01 AM, Phill Hogland phogl...@rimage.com wrote: Here are a couple of quick links (and there are many more on this topic): When this link was posted I was using WixStdBA http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experiences-making-a-multi-language-bundle-td7208949.html#a7587770 Here I use an mba, but the same concepts can be done in WixStdBa http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-td7596896.html#a7598508 I use a single localized bootstrapper and separate localized msi(s). All of my UX GUI is in the mba, except for a few status and error messages in the MSI. I used to try to embed the culture transforms into a single msi. That resulted in very subtle problems, and I was told that is not supported when using a Burn bootstrapper. I would not advise going down that path. Others have discussed in this forum how to ship a single localized bootstrapper and a single msi with multiple transforms applied by the bootstrapper. Each culture specific MSI must be built to create the transforms. Typically a single 'package' project is used and you set the cultures as documented in chm which results in MSBuild batch building the different culture specific outputs. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-for-multiple-cultures-tp7598840p7598843.html Sent from the wix-users mailing list archive at Nabble.com. -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrapper Exe Display Security Warning Dialog (Unknown Publisher)
Hello All, When I run bootstrapper exe it display “Open File – Security Warning” dialog with unknown publisher. Can any one help me, “how to change publisher and remove security warning dialog when execute Bootstrapper exe?” ? Thanks, Mrugesh -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper Exe Display Security Warning Dialog (Unknown Publisher)
Sign the bundle? http://wixtoolset.org/documentation/manual/v3/overview/insignia.html _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Mrugesh Patel [mailto:mrugesh.pa...@tatvasoft.com] Sent: Tuesday, April 21, 2015 9:53 PM To: General discussion about the WiX toolset. Subject: [WiX-users] Bootstrapper Exe Display Security Warning Dialog (Unknown Publisher) Hello All, When I run bootstrapper exe it display “Open File – Security Warning” dialog with unknown publisher. Can any one help me, “how to change publisher and remove security warning dialog when execute Bootstrapper exe?” ? Thanks, Mrugesh -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper application problem @Win x86
Hi guys, am I the only one, who's struggling with this behavior? Any ideas, suggestions would be welcome Many Thanks, Marco Von: Marco Tangl Gesendet: Donnerstag, 09. April 2015 16:56 An: wix-users@lists.sourceforge.net Betreff: Bootstrapper application problem @Win x86 Hi guys, I hope someone could help me out of my misery. I did a bundle installer (WixStandardBootstrapperApplication.RtfLicense ), featuring various msi files. Everything works fine for x64 systems. When executing on x86 systems, during installation a second installation dialog in Modify Mode pops up. I know, that it is started because of a msi package which installs a filter driver within the bundle. Therefore it starts/stops a service by using A custom action with setupapi.dll,InstallHinfSection DefaultInstall 128 [#dwencdrv.inf]. Unfortunately that's all I know ... I don't know why it only happens on x86 and not on x64 systems .. root cause?? Full of expectations and with best regards, Marco -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrapper application problem @Win x86
Hi guys, I hope someone could help me out of my misery. I did a bundle installer (WixStandardBootstrapperApplication.RtfLicense ), featuring various msi files. Everything works fine for x64 systems. When executing on x86 systems, during installation a second installation dialog in Modify Mode pops up. I know, that it is started because of a msi package which installs a filter driver within the bundle. Therefore it starts/stops a service by using A custom action with setupapi.dll,InstallHinfSection DefaultInstall 128 [#dwencdrv.inf]. Unfortunately that's all I know ... I don't know why it only happens on x86 and not on x64 systems .. root cause?? Full of expectations and with best regards, Marco -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper custom background
Thank you very much! It gave me what I needed. All the best, Balazs Kurtan -Original Message- From: Nir Bar [mailto:nir@panel-sw.com] Sent: Friday, March 27, 2015 9:09 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bootstrapper custom background You should author a theme using thmutil http://wixtoolset.org/documentation/manual/v3/xsd/thmutil/ The Theme http://wixtoolset.org/documentation/manual/v3/xsd/thmutil/theme.html 's @ImageFile attribute specifies a background image. - Nir Bar Freelance Developer Mail: nir@panel-sw.com Web: www.panel-sw.com - C++ On Windows, Linux and Embedded Platforms - WiX InstallShield -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-c ustom-background-tp7599737p7599749.html Sent from the wix-users mailing list archive at Nabble.com. -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrapper custom background
Dear Wix Users! I would like to realize a bootstrapper installer, with a custom background image. The installer, and the chain is working perfectly. However I couldnt figure it out how to use a background on which the other control objects are visualized. Is it possible to do? If yes, how? If not, is it possible to have no UI for the bootstrapper and only show the embedded msi installers user interface? With quietly installing the other packages. Could you suggest a proper way to realize such layout? Thank you in advance! Best regards, Balázs Kurtán -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper custom background
You should author a theme using thmutil http://wixtoolset.org/documentation/manual/v3/xsd/thmutil/ The Theme http://wixtoolset.org/documentation/manual/v3/xsd/thmutil/theme.html 's @ImageFile attribute specifies a background image. - Nir Bar Freelance Developer Mail: nir@panel-sw.com Web: www.panel-sw.com - C++ On Windows, Linux and Embedded Platforms - WiX InstallShield -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-custom-background-tp7599737p7599749.html Sent from the wix-users mailing list archive at Nabble.com. -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper Show conditional message box or String without cancel Installation
Custom BA could. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: RonnyS [mailto:ronnys.cod...@gmail.com] Sent: Thursday, March 5, 2015 2:47 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapper Show conditional message box or String without cancel Installation Hello, is there some way to show in the boostrapper a message box or string in UI due to some condition but *continue* installation? At the moment i have this: bal:Condition Message=#(loc.FailtureVersionNTisXP) VersionNT v5.1 /bal:Condition but it terminates the Installation if an user have Windows XP. I need to show a MessageBox at start the Bootstrapper if user has WinXP or a conditional String in HyperlinkTheme.xml without cancel the installation. Page Name=Install Text X=11 Y=121 Width=-11 Height=71 FontId=3 #(loc.InstallWelcomeMsg)/Text I found a sample on this page from Jakob S. http://stackoverflow.com/questions/8239188/wix-show-conditional-message-box-without-cancel . But the sample works at me only in the msi not in the bootstrapper. I hope someone has an idea. -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrapper Show conditional message box or String without cancel Installation
Hello, is there some way to show in the boostrapper a message box or string in UI due to some condition but *continue* installation? At the moment i have this: bal:Condition Message=#(loc.FailtureVersionNTisXP) VersionNT v5.1 /bal:Condition but it terminates the Installation if an user have Windows XP. I need to show a MessageBox at start the Bootstrapper if user has WinXP or a conditional String in HyperlinkTheme.xml without cancel the installation. Page Name=Install Text X=11 Y=121 Width=-11 Height=71 FontId=3 #(loc.InstallWelcomeMsg)/Text I found a sample on this page from Jakob S. http://stackoverflow.com/questions/8239188/wix-show-conditional-message-box-without-cancel . But the sample works at me only in the msi not in the bootstrapper. I hope someone has an idea. -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper/Bundle - how to disable (or reduce) logging
Not supported today. Non-verbose log files are generally useless. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Jeff Fisher [mailto:radi...@msn.com] Sent: Thursday, February 19, 2015 10:36 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapper/Bundle - how to disable (or reduce) logging Hi, sorry if this is obvious, but how can I switch the logging to something other than verbose? I've tried adding Log Disable=yes / to my Bundle, but this doesn't seem to have any impact. The verbose log files are hundreds of MB in size, so this isn't really something that I can ship. Thanks Jeff. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrapper/Bundle - how to disable (or reduce) logging
Hi, sorry if this is obvious, but how can I switch the logging to something other than verbose? I've tried adding Log Disable=yes / to my Bundle, but this doesn't seem to have any impact. The verbose log files are hundreds of MB in size, so this isn't really something that I can ship. Thanks Jeff. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper for multiple cultures
It worked after I changed my Date Format settings to Japanese :). Before I was only changing the Keyboard and Location settings, but Date Format was still English, so it was still coming up in English. Thanks a lot for the help! Regards Vikas -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-for-multiple-cultures-tp7598840p7598899.html Sent from the wix-users mailing list archive at Nabble.com. -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper for multiple cultures
Hi Phill,
I created directories for Japanese them and placed the wxl file and license
files and was able to get a Japanese bootstrapper installer when I ran with
the option -lang 1041. I was able to get the same output even by using a
single msi created in English as my Internal UI is set to No. But how can I
just click on the Installer and make it run with Japanese culture? When I
changed my keyboard settings to JP, it did not help either. Can you tell me
what I am doing wrong here?
Please refer to my code below.
?xml version='1.0' encoding='windows-1252'?
Wix xmlns='http://schemas.microsoft.com/wix/2006/wi'
xmlns:bal=http://schemas.microsoft.com/wix/BalExtension;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;
Bundle Name=AppBundleName Version=$(var.ProductVersion)
Manufacturer=ManufacturerName
UpgradeCode={2D04966D-0EF6-492F-9A23-F456CCE6F6BE}
Copyright=Copyright (c) 2014 - 2015 by Sling Media, Inc.
IconSourceFile=.\Logo_128x128.ico
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.RtfLicense
bal:WixStandardBootstrapperApplication
LicenseFile=.\theme\EULA.rtf
ThemeFile=.\MyTheme.xml
ShowVersion=yes
LogoFile=theme\Logo.png
LocalizationFile=theme\RtfTheme.wxl
/
Payload SourceFile=theme\Logo.png/
Payload SourceFile=player-logo-pc.png/
Payload Id=theme_ja_jp Compressed=yes Name=1041\thm.wxl
SourceFile=theme\1041 \RtfTheme.wxl/
Payload Id=license_ja_jp Compressed=yes Name=1041\license.rtf
SourceFile=theme\1041\license.rtf/
/BootstrapperApplicationRef
WixVariable Id=chkSPD Value=![CDATA[chkSPD]] /
util:RegistrySearch Root='HKCU' Key='SOFTWARE\CompName\ProdName'
Id=SPDCheckInstalled Variable=ProductName Result=exists /
Variable Name=InstallFolder Type=string
Value=[ProgramFilesFolder]ProductName/
Variable Name=LaunchTarget Value=[InstallFolder]\Application.exe/
Chain
MsiPackage Id=MainPackage SourceFile=bin\Release\AppInstaller.msi
Vital=yes DisplayInternalUI=no
MsiProperty Name=INSTALLDIR Value=[InstallFolder]/
/MsiPackage
/Chain
/Bundle
Thanks and Regards
Vikas
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-for-multiple-cultures-tp7598840p7598871.html
Sent from the wix-users mailing list archive at Nabble.com.
--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper for multiple cultures
It has been over a year since I tackled that issue with the help of folks here. This thread http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experiences-making-a-multi-language-bundle-td7208949.html#a7587949 is on the same issue. I know we got it to automatically detect the language, after I upgraded from wix 3.7 (which had a bug). Also you will notice in that thread that part of my issue was that I did not understand how the changes in the behaviour of Win 8 (in contrast to Win 7) was affecting the issue. Make sure that you define you WixLocalization element to specify the correct Culture, Language, and Codepage. Then add additional String elements which you can then use to signal your BA or use in MsiPackage conditions. This example is from one of my localized MSI projects, so you would not need the SummaryCodepage in a Bundle project. But you might have something like: String Id=msiTransfrom1041.mst/String ?xml version=1.0 encoding=utf-8? WixLocalization Culture=ja-JP Codepage=932 Language=1041 xmlns=http://schemas.microsoft.com/wix/2006/localization; String Id=LCID1041/String String Id=Codepage932/String String Id=SummaryCodepage932/String String Id=DownVersionErrorMsg[ProductName] の新しいバージョンがすでにインストールされています。/String /WixLocalization Make sure you set the culture property in VS (or on the command line of light) for the bundle project. You can do it in the IDE as described here http://wixtoolset.org/documentation/manual/v3/howtos/ui_and_localization/specifying_cultures_to_build.html , or just edit the wixproj file to include something like: Culturesen-US;de-DE;es-ES;fr-FR;it-IT;ja-JP;zh-CN/Cultures The WixStdBA will detect what the SystemLanguage is set too (IIRC), so on Windows 8 I always get tripped up on how to configure that, but I then get it worked out. Use ProcessMon http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx and watch where you BA tries to load the lcid named resources. When you do not provide the -lcid switch you will see that it will try to find a resource and if it cannot find the resource it will drop back to the default (which is what is sounds like it is doing for you.) Just guessing. I did not see anything wrong with what you posted, based on my vague memory, but I don't know how your wxl is defined. I also defined a wxl for my default culture (en-US) as I needed to use the string that I created in that wxl file to control the MsiPackage conditions for the en-US package. I switched to creating a mba long ago so now I detect the culture in my BA based on the cuture of the thread and use that info to select which culture specific MSI to installed. So sorry that I do not remember all the details of using the WixStdBA. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-for-multiple-cultures-tp7598840p7598872.html Sent from the wix-users mailing list archive at Nabble.com. -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper for multiple cultures
Here are a couple of quick links (and there are many more on this topic): When this link was posted I was using WixStdBA http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experiences-making-a-multi-language-bundle-td7208949.html#a7587770 Here I use an mba, but the same concepts can be done in WixStdBa http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-td7596896.html#a7598508 I use a single localized bootstrapper and separate localized msi(s). All of my UX GUI is in the mba, except for a few status and error messages in the MSI. I used to try to embed the culture transforms into a single msi. That resulted in very subtle problems, and I was told that is not supported when using a Burn bootstrapper. I would not advise going down that path. Others have discussed in this forum how to ship a single localized bootstrapper and a single msi with multiple transforms applied by the bootstrapper. Each culture specific MSI must be built to create the transforms. Typically a single 'package' project is used and you set the cultures as documented in chm which results in MSBuild batch building the different culture specific outputs. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-for-multiple-cultures-tp7598840p7598843.html Sent from the wix-users mailing list archive at Nabble.com. -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper doesn't run MSI package
You need to evaluate the verbose log (or past to a post relevant parts for others to help). It is typically in your %temp% folder, with obvious name based on your product name. There will be a log for the bootstrapper which contains the 'plan' and for each msi, if launched. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-doesn-t-run-MSI-package-tp7598826p7598827.html Sent from the wix-users mailing list archive at Nabble.com. -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. vanity: www.gigenet.com ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper doesn't run MSI package
[1D28:0570][2015-01-12T15:19:10]i101: Detected package: Application, state: Obsolete, cached: None [1D28:0570][2015-01-12T15:19:12]i201: Planned package: Application, state: Obsolete, default requested: None, ba requested: None, execute: None, rollback: None, cache: No, uncache: No, dependency: None When I have seen state: Obsolete the package in the setup is older (down version) than the package already on the system. For me this has pointed to to possible problems. 1) Clean up my test process and always start with a clean VM when initially testing a msi. 2) Make sure my build process always increments something in the first three parts of the msi version (as well as the Product Code) to qualify as a MSI Major Upgrade. I don't claim to have a lot of experience with this so maybe someone else can clarify. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-doesn-t-run-MSI-package-tp7598826p7598830.html Sent from the wix-users mailing list archive at Nabble.com. -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. vanity: www.gigenet.com ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrapper for multiple cultures
Hi, Please excuse me if this has already been discussed before. I am trying to implement a bootstrapper for multiple cultures. After searching around, I found some help but with that, I am only able to build 2 separate MSIs for 2 cultures and I now have to build 2 separate bootstrapper exe packages, one for each culture. I need some help regarding this: - Once we have 2 MSIs, for say English and Japanese, how do I create Multiple bootstrappers for the same where the WixStandardBootstrapperApplication application strings also need to be localized? Please provide some examples or links for the same. - The Ideal solution would be to create a page for language selection in the bootstrapper which will then apply the required localizations. That way, I will have only 1 MSI package with default language but since localization will be applied on the bootstrapper, the user sees the Installation in his local language. How can we achieve this in Wix? If you have any examples, can you please share them? Thanks and Regards Vikas -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-for-multiple-cultures-tp7598840.html Sent from the wix-users mailing list archive at Nabble.com. -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper and buttons...
On 02-Dec-14 16:44, Steve-Ogilvie wrote: I have modified the theme for the boostrappers I am using but I noticed on the Welcome screen hitting the enter key does not advance to the next screen is this a bug in 3.8 or as designed? Themes don't currently expose a way to set default buttons. -- sig://boB http://joyofsetup.com/ -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrapper and buttons...
I have modified the theme for the boostrappers I am using but I noticed on the Welcome screen hitting the enter key does not advance to the next screen is this a bug in 3.8 or as designed? Steve -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-and-buttons-tp7598336.html Sent from the wix-users mailing list archive at Nabble.com. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrapper runs msiexec elevated which causes my MSI CustomAction to run elevated
I've authored an MSI package that uses a CustomAction to launch an application after install completes. The package requires elevation but the CustomAction is scheduled after InstallFinalize to launch the application as the Standard User, not elevated. When installing the MSI alone using msiexec.exe, things work as expected, and my application launches correctly as the Standard User. However, we're using the WIX Standard BA bootstrapper to chain this package in a install bundle. The problem is, when this MSI package runs as part of the BA, it runs elevated, and so too does the CustomAction, which in turn launches the app elevated, which is not what we want. It seems that the BA launches msiexec.exe elevated. Is there a way to keep the BA from launching the MSI elevated? Thanks in advance, Ryan -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper runs msiexec elevated which causes my MSI CustomAction to run elevated
WixStdBA handles this without a CA via: Variable Name=LaunchTarget Value=[ProgramFilesFolder]\Blah\Blah\Application.exe/ -Original Message- From: Ryan Waller [mailto:rwal...@microsoft.com] Sent: Monday, November 03, 2014 4:32 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapper runs msiexec elevated which causes my MSI CustomAction to run elevated I've authored an MSI package that uses a CustomAction to launch an application after install completes. The package requires elevation but the CustomAction is scheduled after InstallFinalize to launch the application as the Standard User, not elevated. When installing the MSI alone using msiexec.exe, things work as expected, and my application launches correctly as the Standard User. However, we're using the WIX Standard BA bootstrapper to chain this package in a install bundle. The problem is, when this MSI package runs as part of the BA, it runs elevated, and so too does the CustomAction, which in turn launches the app elevated, which is not what we want. It seems that the BA launches msiexec.exe elevated. Is there a way to keep the BA from launching the MSI elevated? Thanks in advance, Ryan -- ___ 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] Bootstrapper runs msiexec elevated which causes my MSI CustomAction to run elevated
I've tried that but it requires the user to click a button after install completes, and they can also cancel. Neither is desirable. Can this be invoked without the button click? Ideally I would just like to have my MSI executed without elevation, just like when running msiexec.exe from the command line. -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Monday, November 3, 2014 2:45 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper runs msiexec elevated which causes my MSI CustomAction to run elevated WixStdBA handles this without a CA via: Variable Name=LaunchTarget Value=[ProgramFilesFolder]\Blah\Blah\Application.exe/ -Original Message- From: Ryan Waller [mailto:rwal...@microsoft.com] Sent: Monday, November 03, 2014 4:32 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapper runs msiexec elevated which causes my MSI CustomAction to run elevated I've authored an MSI package that uses a CustomAction to launch an application after install completes. The package requires elevation but the CustomAction is scheduled after InstallFinalize to launch the application as the Standard User, not elevated. When installing the MSI alone using msiexec.exe, things work as expected, and my application launches correctly as the Standard User. However, we're using the WIX Standard BA bootstrapper to chain this package in a install bundle. The problem is, when this MSI package runs as part of the BA, it runs elevated, and so too does the CustomAction, which in turn launches the app elevated, which is not what we want. It seems that the BA launches msiexec.exe elevated. Is there a way to keep the BA from launching the MSI elevated? Thanks in advance, Ryan -- ___ 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] Bootstrapper runs msiexec elevated which causes my MSI CustomAction to run elevated
If you can find a Way to set LaunchTarget to True without requiring user input, you can achieve your Behavior Quoting Ryan Waller rwal...@microsoft.com: I've tried that but it requires the user to click a button after install completes, and they can also cancel. Neither is desirable. Can this be invoked without the button click? Ideally I would just like to have my MSI executed without elevation, just like when running msiexec.exe from the command line. -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Monday, November 3, 2014 2:45 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper runs msiexec elevated which causes my MSI CustomAction to run elevated WixStdBA handles this without a CA via: Variable Name=LaunchTarget Value=[ProgramFilesFolder]\Blah\Blah\Application.exe/ -Original Message- From: Ryan Waller [mailto:rwal...@microsoft.com] Sent: Monday, November 03, 2014 4:32 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapper runs msiexec elevated which causes my MSI CustomAction to run elevated I've authored an MSI package that uses a CustomAction to launch an application after install completes. The package requires elevation but the CustomAction is scheduled after InstallFinalize to launch the application as the Standard User, not elevated. When installing the MSI alone using msiexec.exe, things work as expected, and my application launches correctly as the Standard User. However, we're using the WIX Standard BA bootstrapper to chain this package in a install bundle. The problem is, when this MSI package runs as part of the BA, it runs elevated, and so too does the CustomAction, which in turn launches the app elevated, which is not what we want. It seems that the BA launches msiexec.exe elevated. Is there a way to keep the BA from launching the MSI elevated? Thanks in advance, Ryan -- ___ 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] Bootstrapper runs msiexec elevated which causes my MSI CustomAction to run elevated
You could make your MSI per-user or create your own BA to show the UI as you desire. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Ryan Waller [mailto:rwal...@microsoft.com] Sent: Monday, November 3, 2014 3:01 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper runs msiexec elevated which causes my MSI CustomAction to run elevated I've tried that but it requires the user to click a button after install completes, and they can also cancel. Neither is desirable. Can this be invoked without the button click? Ideally I would just like to have my MSI executed without elevation, just like when running msiexec.exe from the command line. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrapper themes
Hi, I am looking for a good reference (or bag of tricks) for working with the WiX bootstrapper (the documentation is not very extensive on this subject). Specifically, I would like to find information on creating custom themes. So far I have managed to find very little, but I suppose there must be some source of information available apart from looking at the source code? If anyone happen to have intimate knowledge about how to make a Billboard work in a bundle custom ui for example, I would be very happy to hear about that. Thanks in advance, Pop Qvarnström -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper Custom UI, Checkbox to customize install
That is not currently supported. That may be supported in Wix 3.9 depending on how the RTM looks. -- John Merryweather Cooper Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |jocoo...@jackhenry.com -Original Message- From: newuser2014 [mailto:wamplersovere...@gmail.com] Sent: Wednesday, October 1, 2014 1:44 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bootstrapper Custom UI, Checkbox to customize install Thank you for the advice. Now I can use checkboxes to customize my installation. However, when I tried to put the same checkbox on the modify screen for selection during uninstallation, they don't seem to work. My code looks like the following, selective installation works, but uninstallation does not. Any ideas? Thank you very much for your help! Page Name=Modify Text X=11 Y=80 Width=-11 Height=30 FontId=2 DisablePrefix=yes#(loc.ModifyHeader)/Text Checkbox Name=Component 1 Height=30 Width=200 X=-250 Y=-180 FontId=0Component 1/Checkbox Checkbox Name=Component 2 Height=30 Width=200 X=-250 Y=-150 FontId=0Component 2/Checkbox And I have the following in Bundle.wxs: Variable Name=Comp1 Value=0/ Variable Name=Comp2 Value=0/ Chain PackageGroupRef Id=NetFx40Redist/ MsiPackage DisplayInternalUI=yes SourceFile=comp1.msi InstallCondition= Comp1=1/ MsiPackage DisplayInternalUI=yes SourceFile=comp2.msi InstallCondition=Comp2=1/ -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-Custom-UI-Checkbox-to-customize-install-tp7596905p7597085.html Sent from the wix-users mailing list archive at Nabble.com. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ 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. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] BootStrapper(Burn) Extracts all files to ProgramData folder
Hi ,
I created a BootStrapper using WiX 3.8. When i trigger the Setup.exe and i
looked into the log file, i found that all the core files(including .msi,
data1.cab) will get extracted to the folder C:\Program Data\Package
Cache\{ProductId} . Then i tried suppressing CustomAction through Orca i
could able to do it. So, My question here is where is the security for the
product files which are sensitive files. I worked on InstallShield before
and found the same kind of issue with SupportFiles (SUPPORTDIR). But in
InstallShield only the files that are kept in the SupportFiles will get
extracted, not all.
Could anyone share your thoughts on the same.? Can we stop Burn from
extracting all files into ProgramData?
Regards,
Sampat
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/BootStrapper-Burn-Extracts-all-files-to-ProgramData-folder-tp7597082.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper Custom UI, Checkbox to customize install
Thank you for the advice. Now I can use checkboxes to customize my installation. However, when I tried to put the same checkbox on the modify screen for selection during uninstallation, they don't seem to work. My code looks like the following, selective installation works, but uninstallation does not. Any ideas? Thank you very much for your help! Page Name=Modify Text X=11 Y=80 Width=-11 Height=30 FontId=2 DisablePrefix=yes#(loc.ModifyHeader)/Text Checkbox Name=Component 1 Height=30 Width=200 X=-250 Y=-180 FontId=0Component 1/Checkbox Checkbox Name=Component 2 Height=30 Width=200 X=-250 Y=-150 FontId=0Component 2/Checkbox And I have the following in Bundle.wxs: Variable Name=Comp1 Value=0/ Variable Name=Comp2 Value=0/ Chain PackageGroupRef Id=NetFx40Redist/ MsiPackage DisplayInternalUI=yes SourceFile=comp1.msi InstallCondition= Comp1=1/ MsiPackage DisplayInternalUI=yes SourceFile=comp2.msi InstallCondition=Comp2=1/ -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-Custom-UI-Checkbox-to-customize-install-tp7596905p7597085.html Sent from the wix-users mailing list archive at Nabble.com. -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper Custom UI, Checkbox to customize install
I modified the following in HyperLinkTheme.xml: Page Name=Options Text X=11 Y=80 Width=-11 Height=30 FontId=2 DisablePrefix=yes#(loc.OptionsHeader)/Text Text X=11 Y=121 Width=-11 Height=17 FontId=3 DisablePrefix=yes#(loc.OptionsLocationLabel)/Text Editbox Name=FolderEditbox X=11 Y=143 Width=-91 Height=21 TabStop=yes FontId=3 FileSystemAutoComplete=yes / Button Name=BrowseButton X=-11 Y=142 Width=75 Height=23 TabStop=yes FontId=3#(loc.OptionsBrowseButton)/Button !-- this line right here -- Checkbox Name=LocalDbCheckbox X=11 Y=166 Width=260 Height=17 TabStop=yes FontId=3Install SQL Express LocalDb 2012/Checkbox Button Name=OptionsOkButton X=-91 Y=-11 Width=75 Height=23 TabStop=yes FontId=0#(loc.OptionsOkButton)/Button Button Name=OptionsCancelButton X=-11 Y=-11 Width=75 Height=23 TabStop=yes FontId=0#(loc.OptionsCancelButton)/Button /Page That theme file is referenced here in the Bundle.wxs: BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.HyperlinkLicense bal:WixStandardBootstrapperApplication LicenseUrl= LogoFile=$(var.ProjectDir)Logo\jX.png ThemeFile=$(var.ProjectDir)Resources\HyperlinkTheme.xml / /BootstrapperApplicationRef The LocalDBCheckbox Burn Variable is referenced here in bundle.wxs to pass it to the MSI: MsiProperty Name=USE_LOCALDB Value=[LocalDbCheckbox] / And here in PackageGroup.wxs to condition the installation of LocalDb: Fragment PackageGroup Id=SqlLocalDB32 MsiPackage Id=SqlLocalDB32 InstallCondition=NOT VersionNT64 AND VersionNT = v6.1 AND LocalDbCheckbox SourceFile=$(var.ProjectDir)Layout\x86\SqlLocalDB.msi Vital=yes MsiProperty Name=IACCEPTSQLLOCALDBLICENSETERMS Value=YES/ /MsiPackage /PackageGroup /Fragment (there's a similar block for x64, but it doesn't illuminate the discussion any more). -- John Merryweather Cooper Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |jocoo...@jackhenry.com -Original Message- From: newuser2014 [mailto:wamplersovere...@gmail.com] Sent: Thursday, September 18, 2014 5:42 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bootstrapper Custom UI, Checkbox to customize install Yes, I am running wix 3.8. Yep, a couple of checkboxes are all I need. Is there an example of how this is done? Thanks! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-Custom-UI-Checkbox-to-customize-install-tp7596905p7596907.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ 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. -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrapper Modify Setup
Hi, I've modified my Bootstrapper theme in order to support installing multiple msi during the installation process based on user selection as follows: Chain PackageGroupRef Id=NetFx40Redist/ PackageGroupRef Id=CrystalReport/ MsiPackage DisplayInternalUI=yes SourceFile=..\bin\$(var.Configuration)\en-us\App1.msi InstallCondition=App1=1/ MsiPackage DisplayInternalUI=yes SourceFile=..\bin\$(var.Configuration)\en-us\App2.msi InstallCondition=App2=1/ MsiPackage DisplayInternalUI=yes SourceFile=..\bin\$(var.Configuration)\en-us\App3.msi InstallCondition=App3=1/ MsiPackage DisplayInternalUI=yes SourceFile=..\bin\$(var.Configuration)\en-us\App4.msi InstallCondition=App4=1/ /Chain When the user double clicks on the bootstrapper msi, is there a way for me to detect which msi has been installed and let the user pick which ones to uninstall? Would the uninstall process follow the steps in the Chain element? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-Modify-Setup-tp7596927.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper Modify Setup
The Chain is evaluated from top to bottom when doing an 'Install', and in reverse order (from bottom to top) when doing an uninstall. Typically I just let Burn manage these details. Yes you can create a custom BA (or with WixStdBA use a BAFunctions.dll) and override the various Plan (and other event handlers). I found this blog to be helpful (whether I planed to do an mba or not, in addition to the info in your chm). http://www.wrightfully.com/part-1-of-writing-your-own-net-based-installer-with-wix-overview/ Also your bundle.exe creates a log, typically in your %temp% folder. In looking at that file, particularly with MSI verbose logging enabled, you will see the information about what has been planned, why, and the sequence. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-Modify-Setup-tp7596927p7596930.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrapper Crystal Prerequisite Install
Hi, I have to verify and install Crystal as a prerequisite of my install in the Bootstrapper. I have implemented the following, but it doesn't seem to work. Did I make a mistake somewhere? Thank you very much in advance for your help! Fragment util:RegistrySearch Root=HKLM Key=SOFTWARE\Wow6432Node\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Crystal Reports Value=CRRuntime32Version Variable=CrystalRuntime Result=exists Win64=yes / util:RegistrySearch Root=HKLM Key=SOFTWARE\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Crystal Reports Value=CRRuntime32Version Variable=CrystalRuntimeXP Result=exists / PackageGroup Id=CrystalReport MsiPackage After=NetFx40Redist DisplayName=Crystal Report Cache=yes Compressed=yes Permanent=yes Vital=yes SourceFile=.\CRRuntime_32bit_13_0_10.msi InstallCondition=CrystalRuntimeXP AND (NOT VersionNT64 OR CrystalRuntime) / /PackageGroup /Fragment -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-Crystal-Prerequisite-Install-tp7596900.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper Crystal Prerequisite Install
Any time I see Wow6432Node the first thing I think is you're doing it wrong. Since this is in a bundle, and the bundle is a 32 bit process, one would think you could do: util:RegistrySearch Root=HKLM Key=SOFTWARE\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Crystal Reports Value=CRRuntime32Version Variable=CrystalRuntime32 Result=exists / To detect the 32 bit components being installed. If you have a 32 and 64 bit MSI in your bundle, then you may need the second check (guessing at the Value name): util:RegistrySearch Root=HKLM Key=SOFTWARE\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Crystal Reports Value=CRRuntime64Version Variable=CrystalRuntime64 Result=exists Win64=yes / -Original Message- From: newuser2014 [mailto:wamplersovere...@gmail.com] Sent: Thursday, September 18, 2014 2:15 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapper Crystal Prerequisite Install Hi, I have to verify and install Crystal as a prerequisite of my install in the Bootstrapper. I have implemented the following, but it doesn't seem to work. Did I make a mistake somewhere? Thank you very much in advance for your help! Fragment util:RegistrySearch Root=HKLM Key=SOFTWARE\Wow6432Node\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Crystal Reports Value=CRRuntime32Version Variable=CrystalRuntime Result=exists Win64=yes / util:RegistrySearch Root=HKLM Key=SOFTWARE\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Crystal Reports Value=CRRuntime32Version Variable=CrystalRuntimeXP Result=exists / PackageGroup Id=CrystalReport MsiPackage After=NetFx40Redist DisplayName=Crystal Report Cache=yes Compressed=yes Permanent=yes Vital=yes SourceFile=.\CRRuntime_32bit_13_0_10.msi InstallCondition=CrystalRuntimeXP AND (NOT VersionNT64 OR CrystalRuntime) / /PackageGroup /Fragment -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-Crystal-Prerequisite-Install-tp7596900.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper Crystal Prerequisite Install
The point of Win64 (or not) is to say which registry view you want. Win64=no and defining the search in the normal way will automatically use WoW6432 so you don't need to specify it. That may or may not fix the problem, but IMO it's the right way to do these kinds of search. Just say what the item is and let Win64=yes/no do the redirection as appropriate. --- Phil Wilson On Thu, Sep 18, 2014 at 12:25 PM, Hoover, Jacob jacob.hoo...@greenheck.com wrote: Any time I see Wow6432Node the first thing I think is you're doing it wrong. Since this is in a bundle, and the bundle is a 32 bit process, one would think you could do: util:RegistrySearch Root=HKLM Key=SOFTWARE\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Crystal Reports Value=CRRuntime32Version Variable=CrystalRuntime32 Result=exists / To detect the 32 bit components being installed. If you have a 32 and 64 bit MSI in your bundle, then you may need the second check (guessing at the Value name): util:RegistrySearch Root=HKLM Key=SOFTWARE\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Crystal Reports Value=CRRuntime64Version Variable=CrystalRuntime64 Result=exists Win64=yes / -Original Message- From: newuser2014 [mailto:wamplersovere...@gmail.com] Sent: Thursday, September 18, 2014 2:15 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapper Crystal Prerequisite Install Hi, I have to verify and install Crystal as a prerequisite of my install in the Bootstrapper. I have implemented the following, but it doesn't seem to work. Did I make a mistake somewhere? Thank you very much in advance for your help! Fragment util:RegistrySearch Root=HKLM Key=SOFTWARE\Wow6432Node\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Crystal Reports Value=CRRuntime32Version Variable=CrystalRuntime Result=exists Win64=yes / util:RegistrySearch Root=HKLM Key=SOFTWARE\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Crystal Reports Value=CRRuntime32Version Variable=CrystalRuntimeXP Result=exists / PackageGroup Id=CrystalReport MsiPackage After=NetFx40Redist DisplayName=Crystal Report Cache=yes Compressed=yes Permanent=yes Vital=yes SourceFile=.\CRRuntime_32bit_13_0_10.msi InstallCondition=CrystalRuntimeXP AND (NOT VersionNT64 OR CrystalRuntime) / /PackageGroup /Fragment -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-Crystal-Prerequisite-Install-tp7596900.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper Crystal Prerequisite Install
Does the InstallCondition--CrystalRuntimeXP AND (NOT VersionNT64 OR CrystalRuntime)--look correct? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-Crystal-Prerequisite-Install-tp7596900p7596903.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper Crystal Prerequisite Install
Depends, Does your app support both a 32 bit and 64 bit variant? -Original Message- From: newuser2014 [mailto:wamplersovere...@gmail.com] Sent: Thursday, September 18, 2014 3:01 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bootstrapper Crystal Prerequisite Install Does the InstallCondition--CrystalRuntimeXP AND (NOT VersionNT64 OR CrystalRuntime)--look correct? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-Crystal-Prerequisite-Install-tp7596900p7596903.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrapper Custom UI, Checkbox to customize install
Hi, Is there any where to add a custom dialog to have a few checkboxes for the user to select. And base on the user selections in the checkboxes the Bootstrapper will install the user selected msi. Thank you very much for your help! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-Custom-UI-Checkbox-to-customize-install-tp7596905.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper Custom UI, Checkbox to customize install
Presuming you mean the standard bootstrapper and Wix 3.8 or later, you can modify the theme to add checkboxes and use these to condition packages. For a custom experience, you'll need a managed or unmanaged code custom bootstrapper application. -- John Merryweather Cooper Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |jocoo...@jackhenry.com -Original Message- From: newuser2014 [mailto:wamplersovere...@gmail.com] Sent: Thursday, September 18, 2014 4:39 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapper Custom UI, Checkbox to customize install Hi, Is there any where to add a custom dialog to have a few checkboxes for the user to select. And base on the user selections in the checkboxes the Bootstrapper will install the user selected msi. Thank you very much for your help! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-Custom-UI-Checkbox-to-customize-install-tp7596905.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ 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. -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper Custom UI, Checkbox to customize install
Yes, I am running wix 3.8. Yep, a couple of checkboxes are all I need. Is there an example of how this is done? Thanks! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-Custom-UI-Checkbox-to-customize-install-tp7596905p7596907.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper not upgrading MSI [P]
Classification: Public That is not considered an upgrade MSI can only read the first 3 digits 6.0.0 in order to upgrade you must change one of the first three digits i.e. 6.0.1 http://msdn.microsoft.com/en-us/library/aa370579(v=vs.85).aspx Steve -Original Message- From: Nick downey [mailto:fluffaluffagu...@gmail.com] Sent: July-07-14 11:17 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI The original version was 6.0.0.0 and the new one was 6.0.0.1 Sent with AquaMail for Android http://www.aqua-mail.com On July 7, 2014 11:13:07 AM John Cooper jocoo...@jackhenry.com wrote: Well, the log indicates that Burn is uninstalling. What are the version numbers for the initial and upgrade installs? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:00 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapper not upgrading MSI I have a Wix Bootstrapper which conditionally installs various components, which are defaulted to not install unless a command line parameter is sent. This works fine on the initial install, but when I attempt to perform an upgrade, the command line parameters do not seem to be being read. It also does not upgrade the MSI being run by the bootstrapper, just remove the files it created. The bootstrapper will display Previous version for the progress text and then finish. Here is the log for the Bootstrapper : https://drive.google.com/file/d/0B4QDf83juiMDRFlnV2p0ZEVRYlE/edit?usp= sharing Here is the log for the msi being run: https://drive.google.com/file/d/0B4QDf83juiMDUU1tdG9EdkUxMUk/edit?usp= sharing -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ 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. -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ 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-08-14 2:19:54 PM. The above classification labels were added to the message by TITUS Message Classification. For more information visit www.titus.com. -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrapper not upgrading MSI
I have a Wix Bootstrapper which conditionally installs various components, which are defaulted to not install unless a command line parameter is sent. This works fine on the initial install, but when I attempt to perform an upgrade, the command line parameters do not seem to be being read. It also does not upgrade the MSI being run by the bootstrapper, just remove the files it created. The bootstrapper will display Previous version for the progress text and then finish. Here is the log for the Bootstrapper : https://drive.google.com/file/d/0B4QDf83juiMDRFlnV2p0ZEVRYlE/edit?usp=sharing Here is the log for the msi being run: https://drive.google.com/file/d/0B4QDf83juiMDUU1tdG9EdkUxMUk/edit?usp=sharing -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper not upgrading MSI
Well, the log indicates that Burn is uninstalling. What are the version numbers for the initial and upgrade installs? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:00 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapper not upgrading MSI I have a Wix Bootstrapper which conditionally installs various components, which are defaulted to not install unless a command line parameter is sent. This works fine on the initial install, but when I attempt to perform an upgrade, the command line parameters do not seem to be being read. It also does not upgrade the MSI being run by the bootstrapper, just remove the files it created. The bootstrapper will display Previous version for the progress text and then finish. Here is the log for the Bootstrapper : https://drive.google.com/file/d/0B4QDf83juiMDRFlnV2p0ZEVRYlE/edit?usp=sharing Here is the log for the msi being run: https://drive.google.com/file/d/0B4QDf83juiMDUU1tdG9EdkUxMUk/edit?usp=sharing -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ 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. -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper not upgrading MSI
The original version was 6.0.0.0 and the new one was 6.0.0.1 Sent with AquaMail for Android http://www.aqua-mail.com On July 7, 2014 11:13:07 AM John Cooper jocoo...@jackhenry.com wrote: Well, the log indicates that Burn is uninstalling. What are the version numbers for the initial and upgrade installs? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:00 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapper not upgrading MSI I have a Wix Bootstrapper which conditionally installs various components, which are defaulted to not install unless a command line parameter is sent. This works fine on the initial install, but when I attempt to perform an upgrade, the command line parameters do not seem to be being read. It also does not upgrade the MSI being run by the bootstrapper, just remove the files it created. The bootstrapper will display Previous version for the progress text and then finish. Here is the log for the Bootstrapper : https://drive.google.com/file/d/0B4QDf83juiMDRFlnV2p0ZEVRYlE/edit?usp=sharing Here is the log for the msi being run: https://drive.google.com/file/d/0B4QDf83juiMDUU1tdG9EdkUxMUk/edit?usp=sharing -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ 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. -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper not upgrading MSI
The fourth quad is ignored, which means the versions are effectively the same generating the behavior you're experiencing. Only the first three quads are considered by the installer service. So, 6.0.0.0 and 6.0.1.0 would have worked but 6.0.0.0 and 6.0.0.1 never will. -- 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: Nick downey [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:17 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI The original version was 6.0.0.0 and the new one was 6.0.0.1 Sent with AquaMail for Android http://www.aqua-mail.com On July 7, 2014 11:13:07 AM John Cooper jocoo...@jackhenry.com wrote: Well, the log indicates that Burn is uninstalling. What are the version numbers for the initial and upgrade installs? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:00 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapper not upgrading MSI I have a Wix Bootstrapper which conditionally installs various components, which are defaulted to not install unless a command line parameter is sent. This works fine on the initial install, but when I attempt to perform an upgrade, the command line parameters do not seem to be being read. It also does not upgrade the MSI being run by the bootstrapper, just remove the files it created. The bootstrapper will display Previous version for the progress text and then finish. Here is the log for the Bootstrapper : https://drive.google.com/file/d/0B4QDf83juiMDRFlnV2p0ZEVRYlE/edit?usp= sharing Here is the log for the msi being run: https://drive.google.com/file/d/0B4QDf83juiMDUU1tdG9EdkUxMUk/edit?usp= sharing -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ 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. -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ 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. -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly
Re: [WiX-users] Bootstrapper not upgrading MSI
I just attempted to do this with version 6.0.1.0 from 6.0.0.0, and nothing changed. Progress text displays previous version and all files from previous install are removed, but no new files are installed. Logs are attached (The one ending in 0_compuweigh is the MSI) On Mon, Jul 7, 2014 at 11:20 AM, John Cooper jocoo...@jackhenry.com wrote: The fourth quad is ignored, which means the versions are effectively the same generating the behavior you're experiencing. Only the first three quads are considered by the installer service. So, 6.0.0.0 and 6.0.1.0 would have worked but 6.0.0.0 and 6.0.0.1 never will. -- 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: Nick downey [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:17 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI The original version was 6.0.0.0 and the new one was 6.0.0.1 Sent with AquaMail for Android http://www.aqua-mail.com On July 7, 2014 11:13:07 AM John Cooper jocoo...@jackhenry.com wrote: Well, the log indicates that Burn is uninstalling. What are the version numbers for the initial and upgrade installs? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:00 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapper not upgrading MSI I have a Wix Bootstrapper which conditionally installs various components, which are defaulted to not install unless a command line parameter is sent. This works fine on the initial install, but when I attempt to perform an upgrade, the command line parameters do not seem to be being read. It also does not upgrade the MSI being run by the bootstrapper, just remove the files it created. The bootstrapper will display Previous version for the progress text and then finish. Here is the log for the Bootstrapper : https://drive.google.com/file/d/0B4QDf83juiMDRFlnV2p0ZEVRYlE/edit?usp= sharing Here is the log for the msi being run: https://drive.google.com/file/d/0B4QDf83juiMDUU1tdG9EdkUxMUk/edit?usp= sharing -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ 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. -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ 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
Re: [WiX-users] Bootstrapper not upgrading MSI
Same ProductCode or a different ProductCode for each installer? You can find the ProductCode with Orca in the Property table. If they're the same, you're not setup for major upgrade. -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:46 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI I just attempted to do this with version 6.0.1.0 from 6.0.0.0, and nothing changed. Progress text displays previous version and all files from previous install are removed, but no new files are installed. Logs are attached (The one ending in 0_compuweigh is the MSI) On Mon, Jul 7, 2014 at 11:20 AM, John Cooper jocoo...@jackhenry.com wrote: The fourth quad is ignored, which means the versions are effectively the same generating the behavior you're experiencing. Only the first three quads are considered by the installer service. So, 6.0.0.0 and 6.0.1.0 would have worked but 6.0.0.0 and 6.0.0.1 never will. -- 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: Nick downey [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:17 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI The original version was 6.0.0.0 and the new one was 6.0.0.1 Sent with AquaMail for Android http://www.aqua-mail.com On July 7, 2014 11:13:07 AM John Cooper jocoo...@jackhenry.com wrote: Well, the log indicates that Burn is uninstalling. What are the version numbers for the initial and upgrade installs? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:00 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapper not upgrading MSI I have a Wix Bootstrapper which conditionally installs various components, which are defaulted to not install unless a command line parameter is sent. This works fine on the initial install, but when I attempt to perform an upgrade, the command line parameters do not seem to be being read. It also does not upgrade the MSI being run by the bootstrapper, just remove the files it created. The bootstrapper will display Previous version for the progress text and then finish. Here is the log for the Bootstrapper : https://drive.google.com/file/d/0B4QDf83juiMDRFlnV2p0ZEVRYlE/edit?us p= sharing Here is the log for the msi being run: https://drive.google.com/file/d/0B4QDf83juiMDUU1tdG9EdkUxMUk/edit?us p= sharing -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ 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. -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Open source business process management suite built on Java and Eclipse Turn processes into business applications
Re: [WiX-users] Bootstrapper not upgrading MSI
Burn Bootstrappers do not have a ProductCode, do they?
The MSI Setup project has its product code set to *, and upgrades fine if
not run through the bootstrapper.
On Mon, Jul 7, 2014 at 11:52 AM, John Cooper jocoo...@jackhenry.com wrote:
Same ProductCode or a different ProductCode for each installer? You can
find the ProductCode with Orca in the Property table. If they're the same,
you're not setup for major upgrade.
--
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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com]
Sent: Monday, July 7, 2014 10:46 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Bootstrapper not upgrading MSI
I just attempted to do this with version 6.0.1.0 from 6.0.0.0, and nothing
changed. Progress text displays previous version and all files from
previous install are removed, but no new files are installed.
Logs are attached (The one ending in 0_compuweigh is the MSI)
On Mon, Jul 7, 2014 at 11:20 AM, John Cooper jocoo...@jackhenry.com
wrote:
The fourth quad is ignored, which means the versions are effectively
the same generating the behavior you're experiencing. Only the first
three
quads are considered by the installer service. So, 6.0.0.0 and 6.0.1.0
would have worked but 6.0.0.0 and 6.0.0.1 never will.
--
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: Nick downey [mailto:fluffaluffagu...@gmail.com]
Sent: Monday, July 7, 2014 10:17 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Bootstrapper not upgrading MSI
The original version was 6.0.0.0 and the new one was 6.0.0.1
Sent with AquaMail for Android
http://www.aqua-mail.com
On July 7, 2014 11:13:07 AM John Cooper jocoo...@jackhenry.com wrote:
Well, the log indicates that Burn is uninstalling. What are the
version numbers for the initial and upgrade installs?
--
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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com]
Sent: Monday, July 7, 2014 10:00 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Bootstrapper not upgrading MSI
I have a Wix Bootstrapper which conditionally installs various
components, which are defaulted to not install unless a command line
parameter is sent.
This works fine on the initial install, but when I attempt to
perform an upgrade, the command line parameters do not seem to be
being read.
It also does not upgrade the MSI being run by the bootstrapper, just
remove the files it created. The bootstrapper will display Previous
version for the progress text and then finish.
Here is the log for the Bootstrapper :
https://drive.google.com/file/d/0B4QDf83juiMDRFlnV2p0ZEVRYlE/edit?us
p=
sharing
Here is the log for the msi being run:
https://drive.google.com/file/d/0B4QDf83juiMDUU1tdG9EdkUxMUk/edit?us
p=
sharing
--
Open source business process management suite built on Java
and Eclipse Turn processes into business applications with Bonita
BPM Community Edition Quickly connect people, data, and systems into
organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
___
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.
--
Open source business process management suite built on Java
and Eclipse Turn processes into business applications with Bonita
BPM Community Edition Quickly connect people, data, and systems into
organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
Re: [WiX-users] Bootstrapper not upgrading MSI
No, they don't. So, that's no it. Do you the MajorUpgrade element or the
Upgrade table? What do the entries look like?
--
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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com]
Sent: Monday, July 7, 2014 11:13 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Bootstrapper not upgrading MSI
Burn Bootstrappers do not have a ProductCode, do they?
The MSI Setup project has its product code set to *, and upgrades fine if not
run through the bootstrapper.
On Mon, Jul 7, 2014 at 11:52 AM, John Cooper jocoo...@jackhenry.com wrote:
Same ProductCode or a different ProductCode for each installer? You
can find the ProductCode with Orca in the Property table. If they're
the same, you're not setup for major upgrade.
--
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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com]
Sent: Monday, July 7, 2014 10:46 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Bootstrapper not upgrading MSI
I just attempted to do this with version 6.0.1.0 from 6.0.0.0, and
nothing changed. Progress text displays previous version and all
files from previous install are removed, but no new files are installed.
Logs are attached (The one ending in 0_compuweigh is the MSI)
On Mon, Jul 7, 2014 at 11:20 AM, John Cooper jocoo...@jackhenry.com
wrote:
The fourth quad is ignored, which means the versions are effectively
the same generating the behavior you're experiencing. Only the
first
three
quads are considered by the installer service. So, 6.0.0.0 and 6.0.1.0
would have worked but 6.0.0.0 and 6.0.0.1 never will.
--
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: Nick downey [mailto:fluffaluffagu...@gmail.com]
Sent: Monday, July 7, 2014 10:17 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Bootstrapper not upgrading MSI
The original version was 6.0.0.0 and the new one was 6.0.0.1
Sent with AquaMail for Android
http://www.aqua-mail.com
On July 7, 2014 11:13:07 AM John Cooper jocoo...@jackhenry.com wrote:
Well, the log indicates that Burn is uninstalling. What are the
version numbers for the initial and upgrade installs?
--
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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com]
Sent: Monday, July 7, 2014 10:00 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Bootstrapper not upgrading MSI
I have a Wix Bootstrapper which conditionally installs various
components, which are defaulted to not install unless a command
line
parameter is sent.
This works fine on the initial install, but when I attempt to
perform an upgrade, the command line parameters do not seem to be
being read.
It also does not upgrade the MSI being run by the bootstrapper,
just remove the files it created. The bootstrapper will display
Previous version for the progress text and then finish.
Here is the log for the Bootstrapper :
https://drive.google.com/file/d/0B4QDf83juiMDRFlnV2p0ZEVRYlE/edit?
us
p=
sharing
Here is the log for the msi being run:
https://drive.google.com/file/d/0B4QDf83juiMDUU1tdG9EdkUxMUk/edit?
us
p=
sharing
--
--
--
Open source business process management suite built on
Java and Eclipse Turn processes into business applications with
Bonita BPM Community Edition Quickly connect people, data, and
systems into organized workflows Winner of BOSSIE, CODIE, OW2 and
Gartner awards http://p.sf.net/sfu/Bonitasoft
___
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
Re: [WiX-users] Bootstrapper not upgrading MSI
It might be worth noting that after installing the bootstrapper, if i try and install the same package and click repair, that it will fix the install that never happened for the MSI, and that MSI will be the new version that should have been installed in the first place. It is only when I attempt to perform an upgrade through the bootstrapper. It also works fine if I just upgrade with the MSI. I want users to only have to run the bootstrapper each time for installs/upgrades and whatnot. On Mon, Jul 7, 2014 at 12:23 PM, John Cooper jocoo...@jackhenry.com wrote: No, they don't. So, that's no it. Do you the MajorUpgrade element or the Upgrade table? What do the entries look like? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 11:13 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI Burn Bootstrappers do not have a ProductCode, do they? The MSI Setup project has its product code set to *, and upgrades fine if not run through the bootstrapper. On Mon, Jul 7, 2014 at 11:52 AM, John Cooper jocoo...@jackhenry.com wrote: Same ProductCode or a different ProductCode for each installer? You can find the ProductCode with Orca in the Property table. If they're the same, you're not setup for major upgrade. -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:46 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI I just attempted to do this with version 6.0.1.0 from 6.0.0.0, and nothing changed. Progress text displays previous version and all files from previous install are removed, but no new files are installed. Logs are attached (The one ending in 0_compuweigh is the MSI) On Mon, Jul 7, 2014 at 11:20 AM, John Cooper jocoo...@jackhenry.com wrote: The fourth quad is ignored, which means the versions are effectively the same generating the behavior you're experiencing. Only the first three quads are considered by the installer service. So, 6.0.0.0 and 6.0.1.0 would have worked but 6.0.0.0 and 6.0.0.1 never will. -- 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: Nick downey [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:17 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI The original version was 6.0.0.0 and the new one was 6.0.0.1 Sent with AquaMail for Android http://www.aqua-mail.com On July 7, 2014 11:13:07 AM John Cooper jocoo...@jackhenry.com wrote: Well, the log indicates that Burn is uninstalling. What are the version numbers for the initial and upgrade installs? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:00 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapper not upgrading MSI I have a Wix Bootstrapper which conditionally installs various components, which are defaulted to not install unless a command line parameter is sent. This works fine on the initial install, but when I attempt to perform an upgrade, the command line parameters do not seem to be being read. It also does not upgrade the MSI being run by the bootstrapper, just remove the files it created. The bootstrapper will display Previous version for the progress text and then finish. Here is the log for the Bootstrapper : https://drive.google.com/file/d/0B4QDf83juiMDRFlnV2p0ZEVRYlE/edit? us p= sharing Here is the log for the msi being run: https://drive.google.com/file/d/0B4QDf83juiMDUU1tdG9EdkUxMUk/edit? us p= sharing -- -- -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition
Re: [WiX-users] Bootstrapper not upgrading MSI
Yes, that's an important clue. For most of your assemblies, do they differ only in the fourth quad between the initial install and the upgrade? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 11:53 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI It might be worth noting that after installing the bootstrapper, if i try and install the same package and click repair, that it will fix the install that never happened for the MSI, and that MSI will be the new version that should have been installed in the first place. It is only when I attempt to perform an upgrade through the bootstrapper. It also works fine if I just upgrade with the MSI. I want users to only have to run the bootstrapper each time for installs/upgrades and whatnot. On Mon, Jul 7, 2014 at 12:23 PM, John Cooper jocoo...@jackhenry.com wrote: No, they don't. So, that's no it. Do you the MajorUpgrade element or the Upgrade table? What do the entries look like? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 11:13 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI Burn Bootstrappers do not have a ProductCode, do they? The MSI Setup project has its product code set to *, and upgrades fine if not run through the bootstrapper. On Mon, Jul 7, 2014 at 11:52 AM, John Cooper jocoo...@jackhenry.com wrote: Same ProductCode or a different ProductCode for each installer? You can find the ProductCode with Orca in the Property table. If they're the same, you're not setup for major upgrade. -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:46 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI I just attempted to do this with version 6.0.1.0 from 6.0.0.0, and nothing changed. Progress text displays previous version and all files from previous install are removed, but no new files are installed. Logs are attached (The one ending in 0_compuweigh is the MSI) On Mon, Jul 7, 2014 at 11:20 AM, John Cooper jocoo...@jackhenry.com wrote: The fourth quad is ignored, which means the versions are effectively the same generating the behavior you're experiencing. Only the first three quads are considered by the installer service. So, 6.0.0.0 and 6.0.1.0 would have worked but 6.0.0.0 and 6.0.0.1 never will. -- 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: Nick downey [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:17 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI The original version was 6.0.0.0 and the new one was 6.0.0.1 Sent with AquaMail for Android http://www.aqua-mail.com On July 7, 2014 11:13:07 AM John Cooper jocoo...@jackhenry.com wrote: Well, the log indicates that Burn is uninstalling. What are the version numbers for the initial and upgrade installs? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:00 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapper not upgrading MSI I have a Wix Bootstrapper which conditionally installs various components, which are defaulted to not install unless a command line parameter is sent. This works fine on the initial install, but when I attempt to perform an upgrade, the command line parameters do not seem to be being read. It also does not upgrade the MSI being run by the bootstrapper, just remove the files it created. The bootstrapper will display Previous
Re: [WiX-users] Bootstrapper not upgrading MSI
I just have the one Setup Project which is installed via my bootstrapper, the other items are other installable items such as SQL Server and other things that the software depends on. Since you telling me that the fourth quad is ignored, I have been testing installs by incrementing the third quad by one for each test, but to no avail. On Mon, Jul 7, 2014 at 12:58 PM, John Cooper jocoo...@jackhenry.com wrote: Yes, that's an important clue. For most of your assemblies, do they differ only in the fourth quad between the initial install and the upgrade? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 11:53 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI It might be worth noting that after installing the bootstrapper, if i try and install the same package and click repair, that it will fix the install that never happened for the MSI, and that MSI will be the new version that should have been installed in the first place. It is only when I attempt to perform an upgrade through the bootstrapper. It also works fine if I just upgrade with the MSI. I want users to only have to run the bootstrapper each time for installs/upgrades and whatnot. On Mon, Jul 7, 2014 at 12:23 PM, John Cooper jocoo...@jackhenry.com wrote: No, they don't. So, that's no it. Do you the MajorUpgrade element or the Upgrade table? What do the entries look like? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 11:13 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI Burn Bootstrappers do not have a ProductCode, do they? The MSI Setup project has its product code set to *, and upgrades fine if not run through the bootstrapper. On Mon, Jul 7, 2014 at 11:52 AM, John Cooper jocoo...@jackhenry.com wrote: Same ProductCode or a different ProductCode for each installer? You can find the ProductCode with Orca in the Property table. If they're the same, you're not setup for major upgrade. -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:46 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI I just attempted to do this with version 6.0.1.0 from 6.0.0.0, and nothing changed. Progress text displays previous version and all files from previous install are removed, but no new files are installed. Logs are attached (The one ending in 0_compuweigh is the MSI) On Mon, Jul 7, 2014 at 11:20 AM, John Cooper jocoo...@jackhenry.com wrote: The fourth quad is ignored, which means the versions are effectively the same generating the behavior you're experiencing. Only the first three quads are considered by the installer service. So, 6.0.0.0 and 6.0.1.0 would have worked but 6.0.0.0 and 6.0.0.1 never will. -- 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: Nick downey [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:17 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI The original version was 6.0.0.0 and the new one was 6.0.0.1 Sent with AquaMail for Android http://www.aqua-mail.com On July 7, 2014 11:13:07 AM John Cooper jocoo...@jackhenry.com wrote: Well, the log indicates that Burn is uninstalling. What are the version numbers for the initial and upgrade installs? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:00 AM To: wix-users@lists.sourceforge.net
Re: [WiX-users] Bootstrapper not upgrading MSI
I apologize for the double response, but as stated previously, the bootstrapper is not reading command line arguments (which are used to satisfy InstallConditions) only when I am trying to upgrade, and though right now I am hard-coding INSTALLCW6=1 (the installcondition for the msi i am trying to upgrade), I wonder if the issue is related to the lack of a functional upgrade or not. On Mon, Jul 7, 2014 at 12:58 PM, John Cooper jocoo...@jackhenry.com wrote: Yes, that's an important clue. For most of your assemblies, do they differ only in the fourth quad between the initial install and the upgrade? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 11:53 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI It might be worth noting that after installing the bootstrapper, if i try and install the same package and click repair, that it will fix the install that never happened for the MSI, and that MSI will be the new version that should have been installed in the first place. It is only when I attempt to perform an upgrade through the bootstrapper. It also works fine if I just upgrade with the MSI. I want users to only have to run the bootstrapper each time for installs/upgrades and whatnot. On Mon, Jul 7, 2014 at 12:23 PM, John Cooper jocoo...@jackhenry.com wrote: No, they don't. So, that's no it. Do you the MajorUpgrade element or the Upgrade table? What do the entries look like? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 11:13 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI Burn Bootstrappers do not have a ProductCode, do they? The MSI Setup project has its product code set to *, and upgrades fine if not run through the bootstrapper. On Mon, Jul 7, 2014 at 11:52 AM, John Cooper jocoo...@jackhenry.com wrote: Same ProductCode or a different ProductCode for each installer? You can find the ProductCode with Orca in the Property table. If they're the same, you're not setup for major upgrade. -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:46 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI I just attempted to do this with version 6.0.1.0 from 6.0.0.0, and nothing changed. Progress text displays previous version and all files from previous install are removed, but no new files are installed. Logs are attached (The one ending in 0_compuweigh is the MSI) On Mon, Jul 7, 2014 at 11:20 AM, John Cooper jocoo...@jackhenry.com wrote: The fourth quad is ignored, which means the versions are effectively the same generating the behavior you're experiencing. Only the first three quads are considered by the installer service. So, 6.0.0.0 and 6.0.1.0 would have worked but 6.0.0.0 and 6.0.0.1 never will. -- 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: Nick downey [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:17 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI The original version was 6.0.0.0 and the new one was 6.0.0.1 Sent with AquaMail for Android http://www.aqua-mail.com On July 7, 2014 11:13:07 AM John Cooper jocoo...@jackhenry.com wrote: Well, the log indicates that Burn is uninstalling. What are the version numbers for the initial and upgrade installs? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10
Re: [WiX-users] Bootstrapper not upgrading MSI
Well, the bootstrapper will only accept command line line arguments that are: 1) declared as Variable and 2) marked with bal:Overrideable=yes attributes. -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 12:54 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI I apologize for the double response, but as stated previously, the bootstrapper is not reading command line arguments (which are used to satisfy InstallConditions) only when I am trying to upgrade, and though right now I am hard-coding INSTALLCW6=1 (the installcondition for the msi i am trying to upgrade), I wonder if the issue is related to the lack of a functional upgrade or not. On Mon, Jul 7, 2014 at 12:58 PM, John Cooper jocoo...@jackhenry.com wrote: Yes, that's an important clue. For most of your assemblies, do they differ only in the fourth quad between the initial install and the upgrade? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 11:53 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI It might be worth noting that after installing the bootstrapper, if i try and install the same package and click repair, that it will fix the install that never happened for the MSI, and that MSI will be the new version that should have been installed in the first place. It is only when I attempt to perform an upgrade through the bootstrapper. It also works fine if I just upgrade with the MSI. I want users to only have to run the bootstrapper each time for installs/upgrades and whatnot. On Mon, Jul 7, 2014 at 12:23 PM, John Cooper jocoo...@jackhenry.com wrote: No, they don't. So, that's no it. Do you the MajorUpgrade element or the Upgrade table? What do the entries look like? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 11:13 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI Burn Bootstrappers do not have a ProductCode, do they? The MSI Setup project has its product code set to *, and upgrades fine if not run through the bootstrapper. On Mon, Jul 7, 2014 at 11:52 AM, John Cooper jocoo...@jackhenry.com wrote: Same ProductCode or a different ProductCode for each installer? You can find the ProductCode with Orca in the Property table. If they're the same, you're not setup for major upgrade. -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:46 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI I just attempted to do this with version 6.0.1.0 from 6.0.0.0, and nothing changed. Progress text displays previous version and all files from previous install are removed, but no new files are installed. Logs are attached (The one ending in 0_compuweigh is the MSI) On Mon, Jul 7, 2014 at 11:20 AM, John Cooper jocoo...@jackhenry.com wrote: The fourth quad is ignored, which means the versions are effectively the same generating the behavior you're experiencing. Only the first three quads are considered by the installer service. So, 6.0.0.0 and 6.0.1.0 would have worked but 6.0.0.0 and 6.0.0.1 never will. -- 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: Nick downey [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:17 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI The original version was 6.0.0.0 and the new one was 6.0.0.1 Sent with AquaMail for Android http://www.aqua-mail.com
Re: [WiX-users] Bootstrapper not upgrading MSI
Yes, but it also applies to the assemblies within. If the installer service doesn't think the assemblies are different, no update for each individual assembly will occur. -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 12:07 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI I just have the one Setup Project which is installed via my bootstrapper, the other items are other installable items such as SQL Server and other things that the software depends on. Since you telling me that the fourth quad is ignored, I have been testing installs by incrementing the third quad by one for each test, but to no avail. On Mon, Jul 7, 2014 at 12:58 PM, John Cooper jocoo...@jackhenry.com wrote: Yes, that's an important clue. For most of your assemblies, do they differ only in the fourth quad between the initial install and the upgrade? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 11:53 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI It might be worth noting that after installing the bootstrapper, if i try and install the same package and click repair, that it will fix the install that never happened for the MSI, and that MSI will be the new version that should have been installed in the first place. It is only when I attempt to perform an upgrade through the bootstrapper. It also works fine if I just upgrade with the MSI. I want users to only have to run the bootstrapper each time for installs/upgrades and whatnot. On Mon, Jul 7, 2014 at 12:23 PM, John Cooper jocoo...@jackhenry.com wrote: No, they don't. So, that's no it. Do you the MajorUpgrade element or the Upgrade table? What do the entries look like? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 11:13 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI Burn Bootstrappers do not have a ProductCode, do they? The MSI Setup project has its product code set to *, and upgrades fine if not run through the bootstrapper. On Mon, Jul 7, 2014 at 11:52 AM, John Cooper jocoo...@jackhenry.com wrote: Same ProductCode or a different ProductCode for each installer? You can find the ProductCode with Orca in the Property table. If they're the same, you're not setup for major upgrade. -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:46 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI I just attempted to do this with version 6.0.1.0 from 6.0.0.0, and nothing changed. Progress text displays previous version and all files from previous install are removed, but no new files are installed. Logs are attached (The one ending in 0_compuweigh is the MSI) On Mon, Jul 7, 2014 at 11:20 AM, John Cooper jocoo...@jackhenry.com wrote: The fourth quad is ignored, which means the versions are effectively the same generating the behavior you're experiencing. Only the first three quads are considered by the installer service. So, 6.0.0.0 and 6.0.1.0 would have worked but 6.0.0.0 and 6.0.0.1 never will. -- 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: Nick downey [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:17 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI The original version was 6.0.0.0 and the new one was 6.0.0.1 Sent with AquaMail for Android http://www.aqua-mail.com On July 7, 2014 11
Re: [WiX-users] Bootstrapper not upgrading MSI
It is still removing all of the old assemblies, though, and all of the components of the MSI that were not created via a custom action. My command line arguments are both declared as variables and markes as overrideable. On Mon, Jul 7, 2014 at 2:38 PM, John Cooper jocoo...@jackhenry.com wrote: Yes, but it also applies to the assemblies within. If the installer service doesn't think the assemblies are different, no update for each individual assembly will occur. -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 12:07 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI I just have the one Setup Project which is installed via my bootstrapper, the other items are other installable items such as SQL Server and other things that the software depends on. Since you telling me that the fourth quad is ignored, I have been testing installs by incrementing the third quad by one for each test, but to no avail. On Mon, Jul 7, 2014 at 12:58 PM, John Cooper jocoo...@jackhenry.com wrote: Yes, that's an important clue. For most of your assemblies, do they differ only in the fourth quad between the initial install and the upgrade? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 11:53 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI It might be worth noting that after installing the bootstrapper, if i try and install the same package and click repair, that it will fix the install that never happened for the MSI, and that MSI will be the new version that should have been installed in the first place. It is only when I attempt to perform an upgrade through the bootstrapper. It also works fine if I just upgrade with the MSI. I want users to only have to run the bootstrapper each time for installs/upgrades and whatnot. On Mon, Jul 7, 2014 at 12:23 PM, John Cooper jocoo...@jackhenry.com wrote: No, they don't. So, that's no it. Do you the MajorUpgrade element or the Upgrade table? What do the entries look like? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 11:13 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI Burn Bootstrappers do not have a ProductCode, do they? The MSI Setup project has its product code set to *, and upgrades fine if not run through the bootstrapper. On Mon, Jul 7, 2014 at 11:52 AM, John Cooper jocoo...@jackhenry.com wrote: Same ProductCode or a different ProductCode for each installer? You can find the ProductCode with Orca in the Property table. If they're the same, you're not setup for major upgrade. -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:46 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI I just attempted to do this with version 6.0.1.0 from 6.0.0.0, and nothing changed. Progress text displays previous version and all files from previous install are removed, but no new files are installed. Logs are attached (The one ending in 0_compuweigh is the MSI) On Mon, Jul 7, 2014 at 11:20 AM, John Cooper jocoo...@jackhenry.com wrote: The fourth quad is ignored, which means the versions are effectively the same generating the behavior you're experiencing. Only the first three quads are considered by the installer service. So, 6.0.0.0 and 6.0.1.0 would have worked but 6.0.0.0 and 6.0.0.1 never will. -- 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
Re: [WiX-users] Bootstrapper not upgrading MSI
Just realized my parameters are being passed.. I was just being stupid, so my apologies there. The issue in regards to upgrading still remains however, where the installed files from the previous install are removed in my attempt to upgrade, but the new files are not added. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-not-upgrading-MSI-tp7595682p7595707.html Sent from the wix-users mailing list archive at Nabble.com. -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper not upgrading MSI
I think this has been answered but in case this is read later this is not true for WiX bundles they do use the forth quad. Also, within an MSI the forth quad is used when comparing file versions, the only place it is not used is the MSI itself. Neil -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: 07 July 2014 16:21 To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI The fourth quad is ignored, which means the versions are effectively the same generating the behavior you're experiencing. Only the first three quads are considered by the installer service. So, 6.0.0.0 and 6.0.1.0 would have worked but 6.0.0.0 and 6.0.0.1 never will. -- 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: Nick downey [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:17 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI The original version was 6.0.0.0 and the new one was 6.0.0.1 Sent with AquaMail for Android http://www.aqua-mail.com On July 7, 2014 11:13:07 AM John Cooper jocoo...@jackhenry.com wrote: Well, the log indicates that Burn is uninstalling. What are the version numbers for the initial and upgrade installs? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:00 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapper not upgrading MSI I have a Wix Bootstrapper which conditionally installs various components, which are defaulted to not install unless a command line parameter is sent. This works fine on the initial install, but when I attempt to perform an upgrade, the command line parameters do not seem to be being read. It also does not upgrade the MSI being run by the bootstrapper, just remove the files it created. The bootstrapper will display Previous version for the progress text and then finish. Here is the log for the Bootstrapper : https://drive.google.com/file/d/0B4QDf83juiMDRFlnV2p0ZEVRYlE/edit?usp= sharing Here is the log for the msi being run: https://drive.google.com/file/d/0B4QDf83juiMDUU1tdG9EdkUxMUk/edit?usp= sharing -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ 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. -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ 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
Re: [WiX-users] Bootstrapper not upgrading MSI
As far as I know that's only true for MSI product versions, not for bootstrapper versions. -- Nicolas 2014-07-07 12:20 GMT-03:00 John Cooper jocoo...@jackhenry.com: The fourth quad is ignored, which means the versions are effectively the same generating the behavior you're experiencing. Only the first three quads are considered by the installer service. So, 6.0.0.0 and 6.0.1.0 would have worked but 6.0.0.0 and 6.0.0.1 never will. -- 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: Nick downey [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:17 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI The original version was 6.0.0.0 and the new one was 6.0.0.1 Sent with AquaMail for Android http://www.aqua-mail.com On July 7, 2014 11:13:07 AM John Cooper jocoo...@jackhenry.com wrote: Well, the log indicates that Burn is uninstalling. What are the version numbers for the initial and upgrade installs? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:00 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapper not upgrading MSI I have a Wix Bootstrapper which conditionally installs various components, which are defaulted to not install unless a command line parameter is sent. This works fine on the initial install, but when I attempt to perform an upgrade, the command line parameters do not seem to be being read. It also does not upgrade the MSI being run by the bootstrapper, just remove the files it created. The bootstrapper will display Previous version for the progress text and then finish. Here is the log for the Bootstrapper : https://drive.google.com/file/d/0B4QDf83juiMDRFlnV2p0ZEVRYlE/edit?usp= sharing Here is the log for the msi being run: https://drive.google.com/file/d/0B4QDf83juiMDUU1tdG9EdkUxMUk/edit?usp= sharing -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper not upgrading MSI
Yes, I was referring to the MSI (although I generally setup my bootstrappers to have a version matching the primary MSI). -- John Merryweather Cooper Build Install Engineer - jXchange Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com From: Nicolás Alvarez [nicolas.alva...@gmail.com] Sent: Monday, July 07, 2014 5:42 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI As far as I know that's only true for MSI product versions, not for bootstrapper versions. -- Nicolas 2014-07-07 12:20 GMT-03:00 John Cooper jocoo...@jackhenry.com: The fourth quad is ignored, which means the versions are effectively the same generating the behavior you're experiencing. Only the first three quads are considered by the installer service. So, 6.0.0.0 and 6.0.1.0 would have worked but 6.0.0.0 and 6.0.0.1 never will. -- 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: Nick downey [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:17 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper not upgrading MSI The original version was 6.0.0.0 and the new one was 6.0.0.1 Sent with AquaMail for Android http://www.aqua-mail.com On July 7, 2014 11:13:07 AM John Cooper jocoo...@jackhenry.com wrote: Well, the log indicates that Burn is uninstalling. What are the version numbers for the initial and upgrade installs? -- 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: Steven Fluffaluffagus [mailto:fluffaluffagu...@gmail.com] Sent: Monday, July 7, 2014 10:00 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapper not upgrading MSI I have a Wix Bootstrapper which conditionally installs various components, which are defaulted to not install unless a command line parameter is sent. This works fine on the initial install, but when I attempt to perform an upgrade, the command line parameters do not seem to be being read. It also does not upgrade the MSI being run by the bootstrapper, just remove the files it created. The bootstrapper will display Previous version for the progress text and then finish. Here is the log for the Bootstrapper : https://drive.google.com/file/d/0B4QDf83juiMDRFlnV2p0ZEVRYlE/edit?usp= sharing Here is the log for the msi being run: https://drive.google.com/file/d/0B4QDf83juiMDUU1tdG9EdkUxMUk/edit?usp= sharing -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ 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. -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper will launch in Win 8 but not Win 7
I spent sometime digging into this using the debugger but I can't seem to
find anything errors. I was digging into the logs for the installs on my
machine, the VM and the other win 7 user machines. All the failed installs
look like this:
[0778:055C][2014-06-23T10:22:04]i000: Loading managed bootstrapper
application.
[0778:055C][2014-06-23T10:22:05]e000: Error 0x8013141a: Failed to create the
managed bootstrapper application.
[0778:055C][2014-06-23T10:22:05]e000: Error 0x8013141a: Failed to create UX.
[0778:055C][2014-06-23T10:22:05]e000: Error 0x8013141a: Failed to load UX.
[0778:055C][2014-06-23T10:22:05]e000: Error 0x8013141a: Failed while running
[0778:055C][2014-06-23T10:22:05]i410: Variable: DisplayVersion = 1.0.0.0
[0778:055C][2014-06-23T10:22:05]i410: Variable: WixBundleAction = 4
[0778:055C][2014-06-23T10:22:05]i410: Variable: WixBundleElevated = 0
[0778:055C][2014-06-23T10:22:05]i410: Variable: WixBundleLog =
C:\Users\devinm\AppData\Local\Temp\Client_20140623102202.log
[0778:055C][2014-06-23T10:22:05]i410: Variable: WixBundleManufacturer = ME
[0778:055C][2014-06-23T10:22:05]i410: Variable: WixBundleName = Client
Package
[0778:055C][2014-06-23T10:22:05]i410: Variable: WixBundleOriginalSource =
C:\Users\d\Desktop\ClientBundle.exe
[0778:055C][2014-06-23T10:22:05]i410: Variable: WixBundleProviderKey =
{9c172dc5-e2df-4130-be4e-23af428c1bf7}
[0778:055C][2014-06-23T10:22:05]i410: Variable: WixBundleTag =
[0778:055C][2014-06-23T10:22:05]i410: Variable: WixBundleVersion = 1.0.0.0
[0778:055C][2014-06-23T10:22:05]e000: Error 0x8013141a: Failed to run
per-user mode.
[0778:055C][2014-06-23T10:22:05]i007: Exit code: 0x8013141a, restarting: No
On my personal Win7 machine and any Win8 machine, the bootstrapper runs just
fine and the logs look like this:
[0B74:093C][2014-06-23T09:50:48]i410: Variable: DisplayVersion = 1.0.0.0
[0B74:093C][2014-06-23T09:50:48]i410: Variable: InstallFolder = C:\Program
Files (x86)\Client
[0B74:093C][2014-06-23T09:50:48]i410: Variable: Netfx4FullVersion =
4.5.50938
[0B74:093C][2014-06-23T09:50:48]i410: Variable: Netfx4x64FullVersion =
4.5.50938
[0B74:093C][2014-06-23T09:50:48]i410: Variable: WixBundleAction = 4
[0B74:093C][2014-06-23T09:50:48]i410: Variable: WixBundleElevated = 1
[0B74:093C][2014-06-23T09:50:48]i410: Variable: WixBundleLog =
C:\Users\d\AppData\Local\Temp\Client_Package_20140623094752.log
[0B74:093C][2014-06-23T09:50:48]i410: Variable: WixBundleLog_Client =
C:\Users\d\AppData\Local\Temp\Client_Package_20140623094752_0_Client.log
[0B74:093C][2014-06-23T09:50:48]i410: Variable: WixBundleManufacturer = ME
[0B74:093C][2014-06-23T09:50:48]i410: Variable: WixBundleName = Client
Package
[0B74:093C][2014-06-23T09:50:48]i410: Variable: WixBundleOriginalSource =
C:\Users\d\Desktop\ClientBundle.exe
[0B74:093C][2014-06-23T09:50:48]i410: Variable: WixBundleProviderKey =
{9c172dc5-e2df-4130-be4e-23af428c1bf7}
[0B74:093C][2014-06-23T09:50:48]i410: Variable: WixBundleRollbackLog_Client
=
C:\Users\d\AppData\Local\Temp\Client_Package_20140623094752_0_Client_rollback.log
[0B74:093C][2014-06-23T09:50:48]i410: Variable: WixBundleTag =
[0B74:093C][2014-06-23T09:50:48]i410: Variable: WixBundleVersion = 1.0.0.0
My assumption is the bootstrapper isn't able to run as elevated and is
failing. I'm not sure why it works on certain machines and not others
though. All of the users in this office are admins and running the file as
admin doesn't seem to change much.
Thanks for the earlier reply.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-will-launch-in-Win-8-but-not-Win-7-tp7595374p7595415.html
Sent from the wix-users mailing list archive at Nabble.com.
--
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper will launch in Win 8 but not Win 7
Argh, I apologize, It looks like I was checking the wrong log. Running as admin on the VM spits out similar logs as my machine for elevation. It still won't run on any Win7 machine other than mine, but all the Win8's work just fine. Any ideas as to what would be missing? That debugger you linked was helpful but It's not showing any fails or errors. Thanks Again -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-will-launch-in-Win-8-but-not-Win-7-tp7595374p7595416.html Sent from the wix-users mailing list archive at Nabble.com. -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper will launch in Win 8 but not Win 7
It sounds like the mba has a dependency file which should be added to the bundle as a Payload element. http://blogs.msdn.com/b/suzcook/archive/2003/05/29/debugging-assembly-loading-failures.aspx Generally I would not test a setup on my development machine. No telling what damage could be done. I would always test on a clean VM/machine. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-will-launch-in-Win-8-but-not-Win-7-tp7595374p7595384.html Sent from the wix-users mailing list archive at Nabble.com. -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrapper will launch in Win 8 but not Win 7
First off, sorry for all the questions! I was able to figure out all my localization issues. I'm ready to deliver the project except I can't get the bootstrapper to launch on Win machines. The only Win 7 machine it will run on is mine. Every other Win 7 machine in the office gives me this error in the log: [0CE8:0CEC][2014-06-19T17:40:22]i000: Loading managed bootstrapper application. [0CE8:0CEC][2014-06-19T17:40:22]e000: Error 0x8013141a: Failed to create the managed bootstrapper application. [0CE8:0CEC][2014-06-19T17:40:22]e000: Error 0x8013141a: Failed to create UX. [0CE8:0CEC][2014-06-19T17:40:22]e000: Error 0x8013141a: Failed to load UX. [0CE8:0CEC][2014-06-19T17:40:22]e000: Error 0x8013141a: Failed while running [0CE8:0CEC][2014-06-19T17:40:22]i410: Variable: DisplayVersion = 1.0.0.0 [0CE8:0CEC][2014-06-19T17:40:22]i410: Variable: WixBundleAction = 4 I assumed it was a .net issue but I have the exact same .net versions installed on my machine as the other Win 7 comps. My MBA is a WPF app targeted at .net 4.0. All the machines in my office are set up with 4.5 or higher. If I remove .net from a machine and use the wix bundle to install 4.0, it installs fine but gives me the same error as above. Here is my bundle code. ?xml version=1.0 encoding=UTF-8? 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; xmlns:netfx=http://schemas.microsoft.com/wix/NetFxExtension; ?define BundleVersion=1.0.0.0 ? Bundle Name=Client Package Version=$(var.BundleVersion) Manufacturer=Mi UpgradeCode=01C56548-DD67-425F-BA0C-875705F36327 IconSourceFile=$(var.ICONNAME) BootstrapperApplicationRef Id=ManagedBootstrapperApplicationHost Payload SourceFile=$(var.SolutionDir)Client_Wizard\BootstrapperCore.config/ Payload SourceFile='!(wix.PreqbaThemeXml=SourceDir\Resources\mbapreq.thm)' Compressed='yes' Name='mbapreq.thm'/ Payload SourceFile='!(wix.PreqbaThemeWxl=SourceDir\Resources\mbapreq.wxl)' Compressed='yes' Name='mbapreq.wxl'/ Chain PackageGroupRef Id='Netfx4Full' / MsiPackage SourceFile=$(var.TargetDir)ClientInstall.msi Id=Client Cache=no Visible=no ForcePerMachine=yes MsiProperty Name=INSTALLDIR Value=[InstallFolder]/ /MsiPackage /Chain /Bundle Fragment Variable Name=InstallationPath bal:Overridable=yes / WixVariable Id=PreqbaThemeXml Value=Resources\mbapreq.thm / WixVariable Id=PreqbaThemeWxl Value=Resources\mbapreq.wxl / WixVariable Id=WixMbaPrereqPackageId Value=Netfx4Full / WixVariable Id=WixMbaPrereqLicenseUrl Value=NetfxLicense.rtf / Variable Name=DisplayVersion Value=$(var.BundleVersion) / util:RegistrySearch Root=HKLM Key=SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Full Value=Version Variable=Netfx4FullVersion / util:RegistrySearch Root=HKLM Key=SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Full Value=Version Variable=Netfx4x64FullVersion Win64=yes / util:RegistrySearch Root=HKCU Key=SOFTWARE\Microsoft\PFE\Client Value=Client Variable=ClientExists / PackageGroup Id=Netfx4Full ExePackage Id=Netfx4Full Cache=no PerMachine=yes Permanent=yes Vital=yes Compressed=no Name=..\..\DotNetInstallers\dotNetFx40_Full_x86_x64.exe DownloadUrl=http://go.microsoft.com/fwlink/?LinkID=402630; DetectCondition=Netfx4FullVersion OR Netfx4x64FullVersion /ExePackage /PackageGroup There has to be some kind of .net conflict here. Also, where is the best place to report bugs? I found a few issues with copying files and MBA preq installer localization. Any help you can offer is much appreciated! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-will-launch-in-Win-8-but-not-Win-7-tp7595374.html Sent from the wix-users mailing list archive at Nabble.com. -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper-UI: Text from Startpage overlapping with text from Modifypage
Ok, i solved the problem myself. I deleted all Visible=yes and set the Width on -11 and it works now :) -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-UI-Text-from-Startpage-overlapping-with-text-from-Modifypage-tp7594670p7594728.html Sent from the wix-users mailing list archive at Nabble.com. -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper-UI: Text from Startpage overlapping with text from Modifypage
Had the same problem. Had to sought it out myself. Don't know what I did but HideWhenDisabled=yes is a false friend. Remove them all and then test. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-UI-Text-from-Startpage-overlapping-with-text-from-Modifypage-tp7594670p7594686.html Sent from the wix-users mailing list archive at Nabble.com. -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper-UI: Text from Startpage overlapping with text from Modifypage
Dit mailadres is niet meer in gebruik. Mail kan je voortaan sturen naar basti...@careercontrol.nl. -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper-UI: Text from Startpage overlapping with text from Modifypage
darbid wrote Remove them all and then test. Thanks for your answer! I removed them but it didn't solve my problem :/ -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-UI-Text-from-Startpage-overlapping-with-text-from-Modifypage-tp7594670p7594688.html Sent from the wix-users mailing list archive at Nabble.com. -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrapper-UI: Text from Startpage overlapping with text from Modifypage
Hello! When I install my setup, it shows the InstallHeader and InstallMessage on the first page (startpage) and not on the other pages, like it should do. But when I installed my setup and start my setup again, the modifypage appears with the ModifyHeader AND the InstallHeader and InstallMessage?! I use WIX 3.8 in Visual Studio 2012. What could be wrong? My theme file: ?xml version=1.0 encoding=utf-8? Theme xmlns=http://wixtoolset.org/schemas/thmutil/2010; Window Width=485 Height=300 HexStyle=100a FontId=0#(loc.Caption)/Window Font Id=0 Height=-12 Weight=500 Foreground=00 Background=FFSegoe UI/Font Font Id=1 Height=-24 Weight=500 Foreground=00Segoe UI/Font Font Id=2 Height=-22 Weight=500 Foreground=66 Background=FFSegoe UI/Font Font Id=3 Height=-12 Weight=500 Foreground=00 Background=FFSegoe UI/Font Font Id=4 Height=-12 Weight=500 Foreground=ff Background=FF Underline=yesSegoe UI/Font Image X=11 Y=11 Width=64 Height=64 ImageFile=logo.png Visible=yes/ Text X=80 Y=11 Width=-11 Height=64 FontId=1 Visible=yes DisablePrefix=yes#(loc.Title)/Text Page Name=Help Text X=11 Y=80 Width=-11 Height=30 FontId=2 DisablePrefix=yes#(loc.HelpHeader)/Text Text X=11 Y=112 Width=-11 Height=-35 FontId=3 DisablePrefix=yes#(loc.HelpText)/Text Button Name=HelpCancelButton X=-11 Y=-11 Width=75 Height=23 TabStop=yes FontId=0#(loc.HelpCloseButton)/Button /Page Page Name=Install !-- Hypertext Name=EulaHyperlink X=11 Y=121 Width=-11 Height=51 TabStop=yes FontId=3 HideWhenDisabled=yes#(loc.InstallLicenseLinkText)/Hypertext Checkbox Name=EulaAcceptCheckbox X=-11 Y=-41 Width=260 Height=17 TabStop=yes FontId=3 HideWhenDisabled=yes#(loc.InstallAcceptCheckbox)/Checkbox -- Text X=11 Y=80 Width=-11 Height=30 FontId=2 Visible=yes DisablePrefix=yes#(loc.InstallHeader)/Text Text X=11 Y=121 Width=300 Height=50 FontId=3 Visible=yes DisablePrefix=yes#(loc.InstallMessage)/Text Button Name=OptionsButton X=-171 Y=-11 Width=75 Height=23 TabStop=yes FontId=0 HideWhenDisabled=yes#(loc.InstallOptionsButton)/Button Button Name=InstallButton X=-91 Y=-11 Width=75 Height=23 TabStop=yes FontId=0#(loc.InstallInstallButton)/Button Button Name=WelcomeCancelButton X=-11 Y=-11 Width=75 Height=23 TabStop=yes FontId=0#(loc.InstallCloseButton)/Button /Page Page Name=Options Text X=11 Y=80 Width=-11 Height=30 FontId=2 DisablePrefix=yes#(loc.OptionsHeader)/Text Text X=11 Y=121 Width=-11 Height=17 FontId=3 DisablePrefix=yes#(loc.OptionsLocationLabel)/Text Editbox Name=FolderEditbox X=11 Y=143 Width=-91 Height=21 TabStop=yes FontId=3 FileSystemAutoComplete=yes / Button Name=BrowseButton X=-11 Y=142 Width=75 Height=23 TabStop=yes FontId=3#(loc.OptionsBrowseButton)/Button Button Name=OptionsOkButton X=-91 Y=-11 Width=75 Height=23 TabStop=yes FontId=0#(loc.OptionsOkButton)/Button Button Name=OptionsCancelButton X=-11 Y=-11 Width=75 Height=23 TabStop=yes FontId=0#(loc.OptionsCancelButton)/Button /Page Page Name=Progress Text X=11 Y=80 Width=-11 Height=30 FontId=2 DisablePrefix=yes#(loc.ProgressHeader)/Text Text X=11 Y=121 Width=70 Height=17 FontId=3 DisablePrefix=yes#(loc.ProgressLabel)/Text Text Name=OverallProgressPackageText X=85 Y=121 Width=-11 Height=17 FontId=3 DisablePrefix=yes#(loc.OverallProgressPackageText)/Text Progressbar Name=OverallCalculatedProgressbar X=11 Y=143 Width=-11 Height=15 / Button Name=ProgressCancelButton X=-11 Y=-11 Width=75 Height=23 TabStop=yes FontId=0#(loc.ProgressCancelButton)/Button /Page Page Name=Modify Text X=11 Y=80 Width=-11 Height=30 FontId=2 DisablePrefix=yes#(loc.ModifyHeader)/Text Button Name=RepairButton X=-171 Y=-11 Width=75 Height=23 TabStop=yes FontId=0 HideWhenDisabled=yes#(loc.ModifyRepairButton)/Button Button Name=UninstallButton X=-91 Y=-11 Width=75 Height=23 TabStop=yes FontId=0#(loc.ModifyUninstallButton)/Button Button Name=ModifyCancelButton X=-11 Y=-11 Width=75 Height=23 TabStop=yes FontId=0#(loc.ModifyCloseButton)/Button /Page Page Name=Success Text X=11 Y=80 Width=-11 Height=30 FontId=2 DisablePrefix=yes#(loc.SuccessHeader)/Text Button Name=LaunchButton X=-91 Y=-11 Width=75 Height=23 TabStop=yes FontId=0 HideWhenDisabled=yes#(loc.SuccessLaunchButton)/Button Text Name=SuccessRestartText X=-11 Y=-51 Width=400 Height=34 FontId=3 HideWhenDisabled=yes DisablePrefix=yes#(loc.SuccessRestartText)/Text Button Name=SuccessRestartButton X=-91 Y=-11 Width=75 Height=23 TabStop=yes FontId=0 HideWhenDisabled=yes#(loc.SuccessRestartButton)/Button Button Name=SuccessCancelButton X=-11 Y=-11 Width=75 Height=23 TabStop=yes FontId=0#(loc.SuccessCloseButton)/Button /Page Page
Re: [WiX-users] Bootstrapper config file/Answer file
No. By design no. The Bundle makes a lot of security guarantees and does not use external files to define the chain. A custom BA could use external data (like a .config file) to decide what packages to install from a chain, but the chain definition is built into the Bundle. ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -Original Message- From: Jeremiahf [mailto:jeremi...@gmail.com] Sent: Thursday, April 3, 2014 2:12 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Bootstrapper config file/Answer file Hi all, I have been looking everywhere to find the answer to this question. Does WIX Bootstrapper support the use of an xml config file or answer file to obtain the chain of packages to install? I have seen bootstrapper.confg files and some other information but I feel like I am going down rabbit holes. I would just like to have a single setup.exe file that can utilize a managed configuration file so that the bootstrapper doesn't have to be recompiled when there are version updates. Is it possible? Thank you, J -- ___ 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] Bootstrapper config file/Answer file
Hi all, I have been looking everywhere to find the answer to this question. Does WIX Bootstrapper support the use of an xml config file or answer file to obtain the chain of packages to install? I have seen bootstrapper.confg files and some other information but I feel like I am going down rabbit holes. I would just like to have a single setup.exe file that can utilize a managed configuration file so that the bootstrapper doesn't have to be recompiled when there are version updates. Is it possible? Thank you, J -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper config file/Answer file
My experiences is the bootstrapper captures info on the signature or hash of files it is to manage installation of. You have to assemble the content, up the bootstrapper version number and re-compile every time any of the bundles change. This is a good thing as it ensures cohesion of release content. -Original Message- From: Jeremiahf [mailto:jeremi...@gmail.com] Sent: Thursday, April 03, 2014 2:12 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Bootstrapper config file/Answer file Hi all, I have been looking everywhere to find the answer to this question. Does WIX Bootstrapper support the use of an xml config file or answer file to obtain the chain of packages to install? I have seen bootstrapper.confg files and some other information but I feel like I am going down rabbit holes. I would just like to have a single setup.exe file that can utilize a managed configuration file so that the bootstrapper doesn't have to be recompiled when there are version updates. Is it possible? Thank you, J -- ___ 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] Bootstrapper config file/Answer file
Thank you for the quick feedback. On Thu, Apr 3, 2014 at 4:24 PM, Wheeler, Blaine (DSHS/DCS) bwhee...@dshs.wa.gov wrote: My experiences is the bootstrapper captures info on the signature or hash of files it is to manage installation of. You have to assemble the content, up the bootstrapper version number and re-compile every time any of the bundles change. This is a good thing as it ensures cohesion of release content. -Original Message- From: Jeremiahf [mailto:jeremi...@gmail.com] Sent: Thursday, April 03, 2014 2:12 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Bootstrapper config file/Answer file Hi all, I have been looking everywhere to find the answer to this question. Does WIX Bootstrapper support the use of an xml config file or answer file to obtain the chain of packages to install? I have seen bootstrapper.confg files and some other information but I feel like I am going down rabbit holes. I would just like to have a single setup.exe file that can utilize a managed configuration file so that the bootstrapper doesn't have to be recompiled when there are version updates. Is it possible? Thank you, J -- ___ 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 -- They may forget what you said but they will never forget how you made them feel. -- Anonymous -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] bootstrapper project failing
I created a simple bootstrapper project to pre-install SQLSysClrTypes.msi but I am getting Failed to CreateProcess on path. I really appreciate for your help. Applying execute package: SqlSystemTypes, action: Install, path: Error 0x800700c1: Failed to CreateProcess on path: Error 0x800700c1: Failed to configure per-user EXE package. Bundle Name=Bootstrapper2 Version=1.0.0.0 Manufacturer=Test UpgradeCode=5c117d93-8ca5-4791-8e25-c02c9dda4fdf BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.RtfLicense / Chain PackageGroupRef Id=SqlSystemTypes/ MsiPackage Id=Testpackage DisplayInternalUI=yes Vital=yes SourceFile=Resource\Setup.msi/ /Chain /Bundle Fragment util:RegistrySearch Root=HKLM Key=SOFTWARE\Microsoft\Microsoft SQL Server\RefCount\SQLSysClrTypes Result=exists Variable=SqlSystemClrTypes Win64=yes/ PackageGroup Id=SqlSystemTypes ExePackage Id=SqlSystemTypes DisplayName=Microsoft SQL Server System CLR TypesCache=yesCompressed=yes PerMachine=defaultPermanent=yesVital=yesSourceFile=Resource\SQLSysClrTypes.msi InstallCommand=/passive /norestart DetectCondition=SqlSystemClrTypes / /PackageGroup /Fragment -- 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] bootstrapper project failing
Don't use ExePackage for a MSI, use MsiPackage. -Original Message- From: Getye Tesfaye [mailto:getyetesf...@yahoo.com] Sent: Tuesday, March 18, 2014 4:13 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] bootstrapper project failing I created a simple bootstrapper project to pre-install SQLSysClrTypes.msi but I am getting Failed to CreateProcess on path. I really appreciate for your help. Applying execute package: SqlSystemTypes, action: Install, path: Error 0x800700c1: Failed to CreateProcess on path: Error 0x800700c1: Failed to configure per-user EXE package. Bundle Name=Bootstrapper2 Version=1.0.0.0 Manufacturer=Test UpgradeCode=5c117d93-8ca5-4791-8e25-c02c9dda4fdf BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.RtfLicense / Chain PackageGroupRef Id=SqlSystemTypes/ MsiPackage Id=Testpackage DisplayInternalUI=yes Vital=yes SourceFile=Resource\Setup.msi/ /Chain /Bundle Fragment util:RegistrySearch Root=HKLM Key=SOFTWARE\Microsoft\Microsoft SQL Server\RefCount\SQLSysClrTypes Result=exists Variable=SqlSystemClrTypes Win64=yes/ PackageGroup Id=SqlSystemTypes ExePackage Id=SqlSystemTypes DisplayName=Microsoft SQL Server System CLR TypesCache=yesCompressed=yes PerMachine=defaultPermanent=yesVital=yesSourceFile=Resource\SQLSysClrTypes.msi InstallCommand=/passive /norestart DetectCondition=SqlSystemClrTypes / /PackageGroup /Fragment -- 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] bootstrapper project failing
Thank you. That saves me a lot of time. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/bootstrapper-project-failing-tp7593519p7593527.html Sent from the wix-users mailing list archive at Nabble.com. -- 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] Bootstrapper question
remove the UI from genius and create one with your own MBA. Use these properties, and send them down to msi's -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-question-tp7593254p7593478.html Sent from the wix-users mailing list archive at Nabble.com. -- 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] Bootstrapper question
What is the recommended way for MSIs to communicate with each other? For example, the Bootstrapper executes a chain of MSIs where the first MSI displays a custom dialog which sets a property according to what radio button the user selected. Later, depending on the user's selection in the MSI's dialog, the Bootstrapper needs to select one of two different third party MSIs. Would the correct way to do this be to put the custom dialog up in the Bootstrapper? I guess another option would be to copy and rename the correct third party MSI to, say Generic.msi, so the Bootstrapper could just execute Generic.msi without having to make a decision (yuk). Please let me know your thoughts on this, as maybe I am way off base. (The reason for all this is that I am trying to port a 15-year old evolution of a monster application from InstallShield 6.0 to WiX, and am just learning WiX/MSI. Just started working here and this is my first assignment:) Thanks in advance. -Original Message- From: Rob Mensching [mailto:r...@firegiant.com] Sent: Monday, March 10, 2014 3:26 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper question No. There is no way for Packages to communicate Properties back to the Bundle. ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -Original Message- From: Scott Moyer [mailto:scott.mo...@appliedvision.com] Sent: Monday, March 10, 2014 11:58 AM To: 'WiX-users@lists.sourceforge.net' Subject: [WiX-users] Bootstrapper question Does anyone know if a Bundle/Chain can access a public property from a bundled msi? In the following example the CAMERATYPE property is set in Genius.msi ... ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Bundle Name=Genius Version=1.0.0 UpgradeCode=8feba949-46b1-4b33-9834-879478aaea32 DisableModify=yes BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.HyperlinkLicense / WixVariable Id=WixStdbaLicenseUrl Value= / Chain MsiPackage SourceFile=Genius.msi / MsiPackage SourceFile=Basler.msi InstallCondition=CAMERATYPE = quot;Baslerquot; / /Chain /Bundle /Wix Thanks! NOTICE: The information contained in this electronic mail transmission is intended by Applied Vision Corporation and its affiliates for the sole use of the named individual or entity to which it is directed, and may contain confidential information and/or trade secrets. This electronic mail is not intended for transmission to, or receipt by, anyone other than the named addressee (or a person authorized to deliver it to the named addressee). This electronic mail should not be copied or forwarded to any unauthorized persons. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email or by calling Applied Vision Corporation at 330.926., so that our address record can be corrected. -- 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 NOTICE: The information contained in this electronic mail transmission is intended by Applied Vision Corporation and its affiliates for the sole use of the named individual or entity to which it is directed, and may contain confidential information and/or trade secrets. This electronic mail is not intended for transmission to, or receipt by, anyone other than the named addressee (or a person authorized to deliver it to the named addressee). This electronic mail should not be copied or forwarded to any unauthorized persons. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email or by calling
Re: [WiX-users] Bootstrapper question
MSI's are standalone packages. If you need to tie them together, do it with Burn/Bundle and a custom BA, so you can pass the property down to each MSI that needs it. Not only is this the most robust way, it's the preferred way of doing it. Using DisplayInternalUI is not recommended as it degrades the user experience (choppy installs as there are several different UI's with different look and feel). -Original Message- From: Scott Moyer [mailto:scott.mo...@appliedvision.com] Sent: Thursday, March 13, 2014 9:44 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper question What is the recommended way for MSIs to communicate with each other? For example, the Bootstrapper executes a chain of MSIs where the first MSI displays a custom dialog which sets a property according to what radio button the user selected. Later, depending on the user's selection in the MSI's dialog, the Bootstrapper needs to select one of two different third party MSIs. Would the correct way to do this be to put the custom dialog up in the Bootstrapper? I guess another option would be to copy and rename the correct third party MSI to, say Generic.msi, so the Bootstrapper could just execute Generic.msi without having to make a decision (yuk). Please let me know your thoughts on this, as maybe I am way off base. (The reason for all this is that I am trying to port a 15-year old evolution of a monster application from InstallShield 6.0 to WiX, and am just learning WiX/MSI. Just started working here and this is my first assignment:) Thanks in advance. -Original Message- From: Rob Mensching [mailto:r...@firegiant.com] Sent: Monday, March 10, 2014 3:26 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper question No. There is no way for Packages to communicate Properties back to the Bundle. ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -Original Message- From: Scott Moyer [mailto:scott.mo...@appliedvision.com] Sent: Monday, March 10, 2014 11:58 AM To: 'WiX-users@lists.sourceforge.net' Subject: [WiX-users] Bootstrapper question Does anyone know if a Bundle/Chain can access a public property from a bundled msi? In the following example the CAMERATYPE property is set in Genius.msi ... ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Bundle Name=Genius Version=1.0.0 UpgradeCode=8feba949-46b1-4b33-9834-879478aaea32 DisableModify=yes BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.HyperlinkLicense / WixVariable Id=WixStdbaLicenseUrl Value= / Chain MsiPackage SourceFile=Genius.msi / MsiPackage SourceFile=Basler.msi InstallCondition=CAMERATYPE = quot;Baslerquot; / /Chain /Bundle /Wix Thanks! NOTICE: The information contained in this electronic mail transmission is intended by Applied Vision Corporation and its affiliates for the sole use of the named individual or entity to which it is directed, and may contain confidential information and/or trade secrets. This electronic mail is not intended for transmission to, or receipt by, anyone other than the named addressee (or a person authorized to deliver it to the named addressee). This electronic mail should not be copied or forwarded to any unauthorized persons. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email or by calling Applied Vision Corporation at 330.926., so that our address record can be corrected. -- 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 NOTICE: The information contained in this electronic mail transmission is intended by Applied Vision
[WiX-users] Bootstrapper question
Does anyone know if a Bundle/Chain can access a public property from a bundled msi? In the following example the CAMERATYPE property is set in Genius.msi ... ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Bundle Name=Genius Version=1.0.0 UpgradeCode=8feba949-46b1-4b33-9834-879478aaea32 DisableModify=yes BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.HyperlinkLicense / WixVariable Id=WixStdbaLicenseUrl Value= / Chain MsiPackage SourceFile=Genius.msi / MsiPackage SourceFile=Basler.msi InstallCondition=CAMERATYPE = quot;Baslerquot; / /Chain /Bundle /Wix Thanks! NOTICE: The information contained in this electronic mail transmission is intended by Applied Vision Corporation and its affiliates for the sole use of the named individual or entity to which it is directed, and may contain confidential information and/or trade secrets. This electronic mail is not intended for transmission to, or receipt by, anyone other than the named addressee (or a person authorized to deliver it to the named addressee). This electronic mail should not be copied or forwarded to any unauthorized persons. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email or by calling Applied Vision Corporation at 330.926., so that our address record can be corrected. -- 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] Bootstrapper question
No. There is no way for Packages to communicate Properties back to the Bundle. ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -Original Message- From: Scott Moyer [mailto:scott.mo...@appliedvision.com] Sent: Monday, March 10, 2014 11:58 AM To: 'WiX-users@lists.sourceforge.net' Subject: [WiX-users] Bootstrapper question Does anyone know if a Bundle/Chain can access a public property from a bundled msi? In the following example the CAMERATYPE property is set in Genius.msi ... ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Bundle Name=Genius Version=1.0.0 UpgradeCode=8feba949-46b1-4b33-9834-879478aaea32 DisableModify=yes BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.HyperlinkLicense / WixVariable Id=WixStdbaLicenseUrl Value= / Chain MsiPackage SourceFile=Genius.msi / MsiPackage SourceFile=Basler.msi InstallCondition=CAMERATYPE = quot;Baslerquot; / /Chain /Bundle /Wix Thanks! NOTICE: The information contained in this electronic mail transmission is intended by Applied Vision Corporation and its affiliates for the sole use of the named individual or entity to which it is directed, and may contain confidential information and/or trade secrets. This electronic mail is not intended for transmission to, or receipt by, anyone other than the named addressee (or a person authorized to deliver it to the named addressee). This electronic mail should not be copied or forwarded to any unauthorized persons. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email or by calling Applied Vision Corporation at 330.926., so that our address record can be corrected. -- 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] Bootstrapper question
I fail to see how this would be useful, but I don't think there is anything today in place. The reason I question why you would do it is the condition would end up being a constant expression (either always being true or always being false). To me it seems like you'd want a BA with custom code for detecting/prompting for a camera type, and from there property drive which satellite MSI's to install. I could also envision a user having more than one camera so they may need a UI with check boxes or a checked list box to select the possible cameras. What you can do is pass property values to a MSI from the Bundle via MsiPackage... MsiProperty Name=CAMERATYPE Value=Basler / /MsiPackage That being said, you could create your own extensions to do this but I still fail at seeing how it could be useful. -Original Message- From: Scott Moyer [mailto:scott.mo...@appliedvision.com] Sent: Monday, March 10, 2014 1:58 PM To: 'WiX-users@lists.sourceforge.net' Subject: [WiX-users] Bootstrapper question Does anyone know if a Bundle/Chain can access a public property from a bundled msi? In the following example the CAMERATYPE property is set in Genius.msi ... ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Bundle Name=Genius Version=1.0.0 UpgradeCode=8feba949-46b1-4b33-9834-879478aaea32 DisableModify=yes BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.HyperlinkLicense / WixVariable Id=WixStdbaLicenseUrl Value= / Chain MsiPackage SourceFile=Genius.msi / MsiPackage SourceFile=Basler.msi InstallCondition=CAMERATYPE = quot;Baslerquot; / /Chain /Bundle /Wix Thanks! NOTICE: The information contained in this electronic mail transmission is intended by Applied Vision Corporation and its affiliates for the sole use of the named individual or entity to which it is directed, and may contain confidential information and/or trade secrets. This electronic mail is not intended for transmission to, or receipt by, anyone other than the named addressee (or a person authorized to deliver it to the named addressee). This electronic mail should not be copied or forwarded to any unauthorized persons. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email or by calling Applied Vision Corporation at 330.926., so that our address record can be corrected. -- 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] Bootstrapper question
There is a custom UI in Genius.msi that prompts for and sets the camera type property (as well as the number of cameras). I wonder if that ui can be moved from the MSI up to the BA? -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Monday, March 10, 2014 3:27 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper question I fail to see how this would be useful, but I don't think there is anything today in place. The reason I question why you would do it is the condition would end up being a constant expression (either always being true or always being false). To me it seems like you'd want a BA with custom code for detecting/prompting for a camera type, and from there property drive which satellite MSI's to install. I could also envision a user having more than one camera so they may need a UI with check boxes or a checked list box to select the possible cameras. What you can do is pass property values to a MSI from the Bundle via MsiPackage... MsiProperty Name=CAMERATYPE Value=Basler / /MsiPackage That being said, you could create your own extensions to do this but I still fail at seeing how it could be useful. -Original Message- From: Scott Moyer [mailto:scott.mo...@appliedvision.com] Sent: Monday, March 10, 2014 1:58 PM To: 'WiX-users@lists.sourceforge.net' Subject: [WiX-users] Bootstrapper question Does anyone know if a Bundle/Chain can access a public property from a bundled msi? In the following example the CAMERATYPE property is set in Genius.msi ... ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Bundle Name=Genius Version=1.0.0 UpgradeCode=8feba949-46b1-4b33-9834-879478aaea32 DisableModify=yes BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.HyperlinkLicense / WixVariable Id=WixStdbaLicenseUrl Value= / Chain MsiPackage SourceFile=Genius.msi / MsiPackage SourceFile=Basler.msi InstallCondition=CAMERATYPE = quot;Baslerquot; / /Chain /Bundle /Wix Thanks! NOTICE: The information contained in this electronic mail transmission is intended by Applied Vision Corporation and its affiliates for the sole use of the named individual or entity to which it is directed, and may contain confidential information and/or trade secrets. This electronic mail is not intended for transmission to, or receipt by, anyone other than the named addressee (or a person authorized to deliver it to the named addressee). This electronic mail should not be copied or forwarded to any unauthorized persons. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email or by calling Applied Vision Corporation at 330.926., so that our address record can be corrected. -- 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 NOTICE: The information contained in this electronic mail transmission is intended by Applied Vision Corporation and its affiliates for the sole use of the named individual or entity to which it is directed, and may contain confidential information and/or trade secrets. This electronic mail is not intended for transmission to, or receipt by, anyone other than the named addressee (or a person authorized to deliver it to the named addressee). This electronic mail should not be copied or forwarded to any unauthorized persons. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email or by calling Applied Vision Corporation at 330.926., so that our address record can be corrected. -- Learn Graph
Re: [WiX-users] Bootstrapper for .NET framework 4.0 install does not work properly
Hi Phil, After changing the type of the bootstrapper to output type .exe i am not facing the error below. Thanks for the pointer. But on the trying to install using the bootstrapper .exe created the .NEt framework does not get installed. It shows the message Microsoft .NET framework setup but then goes on to show the popup as below that shows the various usage options: Setup[switches] The other .msi package though does get installed. For all the packages i have set compressed=yes. I have changed the detect condition to as below from earlier for the .Net framework .exe package. Below is the same: PackageGroup Id=Netfx4Full ExePackage Id=Netfx4Full DisplayName=Microsoft .NET Framework 4.0 Compressed=yes Cache=yes PerMachine=yes Permanent=yes Protocol=netfx4 Vital=yes SourceFile=D:\Installables\.NET Framework 4\dotNetFx40_Full_x86_x64.exe InstallCommand=Setup /passive /norestart /ChainingPackage /q RepairCommand=/passive /norestart /repair /ChainingPackage /q UninstallCommand=/uninstall /passive /norestart /ChainingPackage /q DetectCondition=Netfx4FullVersion AND Netfx4x64FullVersion/ /PackageGroup In the log file also i can find that the Detectcondition evaluates to false. Attached is the same. But the .NET framework does start the installation. Could you please provide some help on this as this is urgent for me. Regards, Suvra Jyoti On 28-02-2014 19:42, Phill Hogland wrote: A project that creates a bootstrapper (and uses the Bundle element) should produce an EXE, and not an msi. An MSI does not have the appropriate 'entry point' which is what the error indicates. You might find it easier to use the built-in support for installing .Net 4.0. In my bootstrapper (exe) project I add: Bundle . BootstrapperApplicationRef Id=ManagedBootstrapperApplicationHost .. other files WixVariable Id=WixMbaPrereqPackageId Value=Netfx4ClientRedist / WixVariable Id=WixMbaPrereqLicenseUrl Value=NetfxLicense.rtf/ /BootstrapperApplicationRef /Bundle or look at: http://wixtoolset.org/documentation/manual/v3/howtos/redistributables_and_install_checks/install_dotnet.html you could also get a lot of information from src\ext\NetFxExtension\wixlib -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-for-NET-framework-4-0-install-does-not-work-properly-tp7593004p7593012.html Sent from the wix-users mailing list archive at Nabble.com. -- Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users [13B8:1304][2014-03-03T12:39:55]i001: Burn v3.8.1128.0, Windows v6.1 (Build 7601: Service Pack 1), path: D:\.net Framwork\PipelineOptimizerEngineInstallBootstrapper_06.00.00_3422.exe, cmdline: '' [13B8:1304][2014-03-03T12:39:56]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\rakeshk\AppData\Local\Temp\OptimizerBootstrapper_20140303123956.log' [13B8:1304][2014-03-03T12:39:56]i000: Setting string variable 'WixBundleOriginalSource' to value 'D:\.net Framwork\PipelineOptimizerEngineInstallBootstrapper_06.00.00_3422.exe' [13B8:1304][2014-03-03T12:39:56]i000: Setting string variable 'WixBundleName' to value 'OptimizerBootstrapper' [13B8:1304][2014-03-03T12:39:56]i100: Detect begin, 2 packages [13B8:1304][2014-03-03T12:39:56]i000: Registry key not found. Key = 'SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Full' [13B8:1304][2014-03-03T12:39:56]i000: Registry key not found. Key = 'SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Full' [13B8:1304][2014-03-03T12:39:56]i052: Condition 'Netfx4FullVersion AND Netfx4x64FullVersion' evaluates to false. [13B8:1304][2014-03-03T12:39:56]i101: Detected package: Netfx4Full, state: Absent, cached: None [13B8:1304][2014-03-03T12:39:56]i101: Detected package: PipielineOptimizerEngineApp, state: Absent, cached: None [13B8:1304][2014-03-03T12:39:56]i199: Detect complete, result: 0x0 [13B8:0C7C][2014-03-03T12:39:58]i000: Setting numeric variable 'EulaAcceptCheckbox' to value 1 [13B8:1304][2014-03-03T12:39:58]i200: Plan begin, 2 packages, action: Install [13B8:1304][2014-03-03T12:39:58]w321: Skipping dependency registration on package with no dependency providers: Netfx4Full [13B8:1304][2014-03-03T12:39:58]i000:
[WiX-users] Bootstrapper for .NET framework 4.0 install does not work properly
Hi All,
I want to create a bootstrapper for .NET framework 4.0 install as a
prerequisite for my application if it is not already present. Below is
how i designed my Bundle in which i am referencing my other WIX project:
?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;
Bundle Name=OptimizerBootstrapper Version=1.0.0.0
Manufacturer=SuvraJyoti
UpgradeCode={1A9F7A91-A9F9-428E-ACD0-5D48621A0C83}
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.RtfLicense /
Chain
!-- .NET Framework --
PackageGroupRef Id=Netfx4Full/
!-- Install Application --
MsiPackage Id=PipielineOptimizerEngineApp
SourceFile=$(var.PipelineOptimizerEngineInstallPath)/
/Chain
/Bundle
Fragment
!-- Check for .NET 4.0 --
util:RegistrySearch Root=HKLM
Key=SOFTWARE\Microsoft\Net Framework
Setup\NDP\v4\Full
Value=Version
Variable=Netfx4FullVersion /
util:RegistrySearch Root=HKLM
Key=SOFTWARE\Microsoft\Net Framework
Setup\NDP\v4\Full
Value=Version
Variable=Netfx4x64FullVersion
Win64=yes /
!-- Install .NEt 4.0 --
PackageGroup Id=Netfx4Full
ExePackage Id=Netfx4Full
DisplayName=Microsoft .NET Framework 4.0
Compressed=no
Cache=yes
PerMachine=yes
Permanent=yes
Protocol=netfx4
Vital=yes
SourceFile=D:\Installables\.NET Framework
4\dotNetFx40_Full_x86_x64.exe
InstallCommand=/passive /norestart /ChainingPackage
RepairCommand=/passive /norestart /repair
/ChainingPackage /q
UninstallCommand=/uninstall /passive /norestart
/ChainingPackage /q
DetectCondition=Netfx4FullVersion AND (NOT
VersionNT64 OR Netfx4x64FullVersion) /
/PackageGroup
/Fragment
/Wix
I am getting the below warning as well:
/c:\CompletedBuilds\PLO\OptimizerBundle.wixobj : warning LGHT1109 :
Found mismatched entry point Bundle. Expected Product for specified
output package type.msi./
Also below are all the candle and light commands that i am using:
%WiXDir%\candle -ext WixUIExtension -out %outputPath%\ -I
.\TortInstaller\TortInstall.wxs %outputPath%\db.wxs
%outputPath%\data.wxs %outputPath%\engine.wxs %outputPath%\security.wxs
%outputPath%\gui.wxs -trace
%WiXDir%\light -ext WixUIExtension -out
%outputPath%\PipelineOptimizerEngineInstall_%VERSION%_%BUILD%.msi
%outputPath%\TortInstall.wixobj pause
::Referencing the BUNDLE here
%WiXDir%\candle -ext WixBalExtension -ext WixUtilExtension -out
%outputPath%\
-dPipelineOptimizerEngineInstallPath=%outputPath%\PipelineOptimizerEngineInstall_%VERSION%_%BUILD%.msi
-I .\TortInstaller\OptimizerBundle.wxs -trace
%WiXDir%\light -ext WixBalExtension -ext WixUtilExtension -out
%outputPath%\PipelineOptimizerEngineInstallBootstrapper_%VERSION%_%BUILD%.msi
%outputPath%\OptimizerBundle.wixobj
The PipelineOptimizerEngineInstallBootstrapper.msi that is created does
not seem to work. My system does have .NET framework 4.0 but that should
not mean that i should be getting the message as below on clicking the
Bootstrapper msi:
/The installation package could not be opened.Contact the application
vendor to verify that this is a valid Windows installer package/
Also i get to see that the dotNetFx40_Full_x86_x64.exe is produced in
the output path where the installers are ouput. Should this happen at all.
Please help me in getting these to work.
Regards,
Suvra Jyoti
--
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper for .NET framework 4.0 install does not work properly
A project that creates a bootstrapper (and uses the Bundle element) should produce an EXE, and not an msi. An MSI does not have the appropriate 'entry point' which is what the error indicates. You might find it easier to use the built-in support for installing .Net 4.0. In my bootstrapper (exe) project I add: Bundle . BootstrapperApplicationRef Id=ManagedBootstrapperApplicationHost .. other files WixVariable Id=WixMbaPrereqPackageId Value=Netfx4ClientRedist / WixVariable Id=WixMbaPrereqLicenseUrl Value=NetfxLicense.rtf/ /BootstrapperApplicationRef /Bundle or look at: http://wixtoolset.org/documentation/manual/v3/howtos/redistributables_and_install_checks/install_dotnet.html you could also get a lot of information from src\ext\NetFxExtension\wixlib -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-for-NET-framework-4-0-install-does-not-work-properly-tp7593004p7593012.html Sent from the wix-users mailing list archive at Nabble.com. -- Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper inherited from WixBA
In your BootstrapperCore.config, this is wrong:
host assemblyName=CustomBootstrapperApplication
The assemblyName attribute needs to have your assembly name, CustomBA3. The
config tells Burn which dll has your BA, then the dll's manifest tells burn
which class is your BA.
Also looking at this guide
http://blogs.msdn.com/b/heaths/archive/2011/10/28/introducing-managed-bootstrapper-applications.aspx,
the supportedFramework elements shouldn't be inside the host element.
Sean Hall
From: clacha...@gmail.com
Date: Fri, 10 Jan 2014 18:12:23 +0100
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Bootstrapper inherited from WixBA
Hi all,
We are trying to generate a Bootstrapper Application
CustomBootstrapperApplication which inheritate from WixBA (which we got
from the sources of Wix 3.8).
***
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using WixToolset.UX;
using System.Windows.Forms;
namespace CustomBA3
{
public class CustomBootstrapperApplication : WixBA
{
protected override void Run()
{
MessageBox.Show(Lets Go);
base.Run();
}
}
}
***
The AssemblyInfo contains
[assembly: BootstrapperApplication(typeof(CustomBootstrapperApplication))]
We have tried different bootstrapperCore.config, as
***
?xml version=1.0 encoding=utf-8 ?
configuration
configSections
sectionGroup name=wix.bootstrapper
type=Microsoft.Tools.WindowsInstallerXml.Bootstrapper.BootstrapperSectionGroup,
BootstrapperCore
section name=host
type=Microsoft.Tools.WindowsInstallerXml.Bootstrapper.HostSection,
BootstrapperCore /
/sectionGroup
/configSections
startup useLegacyV2RuntimeActivationPolicy=true
supportedRuntime version=v4.0 /
/startup
wix.bootstrapper
host assemblyName=CustomBootstrapperApplication
supportedFramework version=v4\Full /
supportedFramework version=v4\Client /
/host
/wix.bootstrapper
/configuration
***
or
using
(...)
sectionGroup name=wix.bootstrapper
type=WixToolset.Bootstrapper.BootstrapperSectionGroup, BootstrapperCore
section name=host type=WixToolset.Bootstrapper.HostSection,
BootstrapperCore /
(...)
Our bootstrapper is defined with
(...)
Bundle Name=Bootstrapper Version=1.0.0.0
Manufacturer=Us UpgradeCode=bccd71e0-acc1-4691-a990-4bc251bdcf3f
BootstrapperApplicationRef Id='ManagedBootstrapperApplicationHost'
Payload SourceFile=..\CustomBA3\Bin\Release\CustomBA3.dll /
Payload Name=BootstrapperCore.config
SourceFile=..\CustomBA3\BootstrapperCore.config/
Payload SourceFile=..\CustomBA3\Bin\Release\BootstrapperCore.dll
/
Payload SourceFile=..\CustomBA3\Bin\Release\WixBA.dll /
Payload
SourceFile=..\CustomBA3\Bin\Release\Microsoft.Deployment.WindowsInstaller.dll/
/BootstrapperApplicationRef
(...)
but unfortunately,
all our tries lead to the following error
[1490:1238][2014-01-09T18:54:13]i001: Burn v3.8.1128.0, Windows v6.2 (Build
9200: Service Pack 0), path:
D:\repository\WebForce\Production\v7.0.0\MI_7.0.0_ServicePacks\InstallerProjects\BootstrapperMI\Bootstrapper\bin\Release\Bootstrapper.exe,
cmdline: ''
[1490:1238][2014-01-09T18:54:13]i000: Setting string variable
'WixBundleLog' to value
'C:\Users\spaes\AppData\Local\Temp\Bootstrapper_20140109185413.log'
[1490:1238][2014-01-09T18:54:13]i000: Setting string variable
'WixBundleOriginalSource' to value
'D:\repository\WebForce\Production\v7.0.0\MI_7.0.0_ServicePacks\InstallerProjects\BootstrapperMI\Bootstrapper\bin\Release\Bootstrapper.exe'
[1490:1238][2014-01-09T18:54:13]i000: Setting string variable
'WixBundleName' to value 'Bootstrapper'
[1490:1238][2014-01-09T18:54:13]i000: Loading managed bootstrapper
application.
[1490:1238][2014-01-09T18:54:13]e000: Error 0x80131040: Failed to create
the managed bootstrapper application.
[1490:1238][2014-01-09T18:54:13]e000: Error 0x80131040: Failed to create UX.
[1490:1238][2014-01-09T18:54:13]e000: Error 0x80131040: Failed to load UX.
[1490:1238][2014-01-09T18:54:13]e000: Error 0x80131040: Failed while
running
[1490:1238][2014-01-09T18:54:13]i410: Variable: WixBundleAction = 4
[1490:1238][2014-01-09T18:54:13]i410: Variable: WixBundleElevated = 0
[1490:1238][2014-01-09T18:54:13]i410: Variable: WixBundleLog =
C:\Users\spaes\AppData\Local\Temp\Bootstrapper_20140109185413.log
[1490:1238][2014-01-09T18:54:13]i410: Variable: WixBundleManufacturer = Us
[1490:1238][2014-01-09T18:54:13]i410
[WiX-users] Bootstrapper inherited from WixBA
Hi all,
We are trying to generate a Bootstrapper Application
CustomBootstrapperApplication which inheritate from WixBA (which we got
from the sources of Wix 3.8).
***
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using WixToolset.UX;
using System.Windows.Forms;
namespace CustomBA3
{
public class CustomBootstrapperApplication : WixBA
{
protected override void Run()
{
MessageBox.Show(Lets Go);
base.Run();
}
}
}
***
The AssemblyInfo contains
[assembly: BootstrapperApplication(typeof(CustomBootstrapperApplication))]
We have tried different bootstrapperCore.config, as
***
?xml version=1.0 encoding=utf-8 ?
configuration
configSections
sectionGroup name=wix.bootstrapper
type=Microsoft.Tools.WindowsInstallerXml.Bootstrapper.BootstrapperSectionGroup,
BootstrapperCore
section name=host
type=Microsoft.Tools.WindowsInstallerXml.Bootstrapper.HostSection,
BootstrapperCore /
/sectionGroup
/configSections
startup useLegacyV2RuntimeActivationPolicy=true
supportedRuntime version=v4.0 /
/startup
wix.bootstrapper
host assemblyName=CustomBootstrapperApplication
supportedFramework version=v4\Full /
supportedFramework version=v4\Client /
/host
/wix.bootstrapper
/configuration
***
or
using
(...)
sectionGroup name=wix.bootstrapper
type=WixToolset.Bootstrapper.BootstrapperSectionGroup, BootstrapperCore
section name=host type=WixToolset.Bootstrapper.HostSection,
BootstrapperCore /
(...)
Our bootstrapper is defined with
(...)
Bundle Name=Bootstrapper Version=1.0.0.0
Manufacturer=Us UpgradeCode=bccd71e0-acc1-4691-a990-4bc251bdcf3f
BootstrapperApplicationRef Id='ManagedBootstrapperApplicationHost'
Payload SourceFile=..\CustomBA3\Bin\Release\CustomBA3.dll /
Payload Name=BootstrapperCore.config
SourceFile=..\CustomBA3\BootstrapperCore.config/
Payload SourceFile=..\CustomBA3\Bin\Release\BootstrapperCore.dll
/
Payload SourceFile=..\CustomBA3\Bin\Release\WixBA.dll /
Payload
SourceFile=..\CustomBA3\Bin\Release\Microsoft.Deployment.WindowsInstaller.dll/
/BootstrapperApplicationRef
(...)
but unfortunately,
all our tries lead to the following error
[1490:1238][2014-01-09T18:54:13]i001: Burn v3.8.1128.0, Windows v6.2 (Build
9200: Service Pack 0), path:
D:\repository\WebForce\Production\v7.0.0\MI_7.0.0_ServicePacks\InstallerProjects\BootstrapperMI\Bootstrapper\bin\Release\Bootstrapper.exe,
cmdline: ''
[1490:1238][2014-01-09T18:54:13]i000: Setting string variable
'WixBundleLog' to value
'C:\Users\spaes\AppData\Local\Temp\Bootstrapper_20140109185413.log'
[1490:1238][2014-01-09T18:54:13]i000: Setting string variable
'WixBundleOriginalSource' to value
'D:\repository\WebForce\Production\v7.0.0\MI_7.0.0_ServicePacks\InstallerProjects\BootstrapperMI\Bootstrapper\bin\Release\Bootstrapper.exe'
[1490:1238][2014-01-09T18:54:13]i000: Setting string variable
'WixBundleName' to value 'Bootstrapper'
[1490:1238][2014-01-09T18:54:13]i000: Loading managed bootstrapper
application.
[1490:1238][2014-01-09T18:54:13]e000: Error 0x80131040: Failed to create
the managed bootstrapper application.
[1490:1238][2014-01-09T18:54:13]e000: Error 0x80131040: Failed to create UX.
[1490:1238][2014-01-09T18:54:13]e000: Error 0x80131040: Failed to load UX.
[1490:1238][2014-01-09T18:54:13]e000: Error 0x80131040: Failed while
running
[1490:1238][2014-01-09T18:54:13]i410: Variable: WixBundleAction = 4
[1490:1238][2014-01-09T18:54:13]i410: Variable: WixBundleElevated = 0
[1490:1238][2014-01-09T18:54:13]i410: Variable: WixBundleLog =
C:\Users\spaes\AppData\Local\Temp\Bootstrapper_20140109185413.log
[1490:1238][2014-01-09T18:54:13]i410: Variable: WixBundleManufacturer = Us
[1490:1238][2014-01-09T18:54:13]i410: Variable: WixBundleName = Bootstrapper
[1490:1238][2014-01-09T18:54:13]i410: Variable: WixBundleOriginalSource =
D:\repository\WebForce\Production\v7.0.0\MI_7.0.0_ServicePacks\InstallerProjects\BootstrapperMI\Bootstrapper\bin\Release\Bootstrapper.exe
[1490:1238][2014-01-09T18:54:13]i410: Variable: WixBundleProviderKey =
{22fc06d5-55ec-4512-9a67-f12297e8920b}
[1490:1238][2014-01-09T18:54:13]i410: Variable: WixBundleTag =
[1490:1238][2014-01-09T18:54:13]i410: Variable: WixBundleVersion = 1.0.0.0
[1490:1238][2014-01-09T18:54:13]e000: Error 0x80131040: Failed to run
per-user mode.
[1490:1238][2014-01-09T18:54:13]i007: Exit code: 0x80131040, restarting: No
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink
[WiX-users] Bootstrapper Theme Files and MS-RL
Hi, I'm currently building a bootstrapper application where I had to modify the RtfTheme.xml very slightly (basically add a checkbox) to fit the purposes of my specific installer. Since this application is open-source (MIT license) and I also include all the scripts necessary to generate the installer, I was wondering under what terms I should include the modified RtfTheme.xml in my repository. Are modifications of individual theme files considered a derived work? Should I isolate that specific file inside a folder alongside the MS-RL license text? Let me know what you guys feel like. My feeling is the way WiX uses the MS-RL, modified theme files wouldn't be a derived work (it's not really a contribution to WiX, but really just a quick hack for my own application). It also seems they exist to be modified exactly in this way, but nevertheless I'd like to double-check before I push everything into the repository. Thanks (modifying the Burn UI was insanely easy by the way, thanks again for the great work)! Gonçalo -- 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
