Re: [WiX-users] Overwrite files with higher version on major upgrade
Is that DLL a COM component? If such, is it self registering? --- On Fri, 10/1/10, Alex Ivanoff alex.ivan...@shavlik.com wrote: From: Alex Ivanoff alex.ivan...@shavlik.com Subject: [WiX-users] Overwrite files with higher version on major upgrade To: wix-users@lists.sourceforge.net Date: Friday, October 1, 2010, 7:53 AM We need to overwrite files with higher version on major upgrade: SomeFile.dll (3.0.1.1) - SomeFile.dll (2.1.0.0) How do we do it? -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Automatic remove of older version
That's called a major upgrade. You need to change the product id for your newer installer as well as the version. You also have to say that you want previous version uninstalled. You have 2 options: 1. Use an Upgrade element like explained here. Remember to schedule RemoveExistingProducts action. http://www.tramontana.co.hu/wix/lesson4.php#4.1 or 2. As you use WiX3, you can use instead of Upgrade the MajorUpgrade element; in this case you don't have to specify RemoveExistingProducts, the MajorUpgrade element available in WiX will do it for you. I hope it works. --- On Thu, 9/30/10, marric01 richard.mar...@.gouv.qc.ca wrote: From: marric01 richard.mar...@.gouv.qc.ca Subject: [WiX-users] Automatic remove of older version To: wix-users@lists.sourceforge.net Date: Thursday, September 30, 2010, 10:44 PM Hi, I made an installer with WIX 3.5 that deploy things for a BI Solution. When I have a new version of my WIX Installer, and the client run the installer (MSI), can it automatically uninstall any older version installed on the PC and start the installation of the new version ? It is something possible ? Any suggestion on how to do this (or some link on web) ? I don't want the message saying that theres is another older version on the PC and it got to be uninstall before installing the new one. I never need to Update things ... I always have to remove everything and install it back with new components. I tried this (see code bellow) but it keep saying that another version is installed and that I have to remove it from Add/Remove Program Product Id=725fca14-3120-4e13-a782-90dec57b59b3 Name=AQ_SPU_CUBE Language=1036 Version=2.0.0 Manufacturer=AQ_SPU_CUBE UpgradeCode=002d3b98-f6be-4e8e-b6ae-4848ff009b46 Codepage=1252 Package InstallerVersion=200 Compressed=yes / Media Id=1 Cabinet=media1.cab EmbedCab=yes / Upgrade Id=002d3b98-f6be-4e8e-b6ae-4848ff009b46 UpgradeVersion OnlyDetect=no Property=PREVIOUSFOUND Minimum=1.0.0 IncludeMinimum=yes Maximum=3.0.0 IncludeMaximum=no / /Upgrade InstallExecuteSequence RemoveExistingProducts Before=InstallInitialize / /InstallExecuteSequence Thanks Richard -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Automatic-remove-of-older-version-tp5589138p5589138.html Sent from the wix-users mailing list archive at Nabble.com. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Major upgrade, MigrateFeatureStates custom action
Hi Phil, thanks. Actually I wanted it that way, but I feel it's not the problem
at the moment.
Yet, as is my case, 2 features and the original installer installed Feature1, I
would like the upgrade to go directly upgrading the installed feature with no
UI displayed to select what feature to install (ie go on and upgrade Feature1).
As far as I understand it, scheduling MigrateFeatureStates will set the feature
status of the new installer as found in the original installer (ie my UI for
the new installer will preselect the currently installed feature but still let
the user specify what it wants by actually displaying the UI). Now there might
be a problem indeed. The UI I'm using for my installer is a list box I populate
within a custom action (within a DLL) but actually not query for feature state
in that custom action and preselect anything (I was somehow expecting the MSI
to do it, but of course that's stupid).
Now back to my problem, can you see any problem in the log I posted below or is
the fact that I'm using a UI and schedule MigrateFeatureStates which creates me
problems?
Thanks in advance.
--- On Fri, 9/24/10, Wilson, Phil phil.wil...@invensys.com wrote:
From: Wilson, Phil phil.wil...@invensys.com
Subject: Re: [WiX-users] Major upgrade, MigrateFeatureStates custom action
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Date: Friday, September 24, 2010, 8:01 PM
Setting MigrateFeatureStates means that you want to do an upgrade where the
features that get installed are exactly the same as the features that are
already installed. It usually doesn't make sense to set that and then set
features in a UI dialog.
Phil Wilson
-Original Message-
From: fiordean dacian [mailto:dfiord...@yahoo.com]
Sent: Friday, September 24, 2010 8:01 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Major upgrade, MigrateFeatureStates custom action
Hi
I made a mistake when I copied the FindRelatedProducts in my initial email.
Here is the correct text from the verbose log (we see the property
WIX_UPGRADE_DETECTED being correctly set to my initial installed product GUID)
Action start 16:44:52: FindRelatedProducts.
FindRelatedProducts: Found application: {C0C6FEAB-9024-481E-BB4F-7A54EC0BA765}
MSI (c) (38:4C) [16:44:52:289]: PROPERTY CHANGE: Adding WIX_UPGRADE_DETECTED
property. Its value is '{C0C6FEAB-9024-481E-BB4F-7A54EC0BA765}'.
MSI (c) (38:4C) [16:44:52:289]: PROPERTY CHANGE: Adding MIGRATE property. Its
value is '{C0C6FEAB-9024-481E-BB4F-7A54EC0BA765}'.
Action ended 16:44:52: FindRelatedProducts. Return value 1.
Thanks.
--- On Fri, 9/24/10, fiordean dacian dfiord...@yahoo.com wrote:
From: fiordean dacian dfiord...@yahoo.com
Subject: Major upgrade, MigrateFeatureStates custom action
To: wix-users@lists.sourceforge.net
Date: Friday, September 24, 2010, 5:39 PM
Hello
I have a couple of problems with my installer on a major upgrade. I'm using Wix
3.5.
My installer has 2 features and I use the MajorUpgrade element available with
Wix 3.5 to do my major upgrade.
Here is what I did:
Product Code and version changed within the new installer.
As I use MajorUpgrade element, I removed my explicit declaration of
RemovedExistingProducts as MajorUpgrade seems it schedules it. From the
documentation, I understand MajorUpgrade schedules also MigrateFeatureStates
and this is good as I want to take advantage of this MSI feature (more below).
ALLUSERS property is set to 1 in both installers.
Here is what I get:
Install the first version of the product which installs fine; then launch the
installer for the newer version to perform an upgrade.
I do a verbose log and I get a
couple of strange things:
Action 15:29:09: FindRelatedProducts. Searching for related applications
Action start 15:29:09: FindRelatedProducts.
FindRelatedProducts: Found application: {C0C6FEAB-9024-481E-BB4F-7A54EC0BA765}
MSI (c) (C8:A0) [15:29:09:708]: PROPERTY CHANGE: Adding PREVFOUND property. Its
value is '{C0C6FEAB-9024-481E-BB4F-7A54EC0BA765}'.
Action ended 15:29:09: FindRelatedProducts. Return value 1.
...
MSI (c) (C8:A0) [15:29:09:817]: Doing action: MigrateFeatureStates
Action 15:29:09: MigrateFeatureStates. Migrating feature states from related
applications
Action start 15:29:09: MigrateFeatureStates.
Action ended 15:29:09: MigrateFeatureStates. Return value 0.
...
Plenty of
Disallowing installation of component: {83D1BFA5-5703-43F2-AB56-BB0630B8E921}
since the same component with higher versioned keyfile exists
...
My 2 features are absent from the installation
MSI (s) (5C:FC) [15:29:23:721]: Feature: FullInstallation; Installed: Absent;
Request: Null; Action: Null
MSI (s) (5C:FC) [15:29:23:721]: Feature: DcServer; Installed: Absent;
Request: Null; Action: Null
This explains why no upgrade is done, the question is why they are absent? I
select them through a UI which changed like below compared to the previous
Re: [WiX-users] Checking for other products
I assume you logged MSI actions; what is the value of REQUIREDBINARIES property? Also, I'm note sure you correctly use the upgradecode (ID tag from the Upgrade element). That ID must be the UpgradeCode from the product you want to detect wheter installed or not; do you have that GUID? --- On Sat, 9/25/10, ldy...@vorum.com ldy...@vorum.com wrote: From: ldy...@vorum.com ldy...@vorum.com Subject: [WiX-users] Checking for other products To: wix-users@lists.sourceforge.net Date: Saturday, September 25, 2010, 1:48 AM Hi all, I want to terminate the installation of a product unless there is a recent version of a different product already installed, so I defined an Upgrade element and a Condition thus: !-- The other Product's UpgradeCode. -- ?define ExecutablesCode=Some guid? !-- Minimum Product Version. -- ?define ExecutablesVersion=13.0.13? ?define RidiculouslyHighVersion=99.99.99? . . Upgrade Id=$(var.ExecutablesCode) UpgradeVersion Minimum=$(var.ExecutablesVersion) IncludeMinimum=yes Maximum=$(var.RidiculouslyHighVersion) IncludeMaximum=no OnlyDetect=yes Language=1033 Property=REQUIREDBINARIES / /Upgrade . . Condition Message=You must install ... REQUIREDBINARIES /Condition . . This didn't work; the install always aborts, whether the required product and version are installed or not. I thought it might be a sequencing problem, so I got rid of the Condition and defined a CustomAction and sequenced it sequenced it so it should come some time after FindRelatedProducts, i.e., CustomAction Id=CheckForReqdBins Error=You must install ... Return=check / . . InstallExecuteSequence . . Custom Action=CheckForReqdBins After=PreventDowngrading (NOT REQUIREDBINARIES) /Custom . . Same result. I'm kind of fuzzy about the evaluation of strings as conditions, but something analagous has worked for me when the Upgrade is the product currently being installed. Assisistance appreciated. Regards, Lee -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Major upgrade, MigrateFeatureStates custom action
Hello
I have a couple of problems with my installer on a major upgrade. I'm using Wix
3.5.
My installer has 2 features and I use the MajorUpgrade element available with
Wix 3.5 to do my major upgrade.
Here is what I did:
Product Code and version changed within the new installer.
As I use MajorUpgrade element, I removed my explicit declaration of
RemovedExistingProducts as MajorUpgrade seems it schedules it. From the
documentation, I understand MajorUpgrade schedules also MigrateFeatureStates
and this is good as I want to take advantage of this MSI feature (more below).
ALLUSERS property is set to 1 in both installers.
Here is what I get:
Install the first version of the product which installs fine; then launch the
installer for the newer version to perform an upgrade.
I do a verbose log and I get a couple of strange things:
Action 15:29:09: FindRelatedProducts. Searching for related applications
Action start 15:29:09: FindRelatedProducts.
FindRelatedProducts: Found application: {C0C6FEAB-9024-481E-BB4F-7A54EC0BA765}
MSI (c) (C8:A0) [15:29:09:708]: PROPERTY CHANGE: Adding PREVFOUND property. Its
value is '{C0C6FEAB-9024-481E-BB4F-7A54EC0BA765}'.
Action ended 15:29:09: FindRelatedProducts. Return value 1.
...
MSI (c) (C8:A0) [15:29:09:817]: Doing action: MigrateFeatureStates
Action 15:29:09: MigrateFeatureStates. Migrating feature states from related
applications
Action start 15:29:09: MigrateFeatureStates.
Action ended 15:29:09: MigrateFeatureStates. Return value 0.
...
Plenty of
Disallowing installation of component: {83D1BFA5-5703-43F2-AB56-BB0630B8E921}
since the same component with higher versioned keyfile exists
...
My 2 features are absent from the installation
MSI (s) (5C:FC) [15:29:23:721]: Feature: FullInstallation; Installed: Absent;
Request: Null; Action: Null
MSI (s) (5C:FC) [15:29:23:721]: Feature: DcServer; Installed: Absent;
Request: Null; Action: Null
This explains why no upgrade is done, the question is why they are absent? I
select them through a UI which changed like below compared to the previous
version of my installer:
Old version:
InstallUISequence
Custom Action=FillingListBox After=CostFinalize /
/InstallUISequence
New version:
InstallUISequence
Custom Action=FillingListBox After=MigrateFeatureStates /
/InstallUISequence
Nothing is removed like for a major upgrade (and it says this is maintainance
or uninstall):
MSI (s) (5C:FC) [15:29:23:736]: Doing action: RemoveExistingProducts
Action 15:29:23: RemoveExistingProducts. Removing applications
Action start 15:29:23: RemoveExistingProducts.
MSI (s) (5C:FC) [15:29:23:736]: Skipping RemoveExistingProducts action: current
configuration is maintenance mode or an uninstall
Action ended 15:29:23: RemoveExistingProducts. Return value 0.
So it looks like MigrateFeatureStates doesn't detect the feature state of the
current installation to set it for the new version of the installer.
Here is the Upgrade table for the initial installer:
Upgrade code Version
Attributes ActionProperty
{CB09E96B-19D6-439C-9A40-68143559032A} 6.6.0 258
NEWERFOUND
{64EF24E1-8FC8-44C0-B9AD-981D638B4596} 6.5.0 6.6.0 256
PREVFOUND
And here is the Upgrade table for the new installer:
{CB09E96B-19D6-439C-9A40-68143559032A} 6.7.0 1 WIX_UPGRADE_DETECTED
{CB09E96B-19D6-439C-9A40-68143559032A} 6.7.0 2 WIX_DOWNGRADE_DETECTED
Anyone has an idea what am I doing wrong?
Thanks!
--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] When is a 64-bit install needed and heat
Hello Therefore you can create hybrid installers as long as you dont need to install files to the System64Folder. And how do you exactly do that? Say you have a 32 bit component which needs to install correctly on both 32 bit and 64 bit. Specifying the component as a x64 component will suffice or you need a hybrid which tells a component to write there if 32 and there if 64? thanks --- On Mon, 9/13/10, Fabio Di Lorenzo fa...@dilorenzo.ch wrote: From: Fabio Di Lorenzo fa...@dilorenzo.ch Subject: Re: [WiX-users] When is a 64-bit install needed and heat To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Date: Monday, September 13, 2010, 10:45 AM Hi Sean, If I'm adding items to the registry in the hkey_classes_root hive do I need both a 32-bit and 64-bit installer. Where the registry keys are going is component dependent. You can simply mark a component as x64 Bit component and those registry keys will be written to the x64 View. Therefore you can create hybrid installers as long as you dont need to install files to the System64Folder. Also is ther a way of asking heat to generate me a code fragment given a com server? as far as i know, as long as you aren't using the -scom parameter they should be automatically harvested. Regards, Fabio On Mon, Sep 13, 2010 at 8:40 AM, Sean Farrow sean.far...@seanfarrow.co.ukwrote: Hi: If I'm adding items to the registry in the hkey_classes_root hive do I need both a 32-bit and 64-bit installer. Also is ther a way of asking heat to generate me a code fragment given a com server? Regards Sean. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Detect .NET Framework 3.0
Hello Here is how I would do it (actually I'm using the same but for .NET 3.5) Property Id=FRAMEWORK30 RegistrySearch Id=RegFindFramework35SP1 Root=HKLM Key=SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0 Name=Version Type=raw/ /Property If .NET framework 3.0 is installed, the FRAMEWORK30 will contain the exact version installed on the machine (ie 3.2.30721). Hope this helps. --- On Tue, 8/3/10, BSR PHANI bsrphani...@gmail.com wrote: From: BSR PHANI bsrphani...@gmail.com Subject: [WiX-users] Detect .NET Framework 3.0 To: wix-users-requ...@lists.sourceforge.net, General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Date: Tuesday, August 3, 2010, 9:28 AM Hi , Can any one please help me that how to detect .NET Framework 3.0(launch condition) using WIX 3.0? Thanks, Phani -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn [Re: Bootstrapper]
Hi, Can anyone help with my question below on Burn? Is there a release data for this much awaited tool? Thanks, --- On Fri, 4/16/10, fiordean dacian dfiord...@yahoo.com wrote: From: fiordean dacian dfiord...@yahoo.com Subject: [WiX-users] Burn [Re: Bootstrapper] To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Date: Friday, April 16, 2010, 4:20 PM Hi In relation to Carolina's post, do you guys have any date for Burn? Is there a release we can play with? I have the 3.5.1419 release of the package and I see a tool called burnstub.exe; what is that? Thanks Dacian --- On Fri, 4/16/10, Carolina Zuqueto Amaral carolina.ama...@conv.com.br wrote: From: Carolina Zuqueto Amaral carolina.ama...@conv.com.br Subject: [WiX-users] Bootstrapper To: 'General discussion for Windows Installer XML toolset.' wix-users@lists.sourceforge.net Date: Friday, April 16, 2010, 3:22 PM Hi, I created a bootstrapper, but it isn´t efficient. There is a program what when it is installed, the bootstrapper does not recognize. And the program is reinstalled. This program is the HASP. How can I solve this? PROJ File: Project xmlns=http://schemas.microsoft.com/developer/msbuild/2003; ItemGroup BootstrapperFile Include=aMicrosoft.Windows.Installer.4.5 ProductNameWindows Installer 4.5/ProductName /BootstrapperFile BootstrapperFile Include=cMicrosoft.Net.Framework.3.5.SP1 ProductNameMicrosoft .NET Framework 3.5 SP1/ProductName /BootstrapperFile BootstrapperFile Include=Microsoft.Sql.Server.Express.10.0 ProductNameMicrosoft Sql Server ExpresS 2008/ProductName /BootstrapperFile BootstrapperFile Include=HASP ProductNameHASP/ProductName /BootstrapperFile /ItemGroup Target Name=Bootstrapper GenerateBootstrapper ApplicationFile=AssetHealth\AssetHealth_en.msi ApplicationName=Convergencia Asset Health Client BootstrapperItems=@(BootstrapperFile) OutputPath=.\readysetup AssetHealthClient EN-US 4.5 2008 Culture=en-us / /Target /Project HASP - Package: ?xml version=1.0 encoding=utf-8 ? Package xmlns=http://schemas.microsoft.com/developer/2004/01/bootstrapper; Name=DisplayName Culture=Culture LicenseAgreement=eula.txt !-- Defines list of files to be copied on build -- PackageFiles PackageFile Name=eula.txt/ /PackageFiles InstallChecks RegistryCheck Property=HASP Key=HKLM\SOFTWARE\Classes\Installer\Products\EBC414A23FDC6C849AB13D4D25F2E85B Value=Version / /InstallChecks Commands Reboot=Defer Command PackageFile=HASPUserSetup.exe Arguments=' /qb' !-- These checks determine whether the package is to be installed -- InstallConditions !-- This indicates HASP is already installed -- BypassIf Property=HASP Compare=VersionGreaterThanOrEqualTo/ !-- Block install if user does not have admin privileges -- FailIf Property=AdminUser Compare=ValueEqualTo Value=false String=AdminRequired/ !-- Block install on less than Windows XP SP2 -- FailIf Property=VersionNT Compare=VersionLessThan Value=5.1.2 String=InvalidPlatformWinNT/ !-- Block install on W2K3 with no service pack -- FailIf Property=VersionNT Compare=VersionEqualTo Value=5.2.0 String=InvalidPlatformWinNT/ !-- Block install if the platform is IA-64 -- FailIf Property=ProcessorArchitecture Compare=ValueEqualTo Value=IA64 String=InvalidPlatformArchitecture / /InstallConditions ExitCodes ExitCode Value=0 Result=Success/ ExitCode Value=1602 Result=Fail String=UserCancelled/ ExitCode Value=1603 Result=Fail String=GeneralFailure/ ExitCode Value=3010 Result=SuccessReboot/ DefaultExitCode Result=Fail FormatMessageFromSystem=true String=GeneralFailure / /ExitCodes /Command /Commands !-- Defines a localizable string table for error messages-- Strings String Name=DisplayNameHASP/String String Name=Cultureen/String String Name=AdminRequiredAdministrator permissions are required to install HASP Contact your administrator./String String Name=InvalidPlatformWinNTInstallation of the HASP requires Windows XP SP2, Windows 2003 SP1, Windows Vista, or later. Contact your application vendor./String String Name=UserCancelledThe user has cancelled the installation. HASP has not been installed./String String Name=GeneralFailureA failure occurred attempting to install HASP./String String Name=HASPUserSetupEXEhttp://www.aladdin.com/support/hasp-srm/enduser.aspx/String /Strings /Package HASP - Product: ?xml version=1.0 encoding=utf-8 ? Product xmlns=http
[WiX-users] Burn [Re: Bootstrapper]
Hi In relation to Carolina's post, do you guys have any date for Burn? Is there a release we can play with? I have the 3.5.1419 release of the package and I see a tool called burnstub.exe; what is that? Thanks Dacian --- On Fri, 4/16/10, Carolina Zuqueto Amaral carolina.ama...@conv.com.br wrote: From: Carolina Zuqueto Amaral carolina.ama...@conv.com.br Subject: [WiX-users] Bootstrapper To: 'General discussion for Windows Installer XML toolset.' wix-users@lists.sourceforge.net Date: Friday, April 16, 2010, 3:22 PM Hi, I created a bootstrapper, but it isn´t efficient. There is a program what when it is installed, the bootstrapper does not recognize. And the program is reinstalled. This program is the HASP. How can I solve this? PROJ File: Project xmlns=http://schemas.microsoft.com/developer/msbuild/2003; ItemGroup BootstrapperFile Include=aMicrosoft.Windows.Installer.4.5 ProductNameWindows Installer 4.5/ProductName /BootstrapperFile BootstrapperFile Include=cMicrosoft.Net.Framework.3.5.SP1 ProductNameMicrosoft .NET Framework 3.5 SP1/ProductName /BootstrapperFile BootstrapperFile Include=Microsoft.Sql.Server.Express.10.0 ProductNameMicrosoft Sql Server ExpresS 2008/ProductName /BootstrapperFile BootstrapperFile Include=HASP ProductNameHASP/ProductName /BootstrapperFile /ItemGroup Target Name=Bootstrapper GenerateBootstrapper ApplicationFile=AssetHealth\AssetHealth_en.msi ApplicationName=Convergencia Asset Health Client BootstrapperItems=@(BootstrapperFile) OutputPath=.\readysetup AssetHealthClient EN-US 4.5 2008 Culture=en-us / /Target /Project HASP - Package: ?xml version=1.0 encoding=utf-8 ? Package xmlns=http://schemas.microsoft.com/developer/2004/01/bootstrapper; Name=DisplayName Culture=Culture LicenseAgreement=eula.txt !-- Defines list of files to be copied on build -- PackageFiles PackageFile Name=eula.txt/ /PackageFiles InstallChecks RegistryCheck Property=HASP Key=HKLM\SOFTWARE\Classes\Installer\Products\EBC414A23FDC6C849AB13D4D25F2E85B Value=Version / /InstallChecks Commands Reboot=Defer Command PackageFile=HASPUserSetup.exe Arguments=' /qb' !-- These checks determine whether the package is to be installed -- InstallConditions !-- This indicates HASP is already installed -- BypassIf Property=HASP Compare=VersionGreaterThanOrEqualTo/ !-- Block install if user does not have admin privileges -- FailIf Property=AdminUser Compare=ValueEqualTo Value=false String=AdminRequired/ !-- Block install on less than Windows XP SP2 -- FailIf Property=VersionNT Compare=VersionLessThan Value=5.1.2 String=InvalidPlatformWinNT/ !-- Block install on W2K3 with no service pack -- FailIf Property=VersionNT Compare=VersionEqualTo Value=5.2.0 String=InvalidPlatformWinNT/ !-- Block install if the platform is IA-64 -- FailIf Property=ProcessorArchitecture Compare=ValueEqualTo Value=IA64 String=InvalidPlatformArchitecture / /InstallConditions ExitCodes ExitCode Value=0 Result=Success/ ExitCode Value=1602 Result=Fail String=UserCancelled/ ExitCode Value=1603 Result=Fail String=GeneralFailure/ ExitCode Value=3010 Result=SuccessReboot/ DefaultExitCode Result=Fail FormatMessageFromSystem=true String=GeneralFailure / /ExitCodes /Command /Commands !-- Defines a localizable string table for error messages-- Strings String Name=DisplayNameHASP/String String Name=Cultureen/String String Name=AdminRequiredAdministrator permissions are required to install HASP Contact your administrator./String String Name=InvalidPlatformWinNTInstallation of the HASP requires Windows XP SP2, Windows 2003 SP1, Windows Vista, or later. Contact your application vendor./String String Name=UserCancelledThe user has cancelled the installation. HASP has not been installed./String String Name=GeneralFailureA failure occurred attempting to install HASP./String String Name=HASPUserSetupEXEhttp://www.aladdin.com/support/hasp-srm/enduser.aspx/String /Strings /Package HASP - Product: ?xml version=1.0 encoding=utf-8 ? Product xmlns=http://schemas.microsoft.com/developer/2004/01/bootstrapper; ProductCode=HASP !-- Defines list of files to be copied on build -- PackageFiles CopyAllPackageFiles=IfNotHomeSite PackageFile Name=HASPUserSetup.exe PublicKey= / /PackageFiles /Product Thanks, Carolina Zuqueto Amaral carolina.ama...@conv.com.brmailto:carolina.ama...@conv.com.br tel +55 21 2494-5476 cel +55 21 9524-7186
[WiX-users] Component installed even if not part of selected feature
Hi, I have something like Component Id=C1 Guid=... DiskId=1 File Id=F1 Name=app.exe Source=c:\app.exe Shortcut Id=app1Sc Name=app sc Icon=... IconIndex=.../ Shortcut Id=app1ScRmt Name=appSc Remote Icon=... IconIndex=.../ /File File.../File Registry.../Registry /Component Component Id=C2 Guid=... DiskId=1 File Id=F1 Name=app.exe Source=c:\app.exe Shortcut Id=app2Sc Name=app sc Icon=... IconIndex=.../ /File File.../File Registry.../Registry /Component Component Id=C3 Guid=... DiskId=1 File.../File /Component Feature Id=Full Level=1 ComponentRef Id=C2/ ComponentRef Id=C3/ /Feature Feature Id=Partial Level=1/ ComponentRef Id=C1/ /Feature I select Full feature for installation; I know it's correct because C3 component files are installed. But I also get the shortcuts from C1 component created which looks like the C1 is installed as well (basically C1 and C2 differs only by a shortcut as above, the files are exactly the same) even if not part of Full install. I saw someone already had a similar problem but can't seem to find an answer for my problem in the answers he got (I don't plan using conditions) http://sourceforge.net/mailarchive/forum.php?thread_name=45f1db380908240448n2c4a5594y3a5e9ee8437ee399%40mail.gmail.comforum_name=wix-users Did anyone had a similar problem? Thanks -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Component installed even if not part of selected feature
Hi thanks Pally I confirm the C1 and C2 file IDs are all different (I missed that in my example for C2) --- On Tue, 9/15/09, Pally Sandher pally.sand...@iesve.com wrote: From: Pally Sandher pally.sand...@iesve.com Subject: Re: [WiX-users] Component installed even if not part of selected feature To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Date: Tuesday, September 15, 2009, 5:58 PM Give both app.exe unique File Id's I suspect the shortcuts won't appear. Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: fiordean dacian [mailto:dfiord...@yahoo.com] Sent: 15 September 2009 15:35 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Component installed even if not part of selected feature Hi, I have something like Component Id=C1 Guid=... DiskId=1 File Id=F1 Name=app.exe Source=c:\app.exe Shortcut Id=app1Sc Name=app sc Icon=... IconIndex=.../ Shortcut Id=app1ScRmt Name=appSc Remote Icon=... IconIndex=.../ /File File.../File Registry.../Registry /Component Component Id=C2 Guid=... DiskId=1 File Id=F1 Name=app.exe Source=c:\app.exe Shortcut Id=app2Sc Name=app sc Icon=... IconIndex=.../ /File File.../File Registry.../Registry /Component Component Id=C3 Guid=... DiskId=1 File.../File /Component Feature Id=Full Level=1 ComponentRef Id=C2/ ComponentRef Id=C3/ /Feature Feature Id=Partial Level=1/ ComponentRef Id=C1/ /Feature I select Full feature for installation; I know it's correct because C3 component files are installed. But I also get the shortcuts from C1 component created which looks like the C1 is installed as well (basically C1 and C2 differs only by a shortcut as above, the files are exactly the same) even if not part of Full install. I saw someone already had a similar problem but can't seem to find an answer for my problem in the answers he got (I don't plan using conditions) http://sourceforge.net/mailarchive/forum.php?thread_name=45f1db380908240448n2c4a5594y3a5e9ee8437ee399%40mail.gmail.comforum_name=wix-users Did anyone had a similar problem? Thanks -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Add/Remove Programs entry redundant
Hi,
Thx Richard.
Here is an excerpt from the log.
...
Action 16:05:31: FindRelatedProducts. Searching for related applications
Action start 16:05:31: FindRelatedProducts.
FindRelatedProducts: Found application: {B607D95A-A73C-444B-87BA-B4E9DBAC4DEE}
...
Action 16:05:44: RemoveExistingProducts. Removing applications
Action start 16:05:44: RemoveExistingProducts.
RemoveExistingProducts: Application: {B607D95A-A73C-444B-87BA-B4E9DBAC4DEE},
Command line: UPGRADINGPRODUCTCODE={F393E0C2-E3B5-4CD1-BD6A-8547DDEC1AE3}
CLIENTUILEVEL=0 REMOVE=ALL
...
Should I see something else?
Dacian
- Original Message
From: Richard [EMAIL PROTECTED]
To: WiX Users wix-users@lists.sourceforge.net
Sent: Monday, January 14, 2008 7:00:59 PM
Subject: Re: [WiX-users] Add/Remove Programs entry redundant
What does your verbose log of the upgrade say?
--
The Direct3D Graphics Pipeline -- DirectX 9 draft available for
download
http://www.xmission.com/~legalize/book/download/index.html
Legalize Adulthood! http://blogs.xmission.com/legalize/
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Looking for last minute shopping deals?
Find them fast with Yahoo! Search.
http://tools.search.yahoo.com/newsearch/category.php?category=shopping-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] List box entry selection
Hi, I added a listbox control on a dialog which I'm adding items into within a custom action (it is actually a feature list similar with the tree control on SetupTypeDlg.wxs except I want the features in a list). Question is, how I could select by default the first entry in that listbox? Thanks, Dacian Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditional installation of merge modules
During install:
ProcessComponents action lists
1: {F393E0C2-E3B5-4CD1-BD6A-8547DDEC1AE3} 2:
{BA9B764A-0DE0-11D5-A548-0090278A1BB8} 3: C:\WINDOWS\system32\mfc70u.dll
1: {F393E0C2-E3B5-4CD1-BD6A-8547DDEC1AE3} 2:
{BA9B7647-0DE0-11D5-A548-0090278A1BB8} 3: C:\WINDOWS\system32\mfc70.dll
1: {F393E0C2-E3B5-4CD1-BD6A-8547DDEC1AE3} 2:
{3AC4AA25-A28A-4F09-826A-30CA0A620F35} 3: C:\WINDOWS\system32\mfc71u.dll
1: {F393E0C2-E3B5-4CD1-BD6A-8547DDEC1AE3} 2:
{F607CA48-C332-4029-AF8A-39BDF6912CD4} 3: C:\WINDOWS\system32\mfc71.dll
InstallFiles action lists
InstallFiles: File: mfc70.dll, Directory: C:\WINDOWS\system32\, Size: 974848
InstallFiles: File: mfc70u.dll, Directory: C:\WINDOWS\system32\, Size: 964608
During repair:
InstallValidate action lists
Info 1603. The file C:\WINDOWS\system32\mfc71u.dll is being held in use by the
following process: Name: explorer, Id: 1312, Window Title: '(not determined
yet)'. Close that application and retry.
ProcessComponents action lists
1: {F393E0C2-E3B5-4CD1-BD6A-8547DDEC1AE3} 2:
{BA9B764A-0DE0-11D5-A548-0090278A1BB8} 3: C:\WINDOWS\system32\mfc70u.dll
1: {F393E0C2-E3B5-4CD1-BD6A-8547DDEC1AE3} 2:
{BA9B7647-0DE0-11D5-A548-0090278A1BB8} 3: C:\WINDOWS\system32\mfc70.dll
1: {F393E0C2-E3B5-4CD1-BD6A-8547DDEC1AE3} 2:
{3AC4AA25-A28A-4F09-826A-30CA0A620F35} 3: C:\WINDOWS\system32\mfc71u.dll
1: {F393E0C2-E3B5-4CD1-BD6A-8547DDEC1AE3} 2:
{F607CA48-C332-4029-AF8A-39BDF6912CD4} 3: C:\WINDOWS\system32\mfc71.dll
InstallFiles action lists
InstallFiles: File: mfc70.dll, Directory: C:\WINDOWS\system32\, Size: 974848
InstallFiles: File: mfc70u.dll, Directory: C:\WINDOWS\system32\, Size: 964608
InstallFiles: File: mfc71.dll, Directory: C:\WINDOWS\system32\, Size: 1060864
InstallFiles: File: mfc71u.dll, Directory: C:\WINDOWS\system32\, Size: 1053184
Info 1603. The file C:\WINDOWS\system32\mfc71u.dll is being held in use. Close
that application and retry.
MSI (s) (F4:B4) [15:28:07:752]: Product: DataCaptor Interface Server. The file
C:\WINDOWS\system32\mfc71u.dll is being held in use by the following process
Name: explorer , Id 1312.
Now that looks like during install, mfc71u.dll isn't installed (already
present) but an install is attempted during repair under C:\WINDOWS\system32
folder.
Thx,
Dacian
- Original Message
From: Wilson, Phil [EMAIL PROTECTED]
To: wix-users@lists.sourceforge.net
Sent: Wednesday, November 28, 2007 7:35:18 PM
Subject: Re: [WiX-users] Conditional installation of merge modules
!--
_filtered {font-family:Cambria Math;panose-1:2 4 5 3 5 4 6 3 2 4;}
_filtered {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}
_filtered {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;font-family:Times
New Roman, serif;}
a:link, span.MsoHyperlink
{color:blue;text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}
p.msochpdefault, li.msochpdefault, div.msochpdefault
{margin-right:0in;margin-left:0in;font-size:10.0pt;font-family:Times
New Roman, serif;}
span.emailstyle17
{font-family:Tahoma,
sans-serif;color:windowtext;font-weight:normal;font-style:normal;text-decoration:none
none;}
span.EmailStyle19
{font-family:Tahoma,
sans-serif;color:windowtext;font-weight:normal;font-style:normal;text-decoration:none
none;}
.MsoChpDefault
{font-size:10.0pt;}
_filtered {margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{}
--
Keeping
Wix users on the list…
It’s
not clear to my why the 7.1 Dlls would be in use by Explorer unless you are
installing them into a folder where Explorer is using them from, so you’ll
have to explain exactly where they are installed to. I don’t know what
your default is because the 71 modules can be directed most places. You don’t
have to use Orca to make them go into your app folder. The module retargetable
folder can be set to your app folder.
The
VS 2005 merge modules are completely different, and have a different install
paradigm. They are installed into the systems SxS folder and if you
include (say) the VC80 merge module the corresponding policy merge module is
also included. The VS runtime executable does things differently, but the
end result is the same – a manifest that redirects clients to the current
installed version.
Phil
Wilson
From: fiordean dacian
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 28, 2007 6:26 AM
To: Wilson, Phil
Subject: Re: [WiX-users] Conditional installation of merge modules
Do you mean installing my app
under System folder? Nope.
As for the merge modules, they are installed into their default folder. If I
have to install the 71 dlls into my app's folder, I need to modify them by hand
using Orca, right?
Actually MFC71 wasn't a typo, actually I need VC2003 stuff. I just
[WiX-users] Fw: Conditional installation of merge modules
Do you mean installing my app under System folder? Nope.
As for the merge modules, they are installed into their default folder. If I
have to install the 71 dlls into my app's folder, I need to modify them by hand
using Orca, right?
Actually MFC71 wasn't a typo, actually I need VC2003 stuff. I just mentioned
VC2005 runtime since I saw on that blog a discussion about I don't know what
policy_*.msm thing which btw isn't included with the VC2005 runtime. So forget
that...
Me either I don't know why this is happenning when repair. I was expecting
those msm's not to install each time, but rather when not present. It looks
like they are getting installed no matter. So that's why I was wondering if it's
possible to condition their installation in Wix.
Thanks,
Dacian
- Original Message
From: Wilson, Phil [EMAIL PROTECTED]
To: wix-users@lists.sourceforge.net
Sent: Tuesday, November 27, 2007 7:40:53 PM
Subject: Re: [WiX-users] Conditional installation of merge modules
!--
_filtered {font-family:Cambria Math;panose-1:2 4 5 3 5 4 6 3 2 4;}
_filtered {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}
_filtered {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;font-family:Times
New Roman, serif;}
a:link, span.MsoHyperlink
{color:blue;text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}
span.EmailStyle17
{font-family:Tahoma,
sans-serif;color:windowtext;font-weight:normal;font-style:normal;text-decoration:none
none;}
.MsoChpDefault
{font-size:10.0pt;}
_filtered {margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{}
--
Are
you installing into the System folder? The 71 Dlls can be side by side, so you
can install them into your application folder. Visual Studio 2005 support
Dlls are SxS in the WinSxS folder - they’re installed differently. Was
MFC71 a typo? That’s the Visual Studio 2003 MFC support, but elsewhere
you’re referring to 2005. I’m not sure what you’re
getting at with that “in case of a repair” – this is just at
install time, right?
Phil
Wilson
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of fiordean dacian
Sent: Tuesday, November 27, 2007 7:07 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Conditional installation of merge modules
Hi,
I'm installing MFC71, CRT and STL merge modules together with my product. The
problem I'm having is Windows Installer asks me to reboot at the end of the
installation in case of a repair since some of those modules are held in use by
Windows Explorer. At the installation, I don't have this problem. I assume is
due to the way those merge modules are made. Is there a way to avoid this?
I'm reading through blogs around Internet about policy_* merge modules (I don't
really understand why do I need all those):
http://msdn.technetweb3.orcsweb.com/astebner/archive/2007/02/13/building-an-msi-using-wix-v3-0-that-includes-the-vc-8-0-runtime-merge-modules.aspx
I downloaded VC 2005 SP1 redistributable package from Microsoft but it doesn't
install anything of that type (ie policy_* merge module files).
http://www.microsoft.com/downloads/details.aspx?familyid=200B2FD9-AE1A-4A14-984D-389C36F85647displaylang=en
Any thoughts?
Thanks,
Dacian
Be a better pen pal. Text or chat with friends inside Yahoo!
Mail. See
how.
Get easy, one-click access to your favorites.
Make Yahoo! your homepage.
Get easy, one-click access to your favorites.
Make Yahoo! your homepage.
http://www.yahoo.com/r/hs -
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Conditional installation of merge modules
Hi, I'm installing MFC71, CRT and STL merge modules together with my product. The problem I'm having is Windows Installer asks me to reboot at the end of the installation in case of a repair since some of those modules are held in use by Windows Explorer. At the installation, I don't have this problem. I assume is due to the way those merge modules are made. Is there a way to avoid this? I'm reading through blogs around Internet about policy_* merge modules (I don't really understand why do I need all those): http://msdn.technetweb3.orcsweb.com/astebner/archive/2007/02/13/building-an-msi-using-wix-v3-0-that-includes-the-vc-8-0-runtime-merge-modules.aspx I downloaded VC 2005 SP1 redistributable package from Microsoft but it doesn't install anything of that type (ie policy_* merge module files). http://www.microsoft.com/downloads/details.aspx?familyid=200B2FD9-AE1A-4A14-984D-389C36F85647displaylang=en Any thoughts? Thanks, Dacian Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how. http://overview.mail.yahoo.com/- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] service not showing after ServiceInstall
Can you manually register it? I mean something like YOUR_SERVICE.exe /REGSERVER or similar? Does it show then? For checking if at the end of the installation it was 'registered within the system', you might check you registry under HKLM\SYSTEM\CurrentControlSet\Services even though I'm not sure if this 'guarantees' the system is correctly registered. Dacian - Original Message From: davemave [EMAIL PROTECTED] To: wix-users@lists.sourceforge.net Sent: Thursday, July 26, 2007 12:56:46 PM Subject: Re: [WiX-users] service not showing after ServiceInstall I did a verbose log install but do not know where to look for service installation failure in this log. The installer ends with succes. Do you have any tips on looking into the log to see if the service is installed or not? Bob Arnson-6 wrote: davemave wrote: The msi installs succesfull, but I cannot find the service in the Services.msc snap-in. What's missing? Check a verbose log to make sure the component is being installed and the service registered. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://www.nabble.com/service-not-showing-after-ServiceInstall-tf4129869.html#a11808312 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Yahoo! oneSearch: Finally, mobile search that gives answers, not web links. http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] InstallExecuteSequence
You migh check with Orca that InstallExecuteSequence has the actions in the order you want them. Why don't you use After and Before attributes instead of Sequence? Dacian - Original Message From: Balakrishna.BK [EMAIL PROTECTED] To: wix-users@lists.sourceforge.net Sent: Thursday, July 5, 2007 1:05:28 PM Subject: [WiX-users] InstallExecuteSequence Hi, I am newbie to msi technology and I have the following question in InstallExecutesequence. I am editing my existing msi file using orca and want to swap sequence numbers of appsearch and launchcondion actual Appsearch = 400 as sequence number and Launchcondition = 117 I added a new entry in Reglocator, apsearch and launchcondition and swapped the sequence numbers. So, after modifying my new entry is Appsearch= 117 launchcondition = 400 When i save and launch this msi, i still get launch condition executed 1st in the sequence and installation fails inspite of have regkey in the system Do I need to change this sequence number in each of the language specific msi (extract mst, apply, change, and create msi)..? or modifying the final one is sufficient Thanks, Bala. Send free SMS to your Friends on Mobile from your Yahoo! Messenger. Download Now! http://messenger.yahoo.com/download.php - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Get the Yahoo! toolbar and be alerted to new email wherever you're surfing. http://new.toolbar.yahoo.com/toolbar/features/mail/index.php- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] InstallExecuteSequence
Hi Bala, I can't see any column from InstallExecuteSequence table refering to language stuff. Try and save your msi under a different name after modyfing the sequence numbers for those actions. Also, you might want to decompile your msi into a wxs file. For this you can use dark.exe (distributed with Wix) like this: dark.exe -nologo your_setup.msi product.wxs. Then check product.wxs and see what's happening. Dacian - Original Message From: Balakrishna.BK [EMAIL PROTECTED] To: wix-users@lists.sourceforge.net Sent: Thursday, July 5, 2007 2:57:22 PM Subject: Re: [WiX-users] InstallExecuteSequence Hi Dacian, I modified InstallExecuteSequence table in the order I wanted it to be, but still during installation it doesnt follow the order. I believe I am missing something basic. Also remember that this is a multi-language msi. As I already told, I am modifying the existing msi using orca. unfortunately I dont have any wxs files or the environment to generate msi. Bala. Message: 4 Date: Thu, 5 Jul 2007 04:11:31 -0700 (PDT) From: fiordean dacian Subject: Re: [WiX-users] InstallExecuteSequence To: Balakrishna.BK , wix-users@lists.sourceforge.net Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii You migh check with Orca that InstallExecuteSequence has the actions in the order you want them. Why don't you use After and Before attributes instead of Sequence? Dacian - Original Message From: Balakrishna.BK To: wix-users@lists.sourceforge.net Sent: Thursday, July 5, 2007 1:05:28 PM Subject: [WiX-users] InstallExecuteSequence Hi, I am newbie to msi technology and I have the following question in InstallExecutesequence. I am editing my existing msi file using orca and want to swap sequence numbers of appsearch and launchcondion actual Appsearch = 400 as sequence number and Launchcondition = 117 I added a new entry in Reglocator, apsearch and launchcondition and swapped the sequence numbers. So, after modifying my new entry is Appsearch = 117 launchcondition = 400 When i save and launch this msi, i still get launch condition executed 1st in the sequence and installation fails inspite of have regkey in the system Do I need to change this sequence number in each of the language specific msi (extract mst, apply, change, and create msi)..? or modifying the final one is sufficient Thanks, Bala. Here’s a new way to find what you're looking for - Yahoo! Answers - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center. http://autos.yahoo.com/green_center/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] deffered custom actions
Try something like this: CustomAction Id=CA1 Property=CA2 Value=[INSTALLDIR]/ CustomAction Id=CA2 BinaryKey=MyDll Execute=deferred DllEntry=MyFunc/ InstallExecuteSequence ... Custom Action=CA1 After=.../ Custom Action=CA2 After=CA1/ ... /InstallExecuteSequence Dacian - Original Message From: [EMAIL PROTECTED] [EMAIL PROTECTED] To: wix-users@lists.sourceforge.net Sent: Tuesday, July 3, 2007 10:50:26 AM Subject: [WiX-users] deffered custom actions i know how to send a property to my dll and print it from message box. But now i want to pass the path which user has selected to my property and so that i get it in my dll. plz help. If any one knows ,in that case i can share the code. DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Pvt. Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Pvt. Ltd. does not accept any liability for virus infected mails. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder tool. http://autos.yahoo.com/carfinder/- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Fw: deffered custom actions
So your MessageBox displays the name of the property (which is PATH) instead of C:\Program Files\Product Name, right? Make sure your property is all upercase (like PATH and not Path or anything else). Dacian - Original Message From: [EMAIL PROTECTED] [EMAIL PROTECTED] To: fiordean dacian [EMAIL PROTECTED] Sent: Tuesday, July 3, 2007 11:41:00 AM Subject: Re: [WiX-users] deffered custom actions It works .Thanks very much. In my package i have asked user for a path and now i want to pass this path as a property to my Custom Action.But here every thing i put is being treated as a string.So in my dll when i print msg box it displays the string path]] not actual path. If u understand my problem otherwise i can show u this small code. DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Pvt. Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Pvt. Ltd. does not accept any liability for virus infected mails. Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center. Get the Yahoo! toolbar and be alerted to new email wherever you're surfing. http://new.toolbar.yahoo.com/toolbar/features/mail/index.php- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Fw: deffered custom actions
Post your questions on the list pls. There are more chances for you to get help. I'm not sure about that one, you can use a property for your control and reference it from your CA to check its value: Control Id='MyRadioButton' ...Property='ARCHITECTURE' You can refer ARCHITECTURE within the CA and check its value (1 or 2) then set another property to x86 or x64 depending on that. Dacian - Original Message From: [EMAIL PROTECTED] [EMAIL PROTECTED] To: fiordean dacian [EMAIL PROTECTED] Sent: Tuesday, July 3, 2007 2:48:40 PM Subject: Re: [WiX-users] Fw: deffered custom actions Sir actually i am selection a value from radio button (Architecture ) which is (x86)(x64). Now i want to send this selected value through my Property to my Dll. I tried that publish ,,It helped partially.. what happened is that i have in my radio button 1 for x86 2 for x64 It comes under ARCHITECTURE So when i select ARCHITECTURE it gives properly 1 or 2 depending upon the right selection by user but i want him to catch x86 or x64 corrospinding to 1 or 2..how should i acheive it. CustomAction Id=MyAction.SetProperty Return=check Property=MyAction Value=[ARCHITECTURE] / DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Pvt. Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Pvt. Ltd. does not accept any liability for virus infected mails. Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV. http://tv.yahoo.com/- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Migrating files during major upgrade
Hi Kevin, I had the same (copy some configuration from a previously installed XML). What I did was I wrote a custom action reading the XML within a property than write that out within the new file. Dacian - Original Message From: Kevin Dente [EMAIL PROTECTED] To: Wix Users wix-users@lists.sourceforge.net Sent: Wednesday, June 20, 2007 6:06:15 PM Subject: [WiX-users] Migrating files during major upgrade We've got a WiX 2.0 based install, and have an upgrade scenario that I'm not sure how to accomplish. For the new version of the product, the default (configurable) install directory has changed. When upgrading existing systems, we need to copy some XML configuration info from the original install dir to the new install dir. I'm not sure of the best way to accomplish this. I've considered two options. One is to read the config info into a property and write it out to a new config file in the new location. Unfortunately, as far as I can tell the Xml* custom actions don't support reading XML files, only writing them. The other option is to copy the existing config file to the new install directory - but I'm not really sure how to do that in WiX/MSI. Any pointers? Or other approaches to consider? Thanks, Kevin - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Get the Yahoo! toolbar and be alerted to new email wherever you're surfing. http://new.toolbar.yahoo.com/toolbar/features/mail/index.php- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Fwd: Set property value, depending on the value of other properties
Will something like that work for you? CustomAction Id=CopyAIntoC Property=C Value=[A] and within InstallExecuteSequence !-- This will copy A into C if any of the A or B are set -- Custom Action=CopyAIntoC After=...A OR B/Custom Dacian - Original Message From: José Escrich [EMAIL PROTECTED] To: Bob Arnson [EMAIL PROTECTED] Cc: wix-users@lists.sourceforge.net Sent: Thursday, June 21, 2007 7:43:49 AM Subject: Re: [WiX-users] Fwd: Set property value, depending on the value of other properties Ok, but I don't know how can I set a value of a C property with one of the values A or B. I don't know if there are a custom action to do that. On 6/20/07, Bob Arnson [EMAIL PROTECTED] wrote: José Escrich wrote: I have 2 properties A and B which has some registry values. What I want is set a value for a property C using something like a condition evaluating the values of A and B. Basically, what i want i set the value of A or B in the C property if any of those is blank or empty. You can use a CustomAction/@Property,@Value and in your InstallExecuteSequence/InstallUISequence, use a condition like A OR B to check whether either property is set. -- sig://boB http://joyofsetup.com/ -- img src= http://feeds.feedburner.com/jescrichen.gif?w=3c=1bb=d7ZA/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos more. http://mobile.yahoo.com/go?refer=1GNXIC- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to automatically uninstall a Product in a WIX installer
Hi, The message you get is when you do a minor upgrade (ProductCode is the same, just version changes). In this case (minor upgrades), you have to launch your msi from the command line with like this: msiexec /i your_setup.msi REINSTALL=ALL REINSTALLMODE=vomus. If you want to completely remove your product first, a major upgrade is what you want. For this, change both product code and version for your new setup. Also, add an Upgrade tag refering to your previous version (make sure you set OnlyDetect to 'no' in there). You will probably want to schedule 'RemoveExistingProducts' custom action after 'InstallInitialize'. Dacian - Original Message From: Harm-Jan Zwinderman [EMAIL PROTECTED] To: wix-users@lists.sourceforge.net Sent: Thursday, June 14, 2007 3:24:27 PM Subject: [WiX-users] How to automatically uninstall a Product in a WIX installer Hi, I did build a WIX msi installer to install our product. However when I run this installer again I do get a message box with the text 'Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.' What I would want to happen is that the installer first would deinstall the product and then reinstalls it from the WIX msi installer. I have been playing around with the tag RemoveExistingProducts however that doesn't do the trick. Is it possible to automatically uninstall in a WIX msi installer? Best Regards, Harm-Jan Zwinderman -- Charm B.V. Kruislaan 406 1098 SM Amsterdam T +31 (0)20-751 2190 [EMAIL PROTECTED] - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. http://farechase.yahoo.com/promo-generic-14795097- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrade InstallShield package
Hi Bob, I just reviewed the REINSTALL/REINSTALLMODE which indeed is used for minor upgrades. My fault... Thanks for the help, Dacian - Original Message From: Bob Arnson [EMAIL PROTECTED] To: fiordean dacian [EMAIL PROTECTED] Cc: wix-users@lists.sourceforge.net Sent: Tuesday, June 12, 2007 8:06:26 AM Subject: Re: [WiX-users] Upgrade InstallShield package fiordean dacian wrote: 1. When double click on my new msi, it detects there is a previous product installed (there is a PREVFOUND property set I provided within the Upgrade sequence of my WiX code), but there is no message saying Another version of ... like I get when I do an upgrade with two msi files I generated with WiX but have different versions. It just goes like a normal install, even if some components are upgraded. What I'd expect is getting an error when double click (Another version...), but when launched with REINSTALL=ALL REINSTALLMODE=vomus it should work. The REINSTALL/REINSTALLMODE behavior you describe is a minor upgrade. The Upgrade/UpgradeVersion schema is used to declare a major upgrade, which removes the previous product version as part of installing the newer. Which do you want? -- sig://boB http://joyofsetup.com/ Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games. http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrade InstallShield package
Hi,
I ran into some extra problems with my InstallShield upgrade. Looking with Orca
throughout the Component table on the IS msi installation file, I saw some of
the components don't have a KeyPath set (the KeyPath column is empty). The WiX
source for my new version of the product has KeyPath set on the component
containing the same file, like below:
Component Id=Component1 Guid={GUID1}
File Id=File1 Name=File1.exe Source=...
Shortcut Id=ScFile1 Name=File1 Description=.. .../
/File
!-- just a fix for ICE43 --
Registry Id=... Root=HKCU Key=... KeyPath=yes Action=write/
/Component
Component Id=Component2 Guid={GUID2}
File Id=File2 Name=File2.exe Source=... SelfReg=1 KeyPath=yes/
/Component
Now the problem is IS component I want to upgrade contained, when the setup was
built, both File1 and File2, without a KeyPath. What I tried is I used new
GUIDs for both Component1 and Component2 in my new WiX source. What I was
expecting is:
1. File1.exe and File2.exe from the IS deployement gets removed (the Component
containing them isn't present in my new installation).
2. File1.exe and File2.exe from my new setup are deployed as they are new
components to be installed by the upgrade.
At the end of the day, none File1.exe or File2.exe are present in the
installation folder.
Am I doing something wrong here?
Dacian
- Original Message
From: Wilson, Phil [EMAIL PROTECTED]
To: wix-users@lists.sourceforge.net
Sent: Monday, June 11, 2007 11:33:04 PM
Subject: Re: [WiX-users] Upgrade InstallShield package
1. Is because this is a major upgrade and your new
product has a different ProductCode guid.
2. Is probably because you've set OnlyDetect if I
recall the syntax correctly.
Phil Wilson
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of fiordean
dacian
Sent: Monday, June 11, 2007 8:14 AM
To:
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrade
InstallShield package
Hi,
I located and opened with Orca the
cached msi file under Windows\Installer. The UpgradeCode is, of course,
different compared with the one I was using (displayed by IS UI). Now it looks
like some upgrade is done (files are replaced and on uninstall they are removed
from the system).
I have two questions though related to the upgrade
process:
1. When double click on my new msi, it detects there is a
previous product installed (there is a PREVFOUND property set I provided within
the Upgrade sequence of my WiX code), but there is no message saying Another
version of ... like I get when I do an upgrade with two msi files I generated
with WiX but have different versions. It just goes like a normal install, even
if some components are upgraded. What I'd expect is getting an error when
double
click (Another version...), but when launched with REINSTALL=ALL
REINSTALLMODE=vomus it should work.
2. At the end of the installation, I
have two entries within Add/Remove Programs list: one with the previous name
for
the product and under it the new name for the product. There is just the Remove
button for the previous product version (by design) and clicking on it just
removes the entry from the Add/Remove list (without an installation or
whatever). What I'd expect is no entry for the previous version in the
list.
Any ideas why?
Thx,
Dacian
-
Original Message
From: Wilson, Phil
[EMAIL PROTECTED]
To:
wix-users@lists.sourceforge.net
Sent: Friday, June 8, 2007 8:36:03
PM
Subject: Re: [WiX-users] Upgrade InstallShield package
If you can locate the cached MSI file in
Windows\installer, opening it with Orca will show the UpgradeCode in the
Property table. That might help see if you're on the right track.
Versions are also another reason why a major upgrade won't detect an older one.
Phil Wilson
From: fiordean dacian
[mailto:[EMAIL PROTECTED]
Sent: Friday, June 08, 2007 10:00
AM
To: Wilson, Phil;
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrade
InstallShield package
Hi
Phil,
Looking through IS log I see ALLUSERS with a value of
1.
Running your script displays Context 4, so there is a per-machine
install done by IS. I have ALLUSERS set to 1 in my WiX source, but there is no
detection for the product IS created.
A strange thing I saw running your
script: the product GUID displayed by your script next to the product name I'm
interested is something like
this:
{B607D95A-A73C-444B-87BA-B4E9DBAC4DEE}
while the product
code displayed by IS within its UI
is:
{F1872E85-C933-44D4-8B88-85D68DD9B103}
which makes me think
the UpgradeCode on which I base my Upgrade element to detect the
previous version installed out there is wrong (I take it from the same IS UI
which displays the wrong product code above). I don't see a property for
retrieving the UpgradeCode within the WindowsInstaller automation interface in
order to check if the UpgradeCode
Re: [WiX-users] Upgrade InstallShield package
Hi,
I located and opened with Orca the cached msi file under Windows\Installer. The
UpgradeCode is, of course, different compared with the one I was using
(displayed by IS UI). Now it looks like some upgrade is done (files are
replaced and on uninstall they are removed from the system).
I have two questions though related to the upgrade process:
1. When double click on my new msi, it detects there is a previous product
installed (there is a PREVFOUND property set I provided within the Upgrade
sequence of my WiX code), but there is no message saying Another version of
... like I get when I do an upgrade with two msi files I generated with WiX
but have different versions. It just goes like a normal install, even if some
components are upgraded. What I'd expect is getting an error when double click
(Another version...), but when launched with REINSTALL=ALL
REINSTALLMODE=vomus it should work.
2. At the end of the installation, I have two entries within Add/Remove
Programs list: one with the previous name for the product and under it the new
name for the product. There is just the Remove button for the previous product
version (by design) and clicking on it just removes the entry from the
Add/Remove list (without an installation or whatever). What I'd expect is no
entry for the previous version in the list.
Any ideas why?
Thx,
Dacian
- Original Message
From: Wilson, Phil [EMAIL PROTECTED]
To: wix-users@lists.sourceforge.net
Sent: Friday, June 8, 2007 8:36:03 PM
Subject: Re: [WiX-users] Upgrade InstallShield package
If you can locate the cached MSI file in
Windows\installer, opening it with Orca will show the UpgradeCode in the
Property table. That might help see if you're on the right track.
Versions are also another reason why a major upgrade won't detect an older one.
Phil Wilson
From: fiordean dacian
[mailto:[EMAIL PROTECTED]
Sent: Friday, June 08, 2007 10:00
AM
To: Wilson, Phil;
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrade
InstallShield package
Hi
Phil,
Looking through IS log I see ALLUSERS with a value of
1.
Running your script displays Context 4, so there is a per-machine
install done by IS. I have ALLUSERS set to 1 in my WiX source, but there is no
detection for the product IS created.
A strange thing I saw running your
script: the product GUID displayed by your script next to the product name I'm
interested is something like
this:
{B607D95A-A73C-444B-87BA-B4E9DBAC4DEE}
while the product
code displayed by IS within its UI
is:
{F1872E85-C933-44D4-8B88-85D68DD9B103}
which makes me think
the UpgradeCode on which I base my Upgrade element to detect the
previous version installed out there is wrong (I take it from the same IS UI
which displays the wrong product code above). I don't see a property for
retrieving the UpgradeCode within the WindowsInstaller automation interface in
order to check if the UpgradeCode IS installed product
has.
Dacian
-
Original Message
From: Wilson, Phil
[EMAIL PROTECTED]
To:
wix-users@lists.sourceforge.net
Sent: Tuesday, June 5, 2007 7:22:22
PM
Subject: Re: [WiX-users] Upgrade InstallShield package
InstallShield has a custom action (ISSetAllUsers) that
sets ALLUSERS, so looking in the raw MSI file won't tell you
what's going on. It's mostly used when it upgrades previous products, but
nevertheless I recommend
looking at a log to see what's actually happening to the ALLUSERS value
during the InstallShield MSI install.
This script might help. If it reports a
context of 4 if the product is installed per-machine, 2 if for a user and
unmanaged.
Option Explicit
Public installer,
fullmsg, comp, prod, a, fso, pname, ploc, pid,contxt, sid, psorce, pcache,
pvers
Set fso =
CreateObject(Scripting.FileSystemObject)
Set a =
fso.CreateTextFile(prodex.txt, True)
' Connect to Windows Installer
object
Set installer =
CreateObject(WindowsInstaller.Installer)
a.writeline (Products)
'on
error resume next
For Each prod In installer.ProductsEx(, ,
7)
pid = prod.ProductCode
contxt =
prod.Context
sid=prod.usersid
pname =
prod.InstallProperty(InstalledProductName)
psorce=prod.InstallProperty( InstallSource)
ploc
=prod.InstallProperty( InstallLocation)
pcache =
prod.InstallProperty(LocalPackage)
pvers=prod.InstallProperty(VersionString)
a.writeline (pid
pname pvers installed at
ploc from psorce Context
contxt)
Next
Phil Wilson
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of fiordean
dacian
Sent: Tuesday, June 05, 2007 9:46 AM
To:
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrade
InstallShield package
Hi
Bob,
ALLUSERS property is not set within the .msi file InstallShield
generates, which means there was a per-user installation (there is something
like ApplicationUsers property with the value ALLUSERS). My .msi uses ALLUSERS
with a value
Re: [WiX-users] Upgrade InstallShield package
Hi Phil,
Looking through IS log I see ALLUSERS with a value of 1.
Running your script displays Context 4, so there is a per-machine install
done by IS. I have ALLUSERS set to 1 in my WiX source, but there is no
detection for the product IS created.
A strange thing I saw running your script: the product GUID displayed by your
script next to the product name I'm interested is something like this:
{B607D95A-A73C-444B-87BA-B4E9DBAC4DEE}
while the product code displayed by IS within its UI is:
{F1872E85-C933-44D4-8B88-85D68DD9B103}
which makes me think the UpgradeCode on which I base my Upgrade element to
detect the previous version installed out there is wrong (I take it from the
same IS UI which displays the wrong product code above). I don't see a
property for retrieving the UpgradeCode within the WindowsInstaller automation
interface in order to check if the UpgradeCode IS installed product has.
Dacian
- Original Message
From: Wilson, Phil [EMAIL PROTECTED]
To: wix-users@lists.sourceforge.net
Sent: Tuesday, June 5, 2007 7:22:22 PM
Subject: Re: [WiX-users] Upgrade InstallShield package
InstallShield has a custom action (ISSetAllUsers) that
sets ALLUSERS, so looking in the raw MSI file won't tell you
what's going on. It's mostly used when it upgrades previous products, but
nevertheless I recommend
looking at a log to see what's actually happening to the ALLUSERS value
during the InstallShield MSI install.
This script might help. If it reports a
context of 4 if the product is installed per-machine, 2 if for a user and
unmanaged.
Option Explicit
Public installer,
fullmsg, comp, prod, a, fso, pname, ploc, pid,contxt, sid, psorce, pcache,
pvers
Set fso =
CreateObject(Scripting.FileSystemObject)
Set a =
fso.CreateTextFile(prodex.txt, True)
' Connect to Windows Installer
object
Set installer =
CreateObject(WindowsInstaller.Installer)
a.writeline (Products)
'on
error resume next
For Each prod In installer.ProductsEx(, ,
7)
pid = prod.ProductCode
contxt =
prod.Context
sid=prod.usersid
pname =
prod.InstallProperty(InstalledProductName)
psorce=prod.InstallProperty( InstallSource)
ploc
=prod.InstallProperty( InstallLocation)
pcache =
prod.InstallProperty(LocalPackage)
pvers=prod.InstallProperty(VersionString)
a.writeline (pid
pname pvers installed at
ploc from psorce Context
contxt)
Next
Phil Wilson
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of fiordean
dacian
Sent: Tuesday, June 05, 2007 9:46 AM
To:
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrade
InstallShield package
Hi
Bob,
ALLUSERS property is not set within the .msi file InstallShield
generates, which means there was a per-user installation (there is something
like ApplicationUsers property with the value ALLUSERS). My .msi uses ALLUSERS
with a value of 1 (so per-machine install). I removed ALLUSERS property from my
.msi.
Also, I switched for a major upgrade now (updated Product
UpgradeCode GUIDs and Version), here is the Upgrade sequence:
Upgrade
Id=C466B4D2-CFF9-4880-9910-D95248AAABEB
UpgradeVersion OnlyDetect=no Property=PREVFOUND Maximum=1.0.1
IncludeMaximim=no/
/Upgrade
Upgrade
Id=D1EF72C4-8A32-4526-9F7F-396EC5DAC5C3
UpgradeVersion OnlyDetect=yes Property=NEWERFOUND Minimum=2.0.0
IncludeMinimum=yes/
/Upgrade
The first Upgrade refers to
previous InstallShield package out there, second is for current
version.
Well, I had no success yet.
Dacian
-
Original Message
From: Bob Arnson [EMAIL PROTECTED]
To:
fiordean dacian [EMAIL PROTECTED]
Cc:
wix-users@lists.sourceforge.net
Sent: Tuesday, June 5, 2007 5:23:07
PM
Subject: Re: [WiX-users] Upgrade InstallShield package
fiordean
dacian wrote:
That
would remove my previous installation, right? I'm not sure I want that since
the user might have configured the product (registry keys, config files,
etc.)
and I don't want that to be removed. I just want an upgrade of what's out
there.
Unless you kept all your GUIDs and IDs
the same, you need to do a major upgrade to get to a clean slate
install.
On
top of that, it still doesn't look like the previous installation was
detected
(the PREVFOUND property doesn't have a GUID attached to it and no upgarde is
proposed, just normal install).
The most common
reason is that you're trying to mix and match values of ALLUSERS. MSI doesn't
support a per-user install upgrading a per-machine install (or vice versa).
--
sig://boB
http://joyofsetup.com/
Sick sense of humor? Visit Yahoo! TV's Comedy
with an Edge to see what's on, when.
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2
Re: [WiX-users] Is it possible to detect if a software is currentlyrunning ?
Hopefully Windows Installer does this for any running application you're trying
to uninstall. The problem is you don't have a mecanism in WiX, other than a
custom action, which might help in detecting whether the browser is open.
Dacian
- Original Message
From: Palit [EMAIL PROTECTED]
To: fiordean dacian [EMAIL PROTECTED]; WiX-users@lists.sourceforge.net
Sent: Wednesday, June 6, 2007 6:03:36 PM
Subject: Re: [WiX-users] Is it possible to detect if a software is
currentlyrunning ?
DIV {
MARGIN:0px;}
Thanks
This what I thought and done but when I Uninstall my WebPlayer which it is
running in a browser,
installer can tell me that I must quit the active browser to continue
...
so there is a mecanism somehere
Nicolas.
- Original Message -
From:
fiordean
dacian
To: WiX-users@lists.sourceforge.net
Sent: Tuesday, June 05, 2007 4:57
PM
Subject: Re: [WiX-users] Is it possible
to detect if a software is currentlyrunning ?
Hi
Nicolas,
As far as I know, you'll have to write a custom action for
that.
Good luck,
Dacian
-
Original Message
From: Palit [EMAIL PROTECTED]
To: WiX-users@lists.sourceforge.net
Sent:
Tuesday, June 5, 2007 3:36:14 PM
Subject: [WiX-users] Is it possible to
detect if a software is currently running ?
Hi,
I'm doing a wix installer for a
Web-Player.
Is it possible during the beginning of the
process of installation to detect the running browsers ?
Or I must do a custom action ?
Thanks
Nicolas,
-
This
SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE
version of DB2 express and take
control of your XML. No limits. Just data.
Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing
list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Choose the right car based on your needs. Check out Yahoo!
Autos new Car Finder tool.
-
This
SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE
version of DB2 express and take
control of your XML. No limits. Just data.
Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing
list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Yahoo! oneSearch: Finally, mobile search
that gives answers, not web links.
http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to override RegistrySearch property?
1) Is my CA correct?
Yes
2) How do I sequence the CA so it executes before my UI is displayed?
Put it under InstallUISequence
3) How do I condition the CA to only execute if MY_REAL_VALUE is empty?
Custom Action= MyAssign After=CostInitializeNOT MY_REAL_VALUE/Custom
Good luck,
Dacian
- Original Message
From: Dale Quigg [EMAIL PROTECTED]
To: wix-users@lists.sourceforge.net
Sent: Thursday, June 7, 2007 5:19:37 PM
Subject: [WiX-users] How to override RegistrySearch property?
!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;font-family:Times
New Roman;}
a:link, span.MsoHyperlink
{color:blue;text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{margin:0in;margin-bottom:.0001pt;font-size:10.0pt;font-family:Courier
New;}
_filtered {margin:1.0in 77.95pt 1.0in 77.95pt;}
div.Section1
{}
--
Hi,
I have a custom dialog that includes an edit box that is pre-populated with
the value of a property [MY_REAL_VALUE].
Another property, MY_FOUND_VALUE, is set via RegistrySearch.
If the user did not supply MY_REAL_VALUE in the command line, I want to
set MY_REAL_VALUE = MY_FOUND_VALUE. This way the custom dialog will have
the correct initial value.
Following the example in Section 3.2 of the WiX tutorial, I created a
custom action to set MY_REAL_VALUE = MY_FOUND_VALUE.
CustomAction Id=MyAssign Property='MY_REAL_VALUE'
Value='[MY_REAL_VALUE]' /
I'm sequencing it like this;
Custom Action= MyAssign After=CostInitialize1/Custom
(yes I know the condition is incorrect)
but this custom action does not run before my dialog is displayed.
Three questions;
1) Is my CA correct?
2) How do I sequence the CA so it executes before my UI is displayed?
3) How do I condition the CA to only execute if MY_REAL_VALUE is empty?
Thanks for any help.
Dale
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Shape Yahoo! in your own image. Join our Network Research Panel today!
http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrade InstallShield package
Hi Rob, That would remove my previous installation, right? I'm not sure I want that since the user might have configured the product (registry keys, config files, etc.) and I don't want that to be removed. I just want an upgrade of what's out there. On top of that, it still doesn't look like the previous installation was detected (the PREVFOUND property doesn't have a GUID attached to it and no upgarde is proposed, just normal install). Thx, Dacian - Original Message From: Rob Hamflett [EMAIL PROTECTED] To: wix-users@lists.sourceforge.net Sent: Tuesday, June 5, 2007 10:36:43 AM Subject: Re: [WiX-users] Upgrade InstallShield package You want to remove OnlyDetect from the check for a previous version, and make sure you have RemoveExistingProducts scheduled. Rob fiordean dacian wrote: Hi, I have a package build with InstallShield deployed out there I'd like to upgrade using an msi authored with WiX. The deployed package has a version like '1.0.1', the one I'm working is 1.0.2. Here is the Upgrade sequence in my wxs file: Upgrade Id=C466B4D2-CFF9-4880-9910-D95248AAABEB UpgradeVersion OnlyDetect=yes Property=PREVFOUND Maximum=1.0.2 IncludeMaximum=no/ UpgradeVersion OnlyDetect=yes Property=NEWERFOUND Minimum=1.0.2 IncludeMinimum=yes/ /Upgrade The Id attribute value of Upgrade tag is the same as the one displayed within InstallShield UI's for the upgrade code of the package created with it. As far as I understand (http://www.tramontana.co.hu/wix/lesson4.php), the PREVFOUND property should have attached the Product GUID during FindRelatedProducts action. While looking through the logs, nothing appears to be found and no upgrade is performed. All that is logged related to PREVFOUND is this: SecureCustomProperties = NEWERFOUND;PREVFOUND Any ideas? Thx, Dacian Luggage? GPS? Comic books? Check out fitting gifts for grads http://us.rd.yahoo.com/evt=48249/*http://search.yahoo.com/search?fr=oni_on_mailp=graduation+giftscs=bz at Yahoo! Search. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Don't get soaked. Take a quick peak at the forecast with the Yahoo! Search weather shortcut. http://tools.search.yahoo.com/shortcuts/#loc_weather- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Is it possible to detect if a software is currently running ?
Hi Nicolas, As far as I know, you'll have to write a custom action for that. Good luck, Dacian - Original Message From: Palit [EMAIL PROTECTED] To: WiX-users@lists.sourceforge.net Sent: Tuesday, June 5, 2007 3:36:14 PM Subject: [WiX-users] Is it possible to detect if a software is currently running ? Hi, I'm doing a wix installer for a Web-Player. Is it possible during the beginning of the process of installation to detect the running browsers ? Or I must do a custom action ? Thanks Nicolas, - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Luggage? GPS? Comic books? Check out fitting gifts for grads at Yahoo! Search http://search.yahoo.com/search?fr=oni_on_mailp=graduation+giftscs=bz- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrade InstallShield package
Hi Bob, ALLUSERS property is not set within the .msi file InstallShield generates, which means there was a per-user installation (there is something like ApplicationUsers property with the value ALLUSERS). My .msi uses ALLUSERS with a value of 1 (so per-machine install). I removed ALLUSERS property from my .msi. Also, I switched for a major upgrade now (updated Product UpgradeCode GUIDs and Version), here is the Upgrade sequence: Upgrade Id=C466B4D2-CFF9-4880-9910-D95248AAABEB UpgradeVersion OnlyDetect=no Property=PREVFOUND Maximum=1.0.1 IncludeMaximim=no/ /Upgrade Upgrade Id=D1EF72C4-8A32-4526-9F7F-396EC5DAC5C3 UpgradeVersion OnlyDetect=yes Property=NEWERFOUND Minimum=2.0.0 IncludeMinimum=yes/ /Upgrade The first Upgrade refers to previous InstallShield package out there, second is for current version. Well, I had no success yet. Dacian - Original Message From: Bob Arnson [EMAIL PROTECTED] To: fiordean dacian [EMAIL PROTECTED] Cc: wix-users@lists.sourceforge.net Sent: Tuesday, June 5, 2007 5:23:07 PM Subject: Re: [WiX-users] Upgrade InstallShield package fiordean dacian wrote: That would remove my previous installation, right? I'm not sure I want that since the user might have configured the product (registry keys, config files, etc.) and I don't want that to be removed. I just want an upgrade of what's out there. Unless you kept all your GUIDs and IDs the same, you need to do a major upgrade to get to a clean slate install. On top of that, it still doesn't look like the previous installation was detected (the PREVFOUND property doesn't have a GUID attached to it and no upgarde is proposed, just normal install). The most common reason is that you're trying to mix and match values of ALLUSERS. MSI doesn't support a per-user install upgrading a per-machine install (or vice versa). -- sig://boB http://joyofsetup.com/ Be a PS3 game guru. Get your game face on with the latest PS3 news and previews at Yahoo! Games. http://videogames.yahoo.com/platform?platform=120121- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WixUI_Mode InstallDir
Hi, VerifyReadyDlg.wxs has a Back button control which publish a NewDialog event like this: Control Id=Back Type=PushButton... ... Publish Event=NewDialog Value=[WixUI_VerifyReadyDlg_BackInstallDir]NOT Installed AND WixUI_Mode=InstallDir/Publish ... /Control Building with Mondo UI, the WixUI_Mode property is set to WixUI_Mondo, so there is no chance to go back actually :) Is this a bug? Dacian Got a little couch potato? Check out fun summer activities for kids. http://search.yahoo.com/search?fr=oni_on_mailp=summer+activities+for+kidscs=bz - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WixUI_Mode InstallDir
Hi Bob, Got it :) As I skip Custom/Typical/Complete dialog, the Back button doesn't execute anything since WixUI_InstallMode property isn't set. Cheers, Dacian - Original Message From: Bob Arnson [EMAIL PROTECTED] To: fiordean dacian [EMAIL PROTECTED] Cc: wix-users@lists.sourceforge.net Sent: Friday, June 1, 2007 5:38:58 PM Subject: Re: [WiX-users] WixUI_Mode InstallDir fiordean dacian wrote: VerifyReadyDlg.wxs has a Back button control which publish a NewDialog event like this: Control Id=Back Type=PushButton... ... Publish Event=NewDialog Value=[WixUI_VerifyReadyDlg_BackInstallDir]NOT Installed AND WixUI_Mode=InstallDir/Publish ... /Control Building with Mondo UI, the WixUI_Mode property is set to WixUI_Mondo, so there is no chance to go back actually :) Is this a bug? WiX v2 has eight different possible back actions based on which dialog set is in use, which type was chosen in WixUI_Mondo, and which maintenance operation is being performed. -- sig://boB http://joyofsetup.com/ Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and lay it on us. http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using heat.exe as part of an automated build process
Scott, Not everything that goes into the installer is COM and self registration. Imagine you have a folder containing hundreds of html and gif files for your product documentation. Now having a tool for automating the 'harvesting' process such that every time you add few gifs to that folder, the tool keeps the GUIDs for existing components and only creates new GUIDs for the gifs you added. It seems to me like the solution is a catalog component, which it's not that easy to implement (no component rules breaking). Dacian - Original Message From: Scott Palmer [EMAIL PROTECTED] To: Rob Mensching [EMAIL PROTECTED] Cc: wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net Sent: Tuesday, May 22, 2007 10:08:59 PM Subject: Re: [WiX-users] Using heat.exe as part of an automated build process The problem here is that Microsoft tools are already in the habit of automatic code generation - and they all are designed to produce code for SELF REGISTRATION. The process of self registration is effectively encouraged by the development environment. Now if the development process has to change, fine. But then we are forced to throw out a great deal of the support in Visual Studio for building COM DLLs. What replaces what was taken away? Heat is the closest thing I've found so far and I fully understand that trying to extract the needed information from the final code like it does can be problematic. The point is it is a *huge* step backwards in productivity to go from SelfReg DLLs to needing every developer trained in WiX so they can manually tweak the installer every time they make a relevant change to their COM DLL, let alone that they must now remember that this is even necessary. Other processes could be put in place so the COM developer doesn't need to learn WiX but there will still be added steps and opportunity for things to go wrong. When you write: I have yet to see an automated code generation tool that can just point at any application of any complexity and go, Oh, that's a FizzlyBear and it needs to be installed, uninstalled, upgraded, patched, and handle rollback like this. Oh, and it needs to be per-user/per-machine and store state in this location and… and… and… If you were talking install, uninstall and rollback, then that's an excellent argument for using SelfReg. Everything is nicely self-contained in the DLL and no installer-related tool needs to get too complex. Patching or anything else short of a complete uninstall followed by a re-install is something I'm not interested in. It's asking for trouble and simply not worth the effort. I've seen the writings discouraging CustomActions on the grounds that they are just to hard to get right if you need to account for all of those scenarios and I believe it. Anyway... I'm just looking for a build process, including creating the installer, that doesn't suck... Something as simple as a tool that will take the .rgs files from my visual studio projects and convert them to the appropriate WiX code might work. I don't know yet. All I see is that the rules are changing and it's making things difficult. Code Devination is something that was already there when I used SelfReg... and it was working fine... but now we can't use it. The tools we have to use don't do the job they used to, because they only support SelfReg. We have the source for the ATL register and unregister code.. I wonder if a tool like Heat couldn't just find all the .rgs resources in a DLL and derive the WiX code from them? Perhaps I will write something like that to put in my automated build.. that way the ATL COM wizard could almost be used without any more manual tweaking. It turns out the wizards are buggy and screw up the .rgs files too... putting different GUIDs in the IDL and .rgs files when the GUID should have been matched, but that broke self registration as well, so the developers know to fix that already. Scott On 5/21/07, Rob Mensching [EMAIL PROTECTED] wrote: WiX is intended to be used in an automated build system. It fits in extremely well with every automated build process that I've been introduced to. What you appear to be looking for is an automated code generation process. Code generation is a completely different problem than building. Code generation is about divining what a developer is thinking (or at least should be thinking) and writing the code for him or her. The WiX toolset does not include any good automated code generation tools. There are tools (namely heat.exe, and dark.exe if you start with an MSI) to help developers capture large amounts of data and translate that into .wxs code. But those tools are designed to be guided by a developer, not run blindly in an automated build process. Of course, the results of the tools can be checked into source control and then operated on in an automated build system. Note that writing a automated code
Re: [WiX-users] MSI uninstall OR update previous application version if exists
Hi, - How does install works, i see i have the product GUID, the Version and the UpgradeCode, how does the installer manages those attributes ? Pretty well... - How do i know if the user had the application installed and is upgrading or reinstalling the same version ? (i want to be able to backup and restore some files if that is the case) You can condition certain fo your custom actions using 'INSTALLED' to execute it only when the product is installed and 'NOT INSTALLED' to execute it when the product isnt' installed. You might want to check this for a list of available properties Windows Installer uses: http://msdn2.microsoft.com/en-us/library/aa370905.aspx - Is the previous version automatically uninstalled before installing a new version, are the files that changed replaced, the new files overwrite the old ones? No. You need to specify Upgrade tag. Assuming your previous app had an upgrade code, you specify which of the previous versions you want uninstalled by using the OnlyDectect attribute with the value 'no'. No problem, Dacian __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] UI: Features in a ListBox
Hi Bob, How to I know within the AddLocal and Remove events for the Next button which entry is selected in the listbox? Sketch: Control Id=ListBox Type=ListBox ... Property=LISTBOXVALUES ListBox ListItem Text=Desc. of feature1 Value=Feature1/ ListItem Text=Desc of Feature2 Value=Feature2/ /ListBox /Control ... Control Id=Next Type=PushButton Publish Event=AddLocal Value=Feature1LISTBOXVALUES=Feature1/Publish Publish Event=AddLocal Value=Feature2LISTBOXVALUES=Feature2/Publish Publish Event=Remove Value=Feature1LISTBOXVALUESFeature1/Publish Publish Event=Remove Value=Feature2LISTBOXVALUESFeature2/Publish /Control ??? Thx, Dacian 1. Modify the SetupTypeDlg.wxs such that Typical/Custom/Complete buttons are not displayed but rather a simple ListBox having the list of features I want to install listed in there. The UI manipulation it's ok, but I don't figure how I could link the features in? You have to list the items in ListItem elements. 2. I want the ListBox above behave like 'SelectionTree' from CustomizeDlg.wxs in that when one of the entries (features) gets clicked, the description is diplayed next to it. There doesn't appear to be an event that list boxes publish to support this. Also, on Next button click I want to get out the selected features and install only those, of course :) Publish control events for the Next button to AddLocal and/or Remove the appropriate features. -- sig://boB http://bobs.org __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] UI: Features in a ListBox
Hi, I'm trying to achieve the following: 1. Modify the SetupTypeDlg.wxs such that Typical/Custom/Complete buttons are not displayed but rather a simple ListBox having the list of features I want to install listed in there. The UI manipulation it's ok, but I don't figure how I could link the features in? 2. I want the ListBox above behave like 'SelectionTree' from CustomizeDlg.wxs in that when one of the entries (features) gets clicked, the description is diplayed next to it. Also, on Next button click I want to get out the selected features and install only those, of course :) Any thoughts? Thx, Dacian __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Port monitor + printer driver
Isn't that your custom action is not scheduled correctly? I mean you should instruct the system to create a port monitor once your 'monitor file' was extracted from msi, right? Dacian - Original Message From: Friedrich Dominicus [EMAIL PROTECTED] To: wix-users@lists.sourceforge.net Sent: Wednesday, April 4, 2007 7:03:26 AM Subject: Re: [WiX-users] Port monitor + printer driver fiordean dacian [EMAIL PROTECTED] writes: I guess this is rather a system problem than Windows Installer. The quick answer is yes, you can install your printer monitor and driver from one installer file. Ok, if that does work how? Is this accepted by the system? Problem: the port monitor has to find it's way into the System32 folder but the files are not installed at least up to MsiProcessDrivers and as I was suprised to see much later. So while running a custom action to add the Monitor the file with the monitor is still not accessible on the disk. It's in the .msi file of course. But it seems there is no easy way to just pick it out and install it manually You will have to check that yourself. I did and therfor I asked if there is a way. Cause I did not found it. Regards Friedrich - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/features_spam.html- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] enter user into registry
U can very well set registry entries from a custom action :) Dacian - Original Message From: Some user [EMAIL PROTECTED] To: wix-users@lists.sourceforge.net Sent: Wednesday, April 4, 2007 9:03:37 AM Subject: [WiX-users] enter user into registry how do I enter something the user puts into an edit field into the registry somewhere? Using a custom action I cannot add registry entries? -- View this message in context: http://www.nabble.com/enter-user-into-registry-tf3524223.html#a9832070 Sent from the wix-users mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Finding fabulous fares is fun. Let Yahoo! FareChase search your favorite travel sites to find flight and hotel bargains. http://farechase.yahoo.com/promo-generic-14795097- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Port monitor + printer driver
I guess this is rather a system problem than Windows Installer. The quick answer is yes, you can install your printer monitor and driver from one installer file. Is this accepted by the system? You will have to check that yourself. Dacian - Original Message From: Friedrich Dominicus [EMAIL PROTECTED] To: wix-users@lists.sourceforge.net Sent: Tuesday, April 3, 2007 5:53:45 PM Subject: [WiX-users] Port monitor + printer driver Ok, here we go again. Is there anothe way to install a port monitor and a printer driver from one installer file. Or do one has to write setup program which internally first run msiexec on the port monitor and afterwards the printer driver, in which one then can run a custom action to add the PrinterMonitor and a Printer? Regards Friedrich - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/features_spam.html- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapping to install .net 2.0-sample and best practices?
I don't know if you tried this already (I didn't), but there is also an msistuff project under Platform SDK which works with the bootstrapper you're talking about. msistuff allows you to modify the values for the resources setup.exe uses (basically you can configure your bootstrapper). Have a look at the Readme file under msistuff on how to use it. As far as I know, the bootstrapper from Platform SDK doesn't check for .Net Framework presence, but you should be able to add that easily. Dacian - Original Message From: Chris Bardon [EMAIL PROTECTED] To: wix-users@lists.sourceforge.net Sent: Tuesday, March 20, 2007 3:52:02 PM Subject: [WiX-users] Bootstrapping to install .net 2.0-sample and best practices? I have some applications that depend on .net 2.0 being installed, and I have an idea of how I'd like to have things work. A setup file, deployed from an intranet site will check for the prerequisites, and then once they are installed/verified, download and run my MSI with the command line switches that I specify (if, for example, I want to pass some property values in on the command line). I understand that visual studio has a bootstrapper included that should help with this, but I can't seem to find anything that really talks about how to use it with your own MSI package. Is there a sample out there of how to use the VS bootstrapper? - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Don't pick lemons. See all the new 2007 cars at Yahoo! Autos. http://autos.yahoo.com/new_cars.html - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Help getting upgrades to work
Hi Alex,
You might want to add OnlyDetect='no' attribute for the first UpgradeVersion
tag, something like this:
Upgrade Id=...
UpgradeVersion OnlyDetect=no Minimum=0.0.0.0 IncludeMinimum=yes
.../
UpgradeVersion OnlyDetect=yes
Minimum=0.0.$(var.PRODUCTBUILDVERSION) .../
/Upgrade
If I don't miss anything, this will uninstall your previous version so that is
not present in Add/Remove list anymore.
Cheers,
Dacian
- Original Message
From: Alex Henderson [EMAIL PROTECTED]
To: wix-users@lists.sourceforge.net
Sent: Tuesday, February 27, 2007 10:44:03 PM
Subject: Re: [WiX-users] Help getting upgrades to work
!--
_filtered {font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
_filtered {font-family:Cambria Math;
panose-1:2 4 5 3 5 4 6 3 2 4;}
_filtered {font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
_filtered {font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:Times New Roman,serif;}
a:link, span.MsoHyperlink
{
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{
color:purple;
text-decoration:underline;}
p
{
margin-right:0cm;
margin-left:0cm;
font-size:12.0pt;
font-family:Times New Roman,serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:Times New Roman,serif;}
span.EmailStyle19
{
font-family:Calibri,sans-serif;
color:#1F497D;}
span.EmailStyle20
{
font-family:Calibri,sans-serif;
color:#1F497D;}
span.EmailStyle21
{
font-family:Calibri,sans-serif;
color:#1F497D;}
.MsoChpDefault
{
font-size:10.0pt;}
_filtered {
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{}
_filtered {
}
_filtered {
text-indent:-18.0pt;
font-family:Calibri,sans-serif;
}
_filtered {
text-indent:-18.0pt;}
_filtered {
text-indent:-18.0pt;}
_filtered {
text-indent:-18.0pt;}
_filtered {
text-indent:-18.0pt;}
_filtered {
text-indent:-18.0pt;}
_filtered {
text-indent:-18.0pt;}
_filtered {
text-indent:-18.0pt;}
_filtered {
text-indent:-18.0pt;}
_filtered {
}
_filtered {
text-indent:-18.0pt;
font-family:Calibri,sans-serif;
}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--
Thanks Mike,
Ok, just tried that and the installer runs when a previous
version is installed, which is great... however both version appear in the
add/remove
programs menu now, so it appears changing the product Id has caused MSI to
think its an entirely different product?
Any ideas what Im doing wrong... and out of curiosity,
how does MSI know a previous version of the same product is installed if the
products identifier is no longer the same...(does it use the upgrade code of
the previous installed version / this version to match up?
Chez,
-
Alex
From: Mike Poulson
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, 28 February 2007 10:28 a.m.
To: 'Alex Henderson'; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Help getting upgrades to work
Change your product id. What you are doing is a Major
upgrade in the eyes of MSI.
Mike Poulson
Network Engineer
Tableau Software
400
North 34th Street, Suite 200
Seattle, WA 98103
206 633 3400 x.556
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Alex Henderson
Sent: Tuesday, February 27, 2007 1:12 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Help getting upgrades to work
Im still getting to grips with WiX... my current problem
is trying to figure out how I can get upgrades to work.
What Im looking to do is just have later versions of the
same product uninstall the previously version and install the new version (At
this point Id be quite happy if it was silent...).. heres what
Ive got so far, the PRODUCTBUILDVERSION variable is a 2 part
version number (such as 9.122) with the last part being aligned with our build
numbers.
So I did this:
Upgrade Id=58acbe6b-ffd2-4c7d-97a3-6b16f7d76384
UpgradeVersion Minimum=0.0.0.0
IncludeMinimum=yes
Maximum=0.0.$(var.PRODUCTBUILDVERSION)
IncludeMaximum=no
Property=PREVIOUSVERSIONFOUND/
UpgradeVersion OnlyDetect=yes
Property=NEWERVERSIONFOUND
Minimum=0.0.$(var.PRODUCTBUILDVERSION)
IncludeMinimum=no/
/Upgrade
And then...
CustomAction Id=NoDowngrade Error=A later version
of [ProductName] is already installed! /
InstallExecuteSequence
Custom Action=NoDowngrade
Re: [WiX-users] Reg. Disabling Remove from Windows Defender, and Upgrade feature
For the new version to uninstall the previous, an Upgrade tag is needed with an UpgradeVersion tag under it having the OnlyDetect attribute set to 'no': Upgrade Id=UPGRADE_CODE_FROM_PREV_SETUP UpgradeCode OnlyDetect=no Maximum=1.1.0 IncludeMaximum=no/ /Upgrade Note that Upgrade tag's Id attribute refers to previous setup's UpgradeCode and not Product Guid (Product tag's Id attribute). Dacian - Original Message From: Levi Wilson [EMAIL PROTECTED] To: Vidhya Sagar Bhogavalli (Infosys Technologies Ltd) [EMAIL PROTECTED] Cc: Kansana Hariharan (Infosys Technologies Ltd) [EMAIL PROTECTED]; wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net Sent: Wednesday, February 21, 2007 3:50:50 PM Subject: Re: [WiX-users] Reg. Disabling Remove from Windows Defender, and Upgrade feature 1.) Maybe if you set the ALLUSERS property to 1 that would take care of it? 2.) Someone correct me if I'm wrong, but it sounds like a major upgrade is what you're talking about. I think that if you change the version string it will do a major upgrade? The major upgrade from my understanding will uninstall the previous version, and install the new version. If you use the same product Guid, I think that's how it finds the previous version, and you don't have to do anything yourself. If you want to package the msi into an exe, on the WiX sourceforge page there's a nice bootstrapper sample project that is akin to msistuff.exe in that, well, it is msistuff.exe with an additional option to package an msi file right into the exe. On 2/21/07, Vidhya Sagar Bhogavalli (Infosys Technologies Ltd) [EMAIL PROTECTED] wrote: Hi All, I've a couple of queries on WIX installers. 1. I've created an installer for Windows Vista. I've disabled the Remove feature from Add/Remove Programs by setting the ARPNOREMOVE property to 1. This has also disabled the Remove option from Windows Defender. Though, When I click on Show All Users in Windows Defender, the Remove is enabled. But I want the Remove option to be disabled even for Sow All Users. Is there any property that I can set to do this or any custom action that would help the cause? 2. I want to check if a previous version of the Product already exists and If it does, I want to uninstall it and then install the current version. Though, I cannot resort to the Upgrade feature because it mandates the use of the ReinstallAll property with the msiexec command. Otherwise, it mandates the change of the Product GUID as a major Upgrade. But I don't want to change the product GUID either. I want to do the uninstall of the previous version and then proceed with the current installation from within the .msi. Also, I don't want to write a wrapper Setup.exe which would in turn call the msiexec command with the ReInstallAll property. Is there a possible way of doing this from the .msi? Please mail me If you have a solution for either of my queries. Thanks In Advance, Sagar - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list. http://tv.yahoo.com/collections/265 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Launch Condition
Your condition looks correct. Check that within your InstallExecuteSequence you have scheduled your 'LaunchConditions' after 'AppSearch': InstallExecuteSequence LaunchConditions After='AppSearch' ... /InstallExecuteSequence Cheers, Dacian - Original Message From: Balakrishna.BK [EMAIL PROTECTED] To: wix-users@lists.sourceforge.net Sent: Wednesday, February 21, 2007 2:24:15 PM Subject: [WiX-users] Launch Condition Hi All, I am a beginner in wix. I have the following launch condition. It is working fine, if the Registry key 'SuiteInstallDir' is NOT found in the path and the condition is NOT SUITEINSTALLDIR, but when I create RegKey and remove NOT condition, it is failing and prompts message as 'Software is not installed' and exits. Any suggestions please. REG Key not found and is working fine : Property Id=SUITEINSTALLDIR RegistrySearch Id='BOBJRegistry' Type='raw' Root='HKLM' Key='Software\MyCompany\Suite 12.0\Shared' Name='SuiteInstallDir' / /Property Condition Message=Software is not installed NOT SUITEINSTALLDIR /Condition REG Key is created but Failing with error message: Property Id=SUITEINSTALLDIR RegistrySearch Id='BOBJRegistry' Type='raw' Root='HKLM' Key='Software\MyCompany\Suite 12.0\Shared' Name='SuiteInstallDir' / /Property Condition Message=Software is not installed SUITEINSTALLDIR /Condition My Goal, is to install the msi if a regkey is found, else exit with message. Thanks, Balakrishna. Heres a new way to find what you're looking for - Yahoo! Answers - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users 8:00? 8:25? 8:40? Find a flick in no time with the Yahoo! Search movie showtime shortcut. http://tools.search.yahoo.com/shortcuts/#news- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] CustomAction
Hi Dhaval, I'm new here and I have not much experience with WiX, but if my understanding is correct, here it goes: ... CustomAction Id=ActionA .../ CustomAction Id=UndoActionA .../ InstallExecuteSequence Custom Action=ActionA After=InstallFiles/ Custom Action=UndoActionA After=ActionAREMOVE=ALL/Custom /InstallExecuteSequence This will makes sure your 'UndoActionA' custom action is executed only during removal. Hope this helps, Dacian - Original Message From: Dhaval Patel [EMAIL PROTECTED] To: wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net Sent: Friday, February 2, 2007 7:30:06 PM Subject: [WiX-users] CustomAction I have been trying to find a post that would sum up how to run a CustomAction (to run a batch file) at the end of an installation, and in the same MSI, another CustomAction that would run the corresponding undo action from another batch file. So the flow would be like: Step 1) Install files Step 2) Run batch file for action A Step 3) Run batch file to undo action A Step 4) Uninstall files I have tried hard to find examples and it seems that running a batch file after install is straightforward, but what about the uninstallation phase? Specifically, what's the Event that I should tie the batch file to so that it runs only during uninstallation? Thanks in advance, folks. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/features_spam.html- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] CustomAction
Hi, I think Dhaval only wants its UndoActionA executed on removal, and not during the installation (otherwise it will immediately undo the effects of ActionA, right?) Recap: ActionA on install (and removal eventually) UndoActionA on uninstall only There is indeed a restriction on REMOVE property, your custom action needs to be scheduled after InstallValidate: http://msdn2.microsoft.com/en-us/library/aa368013.aspx Dacian - Original Message From: Levi Wilson [EMAIL PROTECTED] To: fiordean dacian [EMAIL PROTECTED] Cc: WiX-users@lists.sourceforge.net Sent: Monday, February 5, 2007 3:40:39 PM Subject: Re: [WiX-users] CustomAction If you did it that way I think that ActionA would run both on Install AND Uninstall. To get ActionA to run Only in install, you would condition it like this: Custom Action=ActionA After=InstallFilesNOT Installed/Custom !-- Only run on Install -- Custom Action=UndoActionA After=RemoveFilesInstalled AND NOT REINSTALL/Custom !-- Only run on uninstallation -- Please correct me if I'm wrong. I think that I read somewhere in one of the WiX (or MSI?) newsgroups that you shouldn't use the REMOVE property to condition something for uninstallation. Hope this helps. On 2/5/07, fiordean dacian [EMAIL PROTECTED] wrote: Hi Dhaval, I'm new here and I have not much experience with WiX, but if my understanding is correct, here it goes: ... CustomAction Id=ActionA .../ CustomAction Id=UndoActionA .../ InstallExecuteSequence Custom Action=ActionA After=InstallFiles/ Custom Action=UndoActionA After=ActionAREMOVE=ALL/Custom /InstallExecuteSequence This will makes sure your 'UndoActionA' custom action is executed only during removal. Hope this helps, Dacian - Original Message From: Dhaval Patel [EMAIL PROTECTED] To: wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net Sent: Friday, February 2, 2007 7:30:06 PM Subject: [WiX-users] CustomAction I have been trying to find a post that would sum up how to run a CustomAction (to run a batch file) at the end of an installation, and in the same MSI, another CustomAction that would run the corresponding undo action from another batch file. So the flow would be like: Step 1) Install files Step 2) Run batch file for action A Step 3) Run batch file to undo action A Step 4) Uninstall files I have tried hard to find examples and it seems that running a batch file after install is straightforward, but what about the uninstallation phase? Specifically, what's the Event that I should tie the batch file to so that it runs only during uninstallation? Thanks in advance, folks. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Finding fabulous fares is fun. Let Yahoo! FareChase search your favorite travel sites to find flight and hotel bargains. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Have a burning question? Go to www.Answers.yahoo.com and get answers from real people who know.- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] CustomAction
You're right, I didn't see the 'entire' condition you propose for UndoActionA (I saw only INSTALLED part of it :)) Dacian - Original Message From: Levi Wilson [EMAIL PROTECTED] To: fiordean dacian [EMAIL PROTECTED] Cc: WiX-users@lists.sourceforge.net Sent: Monday, February 5, 2007 4:14:19 PM Subject: Re: [WiX-users] CustomAction The condition: Installed AND NOT REINSTALL Would only execute on an Uninstall. On 2/5/07, fiordean dacian [EMAIL PROTECTED] wrote: Hi, I think Dhaval only wants its UndoActionA executed on removal, and not during the installation (otherwise it will immediately undo the effects of ActionA, right?) Recap: ActionA on install (and removal eventually) UndoActionA on uninstall only There is indeed a restriction on REMOVE property, your custom action needs to be scheduled after InstallValidate: http://msdn2.microsoft.com/en-us/library/aa368013.aspx Dacian - Original Message From: Levi Wilson [EMAIL PROTECTED] To: fiordean dacian [EMAIL PROTECTED] Cc: WiX-users@lists.sourceforge.net Sent: Monday, February 5, 2007 3:40:39 PM Subject: Re: [WiX-users] CustomAction If you did it that way I think that ActionA would run both on Install AND Uninstall. To get ActionA to run Only in install, you would condition it like this: Custom Action=ActionA After=InstallFilesNOT Installed/Custom !-- Only run on Install -- Custom Action=UndoActionA After=RemoveFilesInstalled AND NOT REINSTALL/Custom !-- Only run on uninstallation -- Please correct me if I'm wrong. I think that I read somewhere in one of the WiX (or MSI?) newsgroups that you shouldn't use the REMOVE property to condition something for uninstallation. Hope this helps. On 2/5/07, fiordean dacian [EMAIL PROTECTED] wrote: Hi Dhaval, I'm new here and I have not much experience with WiX, but if my understanding is correct, here it goes: ... CustomAction Id=ActionA .../ CustomAction Id=UndoActionA .../ InstallExecuteSequence Custom Action=ActionA After=InstallFiles/ Custom Action=UndoActionA After=ActionAREMOVE=ALL/Custom /InstallExecuteSequence This will makes sure your 'UndoActionA' custom action is executed only during removal. Hope this helps, Dacian - Original Message From: Dhaval Patel [EMAIL PROTECTED] To: wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net Sent: Friday, February 2, 2007 7:30:06 PM Subject: [WiX-users] CustomAction I have been trying to find a post that would sum up how to run a CustomAction (to run a batch file) at the end of an installation, and in the same MSI, another CustomAction that would run the corresponding undo action from another batch file. So the flow would be like: Step 1) Install files Step 2) Run batch file for action A Step 3) Run batch file to undo action A Step 4) Uninstall files I have tried hard to find examples and it seems that running a batch file after install is straightforward, but what about the uninstallation phase? Specifically, what's the Event that I should tie the batch file to so that it runs only during uninstallation? Thanks in advance, folks. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Finding fabulous fares is fun. Let Yahoo! FareChase search your favorite travel sites to find flight and hotel bargains. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Need a quick answer? Get one in minutes from people who know. Ask your question on Yahoo! Answers . - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net
