[WiX-users] Disable logging in Burn
Hi everyone, after Rob has been so kind to point me to the log element to disable burn-logging, I have added Log Disable=yes / and now the log of burn in the %temp% directory vanishes. This created some unwanted side-effect though: In the local directory where my bootstrapper was located, for each MSI included in it a file was created which was named: (null)_0_MSI_PACKAGE_ID.(null) So disabling burn-logging seems not to disable the logging of each MSI. Is this by design, or just my mistake? Best regards, Tobias -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Disable logging in Burn
That sounds like a bug in Burn. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Tobias Erichsen [mailto:i...@tobias-erichsen.de] Sent: Friday, October 24, 2014 6:54 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Disable logging in Burn Hi everyone, after Rob has been so kind to point me to the log element to disable burn-logging, I have added Log Disable=yes / and now the log of burn in the %temp% directory vanishes. This created some unwanted side-effect though: In the local directory where my bootstrapper was located, for each MSI included in it a file was created which was named: (null)_0_MSI_PACKAGE_ID.(null) So disabling burn-logging seems not to disable the logging of each MSI. Is this by design, or just my mistake? Best regards, Tobias -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Display messages from Custom Action in ProgressDlg?
Is it possible to display messages from a custom action in the ProgressDlg (the screen with the progress bar)? I would like to display the names of SQL scripts as they are running. I have to do this in a Custom Action as there are other things to do as the scripts are executed. Brian If you can't explain it simply, you don't understand it well enough. - Albert Einstein -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Display messages from Custom Action in ProgressDlg?
Yes. I generally follow the pattern of: CustomAction Id=SomeCustomAction . . . . / UI ProgressText Action=SomeCustomAction ![CDATA[SomeCustomAction is doing something]] /ProgressText /UI InstallExecuteSequence Custom Action=SomeCustomAction Before=some_point ![CDATA[your conditions]] /Custom -- 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: Brian Enderle [mailto:bria...@gmail.com] Sent: Friday, October 24, 2014 1:38 PM To: WiX Users Subject: [WiX-users] Display messages from Custom Action in ProgressDlg? Is it possible to display messages from a custom action in the ProgressDlg (the screen with the progress bar)? I would like to display the names of SQL scripts as they are running. I have to do this in a Custom Action as there are other things to do as the scripts are executed. Brian If you can't explain it simply, you don't understand it well enough. - Albert Einstein -- ___ 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. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Disable logging in Burn
Unless that is a newer feature I'd challenge how burn is disabling logging today. I don't see anywhere where the manifest would be parsing the Log/@disable. If we are going to disable logging, I'd think you'd still want the log attributes in the manifest. Then with a bit of work, we could allow Bundle.exe /lv or the likes to turn it on as needed. The way it sits today, it almost looks like if you put Log/@Disable in your bundle, that there is no way to re-enable it without rebuilding the bundle. -Original Message- From: Rob Mensching [mailto:r...@firegiant.com] Sent: Friday, October 24, 2014 11:37 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Disable logging in Burn That sounds like a bug in Burn. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Tobias Erichsen [mailto:i...@tobias-erichsen.de] Sent: Friday, October 24, 2014 6:54 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Disable logging in Burn Hi everyone, after Rob has been so kind to point me to the log element to disable burn-logging, I have added Log Disable=yes / and now the log of burn in the %temp% directory vanishes. This created some unwanted side-effect though: In the local directory where my bootstrapper was located, for each MSI included in it a file was created which was named: (null)_0_MSI_PACKAGE_ID.(null) So disabling burn-logging seems not to disable the logging of each MSI. Is this by design, or just my mistake? Best regards, Tobias -- ___ 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] Error database does not exist when executing ExecuteSQLStrings
I have an installer that needs to execute a number of sql scripts. For some
reason they are not getting executed and so I receive the above message.
here is my Product.was file..
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:fire=http://schemas.microsoft.com/wix/FirewallExtension;
xmlns:sql=http://schemas.microsoft.com/wix/SqlExtension;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;
Product Id=* Name=Guru Teach Server Installation Language=1033
Version=6.0.4.0 Manufacturer=Guru Dental
UpgradeCode=76c642f5-9ef3-4575-8ce1-05dd36ea4195
Package InstallerVersion=200 Compressed=yes
InstallScope=perMachine Id=* Platform=x86/
MajorUpgrade DowngradeErrorMessage=A newer version of [ProductName] is
already installed. /
Media Id='1' Cabinet='Data.cab' EmbedCab='yes' DiskPrompt='Please
insert DVD #1' /
Property Id='DiskPrompt' Value=Guru Teach Installation [1] /
Property Id=ARPPRODUCTICON Value=guru.ico /
Property Id='CHGFIREWALL' Value='False' Secure='yes'/
UI Id=MyWixUI_Mondo
UIRef Id=WixUI_Mondo /
UIRef Id=WixUI_ErrorProgressText /
DialogRef Id=FirewallDlg /
Publish Dialog=WelcomeDlg Control=Next Event=NewDialog
Value=FirewallDlg Order=11/Publish
Publish Dialog=SetupTypeDlg Control=Back Event=NewDialog
Value=FirewallDlg1/Publish
/UI
sql:SqlDatabase Id=SqlDatabase Database=master Server=localhost
Instance=MVSQLEXPRESS /
Directory Id=TARGETDIR Name=SourceDir
Component Id=RegistryEntries
Guid={E677A056-74D9-4AF0-BC88-A4BE8C237E5E}
RegistryKey Root=HKLM Key=Software\Reality Engineering,
Inc.\Medvisor Dental ForceDeleteOnUninstall=yes
RegistryValue Type=string Name=INSTALLDIR
Value=[APPLICATIONROOTDIR]/
RegistryValue Type=string Name=ProgName Value=Guru
KeyPath=yes/
/RegistryKey
/Component
Directory Id=ProgramFilesFolder
Directory Id=APPLICATIONROOTDIRECTORY Name=Guru
Directory Id=AdditionalFolders
Directory Id=SERVER Name=Server
Directory Id=MANIFESTS Name=Manifests /
Directory Id=MODULES Name=Modules /
/Directory
/Directory
/Directory
/Directory
/Directory
Binary Id=CreateDatabaseSql SourceFile=SQL
Scripts\CreateDatabase.sql /
Binary Id=CreateUsersSql SourceFile=SQL Scripts\CreateUsers.sql /
Binary Id=CreateBaseLineDbSql SourceFile=SQL
Scripts\CreateBaseLineDb.sql /
Binary Id=RemoveOldGuruContentSql SourceFile=SQL
Scripts\RemoveOldGuruContent.sql /
Binary Id=UpgradeSql SourceFile=SQL Scripts\Upgrade.sql /
Binary Id=AddCompleteMediaSql SourceFile=SQL Scripts\Upgrade.sql
/
Binary Id=InstallGuruContentSql SourceFile=SQL
Scripts\InstallGuruContent.sql /
Binary Id=UpdateCustomPlayListSql SourceFile=SQL
Scripts\UpdateCustomPlayList.sql /
Binary Id=InstallFeaturedContentSql SourceFile=SQL
Scripts\InstallFeaturedContent.sql /
DirectoryRef Id=SERVER
Component Id='CreateDtxDataUser.exe'
Guid='26f80392-dcbe-47af-a7e0-d187cbec0e15'
File Id='CreateDtxDataUser.exe' Source='C:\VS
Publish\Guru\ProgramFiles\Guru\Server\CreateDtxDataUser.exe' KeyPath='yes'/
/Component
Component Id='Guru.Server.exe'
Guid='8027388d-0f90-465b-9668-d1388977caaa'
File Id='Guru.Server.exe' Source='C:\VS
Publish\Guru\ProgramFiles\Guru\Server\Guru.Server.exe' KeyPath='yes'/
ServiceInstall
Id=ServiceInstaller
Type=ownProcess
Name=GuruService
DisplayName=Guru Media and Licensing Service
Description=Provides media distribution, data coordination, and
licensing services to the Guru application
Start=auto
Account=[SERVICEACCOUNT]
Password=[SERVICEPASSWORD]
ErrorControl=normal
/
ServiceControl Id=StartService Start=install Stop=both
Remove=uninstall Name=GuruService Wait=yes /
sql:SqlScript Id=CreateDatabase ExecuteOnInstall=yes
BinaryKey=CreateDatabaseSql SqlDb=SqlDatabase/
sql:SqlScript Id=CreateUsers ExecuteOnInstall=yes
BinaryKey=CreateUsersSql SqlDb=SqlDatabase/
sql:SqlScript Id=CreateBaseLineDb ExecuteOnInstall=yes
BinaryKey=CreateBaseLineDbSql SqlDb=SqlDatabase/
sql:SqlScript Id=RemoveOldGuruContent ExecuteOnInstall=yes
BinaryKey=RemoveOldGuruContentSql SqlDb=SqlDatabase/
sql:SqlScript Id=Upgrade ExecuteOnInstall=yes
BinaryKey=UpgradeSql SqlDb=SqlDatabase/
sql:SqlScript Id=AddCompleteMedia ExecuteOnInstall=yes
BinaryKey=AddCompleteMediaSql SqlDb=SqlDatabase/
sql:SqlScript Id=InstallGuruContent ExecuteOnInstall=yes
BinaryKey=InstallGuruContentSql SqlDb=SqlDatabase/
sql:SqlScript Id=UpdateCustomPlayList ExecuteOnInstall=yes
BinaryKey=UpdateCustomPlayListSql SqlDb=SqlDatabase/
sql:SqlScript Id=InstallFeaturedContent ExecuteOnInstall=yes
BinaryKey=InstallFeaturedContentSql SqlDb=SqlDatabase/
Re: [WiX-users] Error database does not exist when executing ExecuteSQLStrings
If you're creating a database using script, I would recommend a separate
component with a sql:SqlDatabase element wrapped around the sql:SqlScript
elements.
--
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: garymonk [mailto:g...@gurudental.com]
Sent: Friday, October 24, 2014 4:06 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Error database does not exist when executing
ExecuteSQLStrings
I have an installer that needs to execute a number of sql scripts. For some
reason they are not getting executed and so I receive the above message.
here is my Product.was file..
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:fire=http://schemas.microsoft.com/wix/FirewallExtension;
xmlns:sql=http://schemas.microsoft.com/wix/SqlExtension;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;
Product Id=* Name=Guru Teach Server Installation Language=1033
Version=6.0.4.0 Manufacturer=Guru Dental
UpgradeCode=76c642f5-9ef3-4575-8ce1-05dd36ea4195
Package InstallerVersion=200 Compressed=yes
InstallScope=perMachine Id=* Platform=x86/
MajorUpgrade DowngradeErrorMessage=A newer version of [ProductName] is
already installed. /
Media Id='1' Cabinet='Data.cab' EmbedCab='yes' DiskPrompt='Please insert
DVD #1' /
Property Id='DiskPrompt' Value=Guru Teach Installation [1] /
Property Id=ARPPRODUCTICON Value=guru.ico /
Property Id='CHGFIREWALL' Value='False' Secure='yes'/
UI Id=MyWixUI_Mondo
UIRef Id=WixUI_Mondo /
UIRef Id=WixUI_ErrorProgressText /
DialogRef Id=FirewallDlg /
Publish Dialog=WelcomeDlg Control=Next Event=NewDialog
Value=FirewallDlg Order=11/Publish
Publish Dialog=SetupTypeDlg Control=Back Event=NewDialog
Value=FirewallDlg1/Publish
/UI
sql:SqlDatabase Id=SqlDatabase Database=master Server=localhost
Instance=MVSQLEXPRESS /
Directory Id=TARGETDIR Name=SourceDir
Component Id=RegistryEntries
Guid={E677A056-74D9-4AF0-BC88-A4BE8C237E5E}
RegistryKey Root=HKLM Key=Software\Reality Engineering,
Inc.\Medvisor Dental ForceDeleteOnUninstall=yes
RegistryValue Type=string Name=INSTALLDIR
Value=[APPLICATIONROOTDIR]/
RegistryValue Type=string Name=ProgName Value=Guru
KeyPath=yes/
/RegistryKey
/Component
Directory Id=ProgramFilesFolder
Directory Id=APPLICATIONROOTDIRECTORY Name=Guru
Directory Id=AdditionalFolders
Directory Id=SERVER Name=Server
Directory Id=MANIFESTS Name=Manifests /
Directory Id=MODULES Name=Modules /
/Directory
/Directory
/Directory
/Directory
/Directory
Binary Id=CreateDatabaseSql SourceFile=SQL Scripts\CreateDatabase.sql
/
Binary Id=CreateUsersSql SourceFile=SQL Scripts\CreateUsers.sql /
Binary Id=CreateBaseLineDbSql SourceFile=SQL
Scripts\CreateBaseLineDb.sql /
Binary Id=RemoveOldGuruContentSql SourceFile=SQL
Scripts\RemoveOldGuruContent.sql /
Binary Id=UpgradeSql SourceFile=SQL Scripts\Upgrade.sql /
Binary Id=AddCompleteMediaSql SourceFile=SQL Scripts\Upgrade.sql
/
Binary Id=InstallGuruContentSql SourceFile=SQL
Scripts\InstallGuruContent.sql /
Binary Id=UpdateCustomPlayListSql SourceFile=SQL
Scripts\UpdateCustomPlayList.sql /
Binary Id=InstallFeaturedContentSql SourceFile=SQL
Scripts\InstallFeaturedContent.sql /
DirectoryRef Id=SERVER
Component Id='CreateDtxDataUser.exe'
Guid='26f80392-dcbe-47af-a7e0-d187cbec0e15'
File Id='CreateDtxDataUser.exe' Source='C:\VS
Publish\Guru\ProgramFiles\Guru\Server\CreateDtxDataUser.exe' KeyPath='yes'/
/Component
Component Id='Guru.Server.exe'
Guid='8027388d-0f90-465b-9668-d1388977caaa'
File Id='Guru.Server.exe' Source='C:\VS
Publish\Guru\ProgramFiles\Guru\Server\Guru.Server.exe' KeyPath='yes'/
ServiceInstall
Id=ServiceInstaller
Type=ownProcess
Name=GuruService
DisplayName=Guru Media and Licensing Service
Description=Provides media distribution, data coordination, and
licensing services to the Guru application
Start=auto
Account=[SERVICEACCOUNT]
Password=[SERVICEPASSWORD]
ErrorControl=normal
/
ServiceControl Id=StartService Start=install Stop=both
Remove=uninstall Name=GuruService Wait=yes /
sql:SqlScript Id=CreateDatabase ExecuteOnInstall=yes
BinaryKey=CreateDatabaseSql SqlDb=SqlDatabase/
sql:SqlScript Id=CreateUsers ExecuteOnInstall=yes
BinaryKey=CreateUsersSql SqlDb=SqlDatabase/
sql:SqlScript Id=CreateBaseLineDb ExecuteOnInstall=yes
BinaryKey=CreateBaseLineDbSql SqlDb=SqlDatabase/
sql:SqlScript Id=RemoveOldGuruContent ExecuteOnInstall=yes
Re: [WiX-users] Disable logging in Burn
Passing /l should enable logging when it was disabled by default as per: http://wixtoolset.org/documentation/manual/v3/xsd/wix/log.html Not a new feature but that doesn't mean it wasn't broken. smile/ _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Friday, October 24, 2014 12:29 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Disable logging in Burn Unless that is a newer feature I'd challenge how burn is disabling logging today. I don't see anywhere where the manifest would be parsing the Log/@disable. If we are going to disable logging, I'd think you'd still want the log attributes in the manifest. Then with a bit of work, we could allow Bundle.exe /lv or the likes to turn it on as needed. The way it sits today, it almost looks like if you put Log/@Disable in your bundle, that there is no way to re-enable it without rebuilding the bundle. -Original Message- From: Rob Mensching [mailto:r...@firegiant.com] Sent: Friday, October 24, 2014 11:37 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Disable logging in Burn That sounds like a bug in Burn. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Tobias Erichsen [mailto:i...@tobias-erichsen.de] Sent: Friday, October 24, 2014 6:54 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Disable logging in Burn Hi everyone, after Rob has been so kind to point me to the log element to disable burn-logging, I have added Log Disable=yes / and now the log of burn in the %temp% directory vanishes. This created some unwanted side-effect though: In the local directory where my bootstrapper was located, for each MSI included in it a file was created which was named: (null)_0_MSI_PACKAGE_ID.(null) So disabling burn-logging seems not to disable the logging of each MSI. Is this by design, or just my mistake? Best regards, Tobias -- ___ 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] FW: WiX Burn setup is very very slow
I have made a Burn setup with several msi packages.In my package I use Heat to harvest directory and package differents features such as languages files located in different folders of my application.To make the setup works I need to ad a suffix, for example the languade identity for each foder so that I can reference to the same folder component for each language feature using a different Id. In this way the folders and files are not ordered to make the files grouped depend on folder location as they will be installed in sequence.Is there any way to make the msi tables reordered based on folder location so during installation all the files of a folder will be installed at the same time reducing the number of changing folder operations. I have read that changing folder during installation is very time consuming, so how to prevent and optimize this?Heat harvesting don't take care about the folder locations so for each file installed the MSIEXEC will change current folder. It will be possible to reorder the files based on folder location in the msi table during compiling process of msi? -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] FW: How to speed up building burn package
I have a solution with a Burn package and several MSI packages. I'm using WiX 3.8 official. Is there any way to speed up the building of the solution? is there any way for parallelizing building of each msi? or to build multiple msi?The main package msi contains languages divided into different features inside the msi package, it could be better to have each language in a separate msi language pack? For each msi I have encapsulated the cab file but I have set it with no compression in the media element.I Run HarvestDirectory one time and then apply several sxlt transformation using MSBuild transformation to make different wsx to create different feature to install. The Burn package not compress the msi packages inside the burn exe. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] FW: Unzip file after install
I have some folders with localized html documentation, each folder contains many files, and they are not vital for my application, I harvest the folder using heat to build the wxs and then the msi.The installation of these folders is very very slow as heat doesn't order the files based on directory and the setup when during install will change the current directory for each file to install, and every file is marked as keypath. To speed up installation process I'd like to add the zipped folders to my msi and then unzip them with a custom action, is there any build in system for doing this with WiX, using an extension for example? I need to add each localized folder inside a different msiFeature and then I need to run the custom action when the feature is selected to be installed (and removed on uninstall removeing all the folder). Apart of the speedup of the installation process, I have a problem with some folders that I can't harvest using heat as the full path of files with relative folders tree exceed the max limit of characters that can be passed to heat.exe as command args for the path of the folder to harvest, and in this case using the zipped folders to be unzipped from the msi during installation will be the only choice. Which is the best way for doing this? -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] FW: Burn setup automatic testing
I have made a Burn setup I need to perform unit testing to ensure that after a build my setup is ok.I need to test that If I choose to install a feature in the Managed UI WPF the Burn setup finally install, or uninstall, or upgrade a package or feature.Then I need to test the entire install and uninstall process to verify if my application is installed and uninstalled correctly. How can I make this auto test? -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] FW: WiX Burn: how to Force Major Upgrade for a 3dparty msi package
I have an msi package from another company that doesn't manage upgrade well,
they allow to make minor and major upgrade but the package works well only if
you uninstall, clear all the application folder and then make a new
installation.I can't modify the package as I have only the msi file, and they
can't fix the problem.
I make a Burn package adding this package to the chain, so I'd like to force
Major upgrade from WiX Burn.I have added an ExePackage before this msi package
to run a script that call msiexec /X{ProductCode} /qn and then remove the
installation folder and in this way it seem to work.The problem is that if the
msi package is already installed, the package is marked as
MyMsiPackage - Detect: Present, default request: Present, ba request: Present,
execute: None (or MinorUpgrade)
As I uninstall the package using the script that run after the plan operation,
the msi package is marked as present so the execute action is none (if the
package version is the same) or MinorUpgrade (if the version change)
In both cases as I haveuninstalled the package It doesnt install the pakage (in
the first case not start the installation, in the second the minor upgrade
report errors)
Is there a way for setting the detect of the msi to absent? as to force the
installation of the package in any way?
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] FW: R: WiX Burn Major Upgrade Uninstall the old msi packages but not install the new msi packages
I have added the MajorUpgrade ad shown in the wix help MajorUpgrade DowngradeErrorMessage=A later version of [ProductName] is already installed. Setup will now exit.I haven't assigned the Schedule value as it is for default afterInstallValidate as reported in the WiX help Schedule = Determines the scheduling of the RemoveExistingProducts standard action, which is when the installed product is removed. The default is afterInstallValidate which removes the installed product entirely before installing the upgrade product. It's slowest but gives the most flexibility in changing components and features in the upgrade product.- But what I can see from the logs is that when I run the Burn setup it start and perform the installation of all the msi packages and then start the unistall of the old Burn setup that perform the uninstall of the msi package. As I can see the msi is not involved in the perform of the upgrade but it's Burn that call the install and the uninstall of the package. As another proof I have tried to install and the upgrade the only msi package running it directly.In the case of a minor upgrade (changing only the revision number) it doesn't perform the uninstall of the old package but only the minor upgrade.In the case of a major upgrade (changing the first version number) it does all correctly, uninstall the old package and the install the new one. So where is the problem is Bur bugged in the version 3.8? I have missed something?As I have seen the element MajoutUpgrade on the msi package not block the minor upgrade but is used only if it's added using Burn.But using Burn is the bootstrapper that command the process and install first and then uninstall. So where is the problem?I'm really disappointed, I'm near to give up with using WiX and Burn. As soon as possible I'll try to add a simplified sample to reproduce the problem,Thanks Date: Tue, 14 Oct 2014 11:17:27 -0700 From: phildgwil...@gmail.com To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] R: WiX Burn Major Upgrade Uninstall the old msi packages but not install the new msi packages If your MSI package has the MajorUpgrade element to perform the upgrade, then that's what's doing the upgrade, so you perhaps have it scheduled afterInstallExecute, which means the uninstall happens after the new product is installed. If you schedule it afterInstallInitlize it will remove the old product first. --- Phil Wilson On Tue, Oct 14, 2014 at 1:48 AM, Marco Tognacci mark...@live.it wrote: The burn log says that first is installed the new Version of My package then is uninstalled the old Version of My package. As myPackage remove some folders on uninstall, it remove even the new files intalled by the new Version of myPackage. IS there a way to force burn setup to perform first uninstall of the old Version of myPackage and then perfom the intall of the new Version of myPavkage? myPackage have the MajorUpgrade element, and I'using wix 3.8. Inviata dal mio Windows Phone Da: Hoover, Jacobmailto:jacob.hoo...@greenheck.com Inviato: 06/10/2014 20:41 A: General discussion about the WiX toolset.mailto:wix-users@lists.sourceforge.net Oggetto: Re: [WiX-users] WiX Burn Major Upgrade Uninstall the old msi packages but not install the new msi packages The bundle log will tell you what it did and why it did it. Are you using WixStdBA or your own BA? -Original Message- From: Marco Tognacci [mailto:mark...@live.it] Sent: Monday, October 06, 2014 1:24 PM To: WiX - users Subject: [WiX-users] WiX Burn Major Upgrade Uninstall the old msi packages but not install the new msi packages I have made a Burn setup package with the last official WiX release 3.8.I have some msi package inside the Burn chain, for example packA.msi version number 1.0.0.0packB.msi version number 1.0.0.0 the burn package genrated isburn.exe version number 1.0.0.0 then I need to update one of the packages and regenerate the burn setup again packA.msi version number 1.1.0.0packB.msi version number 1.0.0.0burn.exe version number 1.1.0.0 when I install the new package burn call the uninstall of all package but not install the new packages.Is there any bug in WiX 3.8 about upgrading Burn? or There is some problems in how I make the burn package for upgrading? -- Slashdot TV. Videos 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. Videos for Nerds. Stuff that Matters.
[WiX-users] FW: Managed Burn Bootstrapper not localize prerequisites window
The Burn Managed bootstrapper of the version 3.9 not works in localizing the Prerequisites window.I'm in Italy, and I have tried to install on a english Windows 7 OS and the prerequisites window appear localized in Italian not in english.The prerequisite that I need to Install, the Net Framework 4.5.2, is correcly localized in english if I run it directly?Is it a bug, or is there some other configuration to set? -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] FW: WiX Burn: how to Force Major Upgrade for a 3dparty msi package
I have an msi package from another company that doesn't manage upgrade well,
they allow to make minor and major upgrade but the package works well only if
you uninstall, clear all the application folder and then make a new
installation.I can't modify the package as I have only the msi file, and they
can't fix the problem.
I make a Burn package adding this package to the chain, so I'd like to force
Major upgrade from WiX Burn.I have added an ExePackage before this msi package
to run a script that call msiexec /X{ProductCode} /qn and then remove the
installation folder and in this way it seem to work.The problem is that if the
msi package is already installed, the package is marked as
MyMsiPackage - Detect: Present, default request: Present, ba request: Present,
execute: None (or MinorUpgrade)
As I uninstall the package using the script that run after the plan operation,
the msi package is marked as present so the execute action is none (if the
package version is the same) or MinorUpgrade (if the version change)
In both cases as I haveuninstalled the package It doesnt install the pakage (in
the first case not start the installation, in the second the minor upgrade
report errors)
Is there a way for setting the detect of the msi to absent? as to force the
installation of the package in any way?
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] FW: Unzip file after install
You can add a zip file and unzip using a custom action but remember that the MSI will not uninstall all the files that were unzipped.(only the .zip file will be deleted ) You will have to write a Custom Action to delete that also. -Original Message- From: Marco Tognacci [mailto:mark...@live.it] Sent: Friday, October 24, 2014 2:41 PM To: WiX - users Subject: [WiX-users] FW: Unzip file after install I have some folders with localized html documentation, each folder contains many files, and they are not vital for my application, I harvest the folder using heat to build the wxs and then the msi.The installation of these folders is very very slow as heat doesn't order the files based on directory and the setup when during install will change the current directory for each file to install, and every file is marked as keypath. To speed up installation process I'd like to add the zipped folders to my msi and then unzip them with a custom action, is there any build in system for doing this with WiX, using an extension for example? I need to add each localized folder inside a different msiFeature and then I need to run the custom action when the feature is selected to be installed (and removed on uninstall removeing all the folder). Apart of the speedup of the installation process, I have a problem with some folders that I can't harvest using heat as the full path of files with relative folders tree exceed the max limit of characters that can be passed to heat.exe as command args for the path of the folder to harvest, and in this case using the zipped folders to be unzipped from the msi during installation will be the only choice. Which is the best way for doing this? -- ___ 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] Error database does not exist when executing ExecuteSQLStrings
I changed my product.was to the following but when I test it it doesn't create the database. I don't receive any errors when I run it, it just doesn't create anything. My product.was... Component Id='SqlComponent' Guid='A60B1852-7C4B-402B-A619-EECA2893C5AC' KeyPath='yes' ConditionUSEINTEGRATEDSECURITY = 1/Condition sql:SqlDatabase Id='SqlDatabase' Database='mvdb' Server='MVSQLEXPRESS' CreateOnInstall='yes' DropOnUninstall='no' ContinueOnError='no'/ sql:SqlScript Id=CreateDatabase ExecuteOnInstall=yes BinaryKey=CreateDatabaseSql SqlDb=SqlDatabase/ sql:SqlScript Id=CreateUsers ExecuteOnInstall=yes BinaryKey=CreateUsersSql SqlDb=SqlDatabase/ sql:SqlScript Id=CreateBaseLineDb ExecuteOnInstall=yes BinaryKey=CreateBaseLineDbSql SqlDb=SqlDatabase/ sql:SqlScript Id=RemoveOldGuruContent ExecuteOnInstall=yes BinaryKey=RemoveOldGuruContentSql SqlDb=SqlDatabase/ sql:SqlScript Id=Upgrade ExecuteOnInstall=yes BinaryKey=UpgradeSql SqlDb=SqlDatabase/ sql:SqlScript Id=AddCompleteMedia ExecuteOnInstall=yes BinaryKey=AddCompleteMediaSql SqlDb=SqlDatabase/ sql:SqlScript Id=InstallGuruContent ExecuteOnInstall=yes BinaryKey=InstallGuruContentSql SqlDb=SqlDatabase/ sql:SqlScript Id=UpdateCustomPlayList ExecuteOnInstall=yes BinaryKey=UpdateCustomPlayListSql SqlDb=SqlDatabase/ sql:SqlScript Id=InstallFeaturedContent ExecuteOnInstall=yes BinaryKey=InstallFeaturedContentSql SqlDb=SqlDatabase/ /Component Feature Id=Server Title=Guru Teach Server Level=1 ComponentRef Id=RegistryEntries/ ComponentRef Id='CreateDtxDataUser.exe' / ComponentRef Id='Guru.Server.exe' / ComponentRef Id='ChangeFirewall' / ComponentRef Id='Guru.Server.exe.config' / ComponentRef Id='Guru.Server.Remoting.dll' / ComponentRef Id='Guru.ServerLibrary.dll' / ComponentRef Id='Ionic.Zip.Reduced.dll' / ComponentRef Id='JsonChannel.dll' / ComponentRef Id='license.dat' / ComponentRef Id='Microsoft.Practices.Prism.dll' / ComponentRef Id='Microsoft.Practices.ServiceLocation.dll' / ComponentRef Id='SQLExpressProvider.dll' / ComponentRef Id='Guru_Featured_manifest.xml' / ComponentRef Id='GURU_Library_manifest.xml' / ComponentRef Id='Guru.Server.Configuration.dll' / ComponentRef Id='SqlComponent'/ /Feature Tanks for the help! Gary -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Error-database-does-not-exist-when-executing-ExecuteSQLStrings-tp7597477p7597489.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] FW: How to speed up building burn package
There are many factors and opinions on this issue. I try to make sure that my MSI projects can build incrementally (if nothing was changed). I use MSBuild command line scripts (customized with ITask and Targets) to do most builds, rather than VS (used for development debugging) I minimize use of the preprocessor. I put as much common and rarely changing code as possible into wixlibs (not bound to files). I define paths using compiler -I and -d, and linker -b commands (I edit my project file directly, there are other approaches). I use external cabs, and configure to reuse cabs. I always rebuild my bundle to make sure that the version gets incremented (which depends on your approach to versioning). I have experimented with changing the compression level, but have not seen much of a change. Consider the following: http://wixtoolset.org/documentation/manual/v3/howtos/general/optimizing_builds.html I have not done this, but: http://msdn.microsoft.com/en-us/library/bb651793.aspx -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-speed-up-building-burn-package-tp7597361p7597490.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
