Ok.
It would be cool if you could use a Burn-Package like a Msi-Package and it
would know, if it is allowed to perform an upgrade. I have tested yet, that the
WiXStBA stops with an error, if one tries to install an older bundle over a
newer yet installed one. So I was hoping that you can
It might be appropriate to use MSIPackage/@Permanent and a condition of
ConfigRequiresIt and not ProductDetected (set with a product search). If the
package was present before the bundle was installed, there's some third party
thing using it and you don't know when it's safe to remove (if ever).
That sounds like a good solution. Are you saying that setting Permanent
stops the InstallCondition ever uninstalling it?
Neil
It might be appropriate to use MSIPackage/@Permanent and a condition of
ConfigRequiresIt and not ProductDetected (set with a product search). If
the
package was present
We install the java runtime (version 6) by extracting the msi and cab. We've
never had any trouble doing it this way through several Java updates (and a
change of bootstrapper).
MsiPackage DisplayName=Java(tm) 6 Update 24
Description=Java virtual machine
I'll admit I haven't tried it but it wouldn't be very permanent if it did :)
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 01 October 2012 10:15
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Conditional MsiPackage
That
You'll have a variable for the path
Variable Name=InstallFolder
Value=[ProgramFilesFolder]companyname\productname Persisted=yes
bal:Overridable=yes Type=string /
Which you pass to your MSI using MSIProperty. Assuming you use INSTALLDIR as
your directory Id in your MSI, as is commonly
The other thing you will have to do is to save the path in your MSI (e.g.
In the registry) and then retrieve it in your bundle so that on an upgrade
the previous path is restored e.g.:
Variable Name=InstallFolder Type=string
Value=[ProgramFilesFolder]company\app Persisted=yes
bal:Overridable=yes
I have a simple burn package that install SQL express and one MSI. The install
works the first time I run it but when I upgrade it the SQL package is removed
(if I upgrade again it is put back). It appears from the logs that it doesn't
recognise that the package is referenced and so the upgrade
Thanks for your advises.
There are two problems with WixBundleInstalled:
1) I have to distinguish 3 states: version is same, current version is lower
than installed version, current version is higher than installed version. But
WixBundleInstalled only has value 0 or 1.
2) Which is even worse: I
___
Douglas Thomas
Sr. Sftw. Developer
RedPrairie
308 N. Cleveland-Massillon Rd.
Akron, OH 44333-9302
Office: (330) 665-1698
Fax: (330) 665-2915
www.RedPrairie.comhttp://www.redprairie.com/
doug.tho...@redprairie.com
Email
More info: Running v1 installs SQL, v2 removes it, v3,4,5 etc installs SQL
then immediately removes it!
In the log file created for the upgrade there is this entry
[1664:16B4][2012-10-01T13:30:31]: Skipping dependency registration on
package with no dependency providers: SQLServerExpress.
Neil
I have the same code in the DetectMsiFeature and, both get called in the
initial installation. However, when I run the bootstrap executable again
(or run Change in ARP) I do not get any calls to PlanMsiFeature, which is
where I modify the feature states based upon user input.
--
View this
Hello,
We upgraded from WiX3.5.2519 to 3.6.3303.1, and it seems like wixlibs are not
working as expected anymore in our projects.
The library project builds, but when a merge module attempts to build(which has
the wixlib project as a reference), I get the following error:
The end element
Is the wixlib xml valid ? There might be a malformed element somewhere
inside.
-Original Message-
From: Stelios Kyprou [mailto:stelios.kyp...@fcg.im]
Sent: 01 October 2012 15:47
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] WixLibs do not seem to work
I don't think so..but just to be sure, I changed all the values to a single
string char. So for example, one string definition would end up being:
String Id=ValidateSharepointUrl![CDATA[a]]/String
So there are a bunch of these String definitions between
?xml version=1.0 encoding=utf-8?wixLibrary
Hi,
I have created a managed bootstrapper using burn which installs one to three
MSIs. One of the packages might require a restart of the system.
What I now do is this:
private void ApplyComplete(object sender, ApplyCompleteEventArgs e)
{
// ..
We have 3.6 wixlibs building with no problems and I can't see any relevant
bugs in the bugs database. Wix 3.6 was mostly Burn rather than core toolset
changes.
I wasn't thinking of the strings being bad, so much as the xml elements
themselves. The error message makes it sound like badly formed
Uh - yep. Right there in the Bal schema doc. My mad Google skillz were,
apparently, taking the weekend off or something,
Thanks!
- keywords for crawlers, for future archive searchers
Burn Wix Wxs
Suppress Options Button
Remove Options Button
Bal Schema
Ok I found the problem!
You know how when you create a wixlib project, you have a default Library.wxs
file?
In 3.6 by having this as follows worked:
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
/Wix
With 3.6, this won't work...you NEED to have the fragment
First paragraph I meant to say 3.5
-Original Message-
From: Stelios Kyprou [mailto:stelios.kyp...@fcg.im]
Sent: 01 October 2012 17:12
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WixLibs do not seem to work after 3.6 upgrade.
Ok I found the
Sigh... Am I daft, or I just don't understand...
I have multiple packages I need to install as pre reqs of the main
install... Do these make sense?
.Net 4.0:
ExePackage Id=DotNetFx40
DisplayName=Microsoft .NET Framework 4
Sure.
Plan section of new bundle -
[1910:00E8][2012-09-17T09:54:25]: Plan 15 packages, action: Install
[1910:00E8][2012-09-17T09:54:25]: Skipping dependency registration on
package with no dependency providers: VC8X86
[1910:00E8][2012-09-17T09:54:25]: Setting string variable
Sure.
Plan section of new bundle -
[1910:00E8][2012-09-17T09:54:25]: Plan 15 packages, action: Install
[1910:00E8][2012-09-17T09:54:25]: Skipping dependency registration on
package with no dependency providers: VC8X86
[1910:00E8][2012-09-17T09:54:25]: Setting string variable
You can also return IDRESTART from OnShutdown().
On Mon, Oct 1, 2012 at 8:44 AM, Henning Krause m...@henningkrause.euwrote:
Hi,
I have created a managed bootstrapper using burn which installs one to
three MSIs. One of the packages might require a restart of the system.
What I now do is
These are the results even though I don't have 90% of the pre reqs:
Detect 8 packages
Detected partially cached package: MainInstall, invalid payload:
MainInstall, reason: 0x80070570
Detected package: DotNetFx40, state: Absent, cached: None
Detected package: A_Synchronizationx86, state: Absent,
Permanent tells the engine to not uninstall Packages. I agree with Peter.
smile/
On Mon, Oct 1, 2012 at 2:21 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote:
I'll admit I haven't tried it but it wouldn't be very permanent if it did
:)
-Original Message-
From: Neil Sleightholm
The WiX toolset automatically creates a dependency provider for packages
that it can (MsiPackage and in WiX v3.7, MspPackage). Since ExePackages are
opaque, you'd need to add your own dependency provider (Provides element
from WixDependencyExtension) to get the engine to do reference counting.
On
One of my family of install packages uses Windows Installer 4 to get access to
the restart manager. Unfortunately this has the consequences that its MSIs
cannot be validated at creation time on a vanilla Windows Server 2003 machine.
What are the potential risks of using -sval to turn off
Is there any documentation or a sample for this? The topic How to: Author
product dependencies is blank!
Neil
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 01 October 2012 18:43
To: General discussion for Windows Installer XML toolset.
Subject: Re:
Update (sorry for the fast turnaround, but I forgot to do this ...) I just read
in the book by Nick Ramirez that -sval is the same as turning off all ICE
stuff. This was *not* clear from the supplied documentation, at least in Wix
3.5 ... (i.e., validation does not sound necessarily the same as
There is one here
http://bryanpjohnston.wordpress.com/2012/09/28/custom-wix-managed-bootstrapper-application/comment-page-1/#comment-7
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Examples-of-Burn-tp7578587p7580985.html
Sent from the wix-users
After a little trial and error I came up with this:
dep:Provides Key=SQLServer2008R2ExpressSP1 Version=10.50.2500.0 /
Where dep is defined as:
xmlns:dep=http://schemas.microsoft.com/wix/DependencyExtension;
dep:Provides / is placed as a child of the ExePackage.
What this does is
I just grabbed Wix 3.6 so I could use Wix in 2012 and the installer's UI
was very pretty. Was that somehow written in WiX itself?
Adam
--
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy
Very pretty, but very inaccessible with screen readers.
-Original Message-
From: Adam Tegen [mailto:adam.te...@gmail.com]
Sent: Monday, October 01, 2012 8:04 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Was the fancy Wix 3.6 installer made in WIX
I just grabbed Wix 3.6
I don't get it; aren't WiX projects written purely in XML?
-Original Message-
From: vchauras [mailto:vivekchauras...@gmail.com]
Sent: Monday, October 01, 2012 2:56 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Examples of Burn
There is one here
On 01-Oct-12 12:12, Stelios Kyprou wrote:
In 3.6 by having this as follows worked:
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
/Wix
I'm surprised that worked in either version: The schema definitely
implies something's required. But please file a bug.
On 28-Sep-12 14:53, Janzen Brewer wrote:
Did I lose something in the build processes of these DTF libraries that would
compile those error.txt files? Or is using resgen.exe in a pre-build script
expected?
The .resources version of those files are also checked in. Apparently it
wasn't a high
On 01-Oct-12 10:33, Brian_Covington wrote:
I have the same code in the DetectMsiFeature and, both get called in the
initial installation. However, when I run the bootstrap executable again
(or run Change in ARP) I do not get any calls to PlanMsiFeature, which is
where I modify the feature
On 01-Oct-12 20:04, Adam Tegen wrote:
I just grabbed Wix 3.6 so I could use Wix in 2012 and the installer's UI
was very pretty. Was that somehow written in WiX itself?
It's a bundle with a custom bootstrapper application built in WPF.
--
sig://boB
http://joyofsetup.com/
On 25-Sep-12 09:55, Parker, Steven wrote:
Just to update I have found that the problem seems to stem from the torch
call and if I use the wixmst file generated by 3.5 it creates the patch fine.
Can you post the .wixmsts in a bug?
--
sig://boB
http://joyofsetup.com/
On 30-Sep-12 14:48, Rob Mensching wrote:
When your BA can't handle it.
Or when a suddenly-dropped internet connection is rare...
--
sig://boB
http://joyofsetup.com/
--
Don't let slow site performance ruin your
Burn based codes have a bootstrapper C# code too.
On Mon, Oct 1, 2012 at 8:11 PM, Katherine Moss [via Windows Installer XML
(WiX) toolset] ml-node+s687559n7580990...@n2.nabble.com wrote:
I don't get it; aren't WiX projects written purely in XML?
-Original Message-
From: vchauras
Hi,
I've got a simple bundle setup with one msi:
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:bal=http://schemas.microsoft.com/wix/BalExtension;
Bundle Name=My Setup Version=1.0.0.0 Manufacturer=My Company
UpgradeCode=SOME_GUID
..
Chain
43 matches
Mail list logo
