I have a WiX bundle for different components of our software.
Every component has its own msi and installs perfectly.
But I want to install the bundle so that for every msi I get an entry in ARP,
but I can only get the bundle to appear.
How can I force the burn chain to show every component?
I have a setup which works great but has one bug.
If only the revision number changes, the setup tells
me that this product version is already installed.
e.g. I have one msi with version 1.2.3.4 installed
and I want to upgrade to 1.2.3.5. This doesn't
work for me. I couldn't find any
Take a look at the MsiPackage/@Visible attribute
http://wix.sourceforge.net/manual-wix3/wix_xsd_msipackage.htm.
Neil
I have a WiX bundle for different components of our software.
Every component has its own msi and installs perfectly.
But I want to install the bundle so that for every msi I
This is a limitation of Windows Installer the only way to get around it is
to allow same version upgrades but this is not without its own problems
primarily that 1.2.3.4 will also downgrade 1.2.3.5
Neil
I have a setup which works great but has one bug.
If only the revision number changes, the
I have it formatted I think, this is a line from the agreement:
Where the Licence has been purchased through a distributor including
[DISTRIBUTORNAME]
Property: Property Id=DISTRIBUTORNAME Secure=yes Value=Company Ltd/
But it is still only showing [DISTRIBUTORNAME] in the agreement on the
On 2012-12-17 09:58, Neil Sleightholm wrote:
Take a look at the MsiPackage/@Visible attribute
http://wix.sourceforge.net/manual-wix3/wix_xsd_msipackage.htm.
This solved my problem. Thank you very much.
I read this page many times and overlooked it every time.
Marc
I'm new to Burn, and was trying my first test dummy setup with GUI
that I found here:
http://bryanpjohnston.com/2012/09/28/custom-wix-managed-bootstrapper-application/
Solution contains three projects: TestBA.csproj,
DummyInstaller.wixproj, and BootstrapperSetup.wixproj. I removed all
the MVVM
You could try setting Vital=no on the File element. I'm not sure if that
applies to removal as well as installation.
-Original Message-
From: Nirmalraj Durai [mailto:nirmal.du...@gmail.com]
Sent: 17 December 2012 06:05
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Network path
Hey all,
Even am in the same boat. How to create a uninstall shortcut in startmenu-
program files to uninstall application installed with WiX bootstrapper. I am
not getting the product code of bootstrapper, which I would have used for
un-installation. looking for same un-install shortcut which is
Hi all,
I'm putting together an installer to help users get Mercurial running on
IIS and I'm using burn for it.
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Bundle Name=HgOnIISAssistant Version=1.0.0.0
Manufacturer=HgOnIISAssistant
I thought MSI only looked at first three digits, ie change 1.2.3.4 to
1.2.4.4 to affect changes.
tenholde
-Original Message-
From: Marc Fauser [mailto:marc.fau...@gmail.com]
Sent: Monday, December 17, 2012 2:54 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Wix Upgrades
Hi,
MSI is able to store version number information upto four places. In
upgrade process it consider version number upto three places only.
fourth part will be ignored by its upgrade machinery.
Please check /Note that Windows Installer uses only the first three
fields of the product version/
Hello,
I have created a MSI with WiX (version 3.5.2519.0), this MSI put a CTG.ini
to specific folders:
C:\Program Files (x86)\IBM\CICS Universal Client
C:\Program Files (x86)\IBM\IBM CICS Universal Client
The same MSI is executed on 2 computer but:
The first computer have this file in the
Several people from the WiX community lent a hand getting the update to the
WiX book into shape. The end result covers more ground than the last
version, including, of course, Burn. All in all, I'm very pleased with the
end result! It's available for the Kindle on Amazon's site at:
What he means is that you have to check the documentation to see if it accepts
formatted text. If it doesn't it will display the text as is.
-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: December-17-12 5:26 AM
To: 'General discussion for Windows
Oh silly me, I found it, unfortunately it does not support embedded
properties..thanks
Kind Regards,
Natalie Carr
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: Monday, December 17, 2012 2:33 PM
To: General discussion for Windows Installer XML toolset.
Hi does anyone have a full example of extracting a file from the binary
table and executing it in C++? I cannot seem get it working at all.
Kind Regards,
Natalie Carr
--
LogMeIn Rescue: Anywhere, Anytime Remote
I am *not* able to get msiexec.exe to set the recovery option of my Windows
service to Restart the Service.
Wix 3.6 documentation suggests that I can use ServiceConfigFailureActions to
accomplish this.
Here is my ServiceInstall element:
ServiceInstall Id=ServiceInstallID
Does it work if, instead of using the ServiceConfigFailureActions and Failure
elements, you use the util:ServiceConfig element? It has
FirstFailureActionType, SecondFailureActionType and ThirdFailureActionType
attributes that you can set to restart, runcommand or reboot.
--
View this message in
Error 5 is access denied. Are you running the installation as administrator ?
-Original Message-
From: Marty Offe [mailto:marty.o...@harlandfs.com]
Sent: 17 December 2012 16:44
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How do to configure a Windows service to Restart the
--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover
To add to what Nick said, here's what I have. It works in WiX 3.5:
ServiceInstall Id=InstallMyService ...
util:ServiceConfig ServiceName=MyService
FirstFailureActionType=restart SecondFailureActionType=restart
ThirdFailureActionType=restart ResetPeriodInDays=1
RestartServiceDelayInSeconds=60 /
Could you attach the part of the log into the email message? Attachments
don't show up in the forum for me. It could be a couple of things really.
Might help to post some of your WiX markup too.
--
View this message in context:
I don't see your MSI in the bundle's chain. Only the python and .NET ones. Is
this the code you wanted to show to the forum?
I've gotten that error message once before. It went away after I recompiled
through.
--
View this message in context:
In your Bundle.wxs, if you have:
BootstrapperApplicationRef Id=ManagedBootstrapperApplicationHost
...
/BootstrapperApplicationRef
then you also need, after the BootstrapperApplicationRef:
WixVariable Id=WixMbaPrereqLicenseUrl Value=... /
WixVariable Id=WixMbaPrereqPackageId Value=... /
Finally got the bottom of it...
In my MSI I have something like this:
Feature Id=DefaultFeature Level=0
Condition Level=1TYPE=1/Condition
ComponentGroupRef Id=Test /
/Feature
The value of TYPE is set by burn and passed in to the MSI. On upgrade I assumed
that this value
Ahh, yes. Feature Conditions must be used very carefully. If they evaluate
to false during uninstall after evaluating to true on install or repair,
you can get really unexpected behaviors like this.
On Mon, Dec 17, 2012 at 10:15 AM, Neil Sleightholm n...@x2systems.comwrote:
Finally got the
Hi,
To the WiX developers:
I was running Process Explorer (sysinternals) and I saw that the
Description and Company Name columns only contains one character (the
first one set in @Bundle/Name and @Bundle/Manufacturer).
On all the processes running on my computer, only the bootstrapper
(created
I found why:
when wix updates the bootstraper resource versioninfo, for strings, the
wType is not set correctly, wType is 0 instead of 1.
see
http://msdn.microsoft.com/en-us/library/windows/desktop/ms646987(v=vs.85).aspx
Modifying with an hexadecimal editor the wType from 0 to 1 makes the string
We are having issues propagating the environment variables. The setup has a
custom action that propagates the environment using the SendMessageTimeOut api
SendMessageTimeout(HWND_BROADCAST, WM_SETTINGCHANGE, 0,(LPARAM)
Environment, SMTO_ABORTIFHUNG, 5000, NULL);
On a 64 bit OS, both 32
I thought MSI did the send message thing itself and that console windows
are never affected by it.
On Mon, Dec 17, 2012 at 4:31 PM, Mita Patel mpa...@esri.com wrote:
We are having issues propagating the environment variables. The setup has
a custom action that propagates the environment using
problem comes from:
wix37-sources\src\DTF\Libraries\Resources\VersionStringTable.cs (line 81)
where verValue.Data is set, and in VersionInfo.cs (line 83): this.isString
= false;
so we lose the info that verValue is a string.
Could it be fixed before final release of WiX 3.7?
to reproduce while
On 17-Dec-12 11:43, Marty Offe wrote:
I am *not* able to get msiexec.exe to set the recovery option of my Windows
service to Restart the Service.
Two things:
1. Your authoring doesn't match your MSI tables doesn't match your MSI log.
2. There's no indication in the doc that
On 17-Dec-12 19:57, up2date cyborg wrote:
Maybe I should not post this on the wix-user list?!
Please file a bug so it doesn't get lost.
--
sig://boB
http://joyofsetup.com/
--
LogMeIn Rescue: Anywhere, Anytime Remote
Here find the content of files:
MSI_NOT_OK.log ==
=== Verbose logging started: 5/12/2012 16:06:02 Build type: SHIP UNICODE
5.00.7600.00 Calling process: C:\WINDOWS\system32\msiexec.exe ===
Font created. Charset: Req=0, Ret=0, Font:
That is how environment variables work, the variables are only read when the
environment is started. IIRC you can write applications that monitor for
WM_SETTINGCHANGE and update themselves but the standard consoles don't.
Neil
-Original Message-
From: Mita Patel
36 matches
Mail list logo
