Sorry for the delay, in your MBA, what is the value of e.Status from
private void ApplyComplete(object sender, ApplyCompleteEventArgs e)
From: Nick Miller [nmil...@livetechnology.com]
Sent: Wednesday, May 15, 2013 10:49 AM
To: General discussion for
Another possible option, RegisterApplicationRestart -
http://msdn.microsoft.com/en-us/library/windows/desktop/aa373347(v=vs.85).aspx
for Vista or newer (which is where the run once keys were disabled for standard
users).
From: Rob Mensching
SuppressSignatureVerification=yes
Fab. That did the trick. many thanks, Rob :)
On Wed, May 29, 2013 at 6:32 PM, Rob Mensching r...@robmensching.com wrote:
Sounds like that MSI has it's digital signature messed up. Microsoft made
that mistake a few times. You can work around the issue by
This is what I do, it doesn't do the download as I prefer to embed the
file but that shouldn't be too hard to add:
Fragment
util:RegistrySearch
Id=Java7FamilyVersion
Root=HKLM Key=SOFTWARE\JavaSoft\Java Runtime Environment
Value=Java7FamilyVersion
Variable=Java7FamilyVersion
We're looking at simply making WiX part of the toolkit you need to build
our solutions. We've tried this with some smaller projects and it's worked
really well. Developers can follow up on their own impacts, and they can
tell when they've broken the install. This increases build quality and
frees
Well Bob is correct those switches are documented. I am not sure now what
document I was looking at yesterday which seemed to be missing this
information. I have 3.7.1224 installed on several systems as I experiment
and learn the details and I thought I had checked the CHM carefully prior to
Hi,
I have one MSI, with a bunch of compressed files in an embedded cab, and
one readme next to the install as an uncompressed file. This file is still
in the installer, it's just got the nonCompressed bit set. This is so we
can update the readme right up until release with late-breaking
Thanks for the reply,
Here is the result when I break the CA:
APPLY COMPLETE, e.STATUS: -2147023293
APPLY COMPLETE, e.STATUS: -2147023293
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Thursday, May 30, 2013 2:41 AM
To: General discussion for Windows
I've recently added WiX to my continuous integration server, Team City. They
key is to not have to install stuff on the build machines. WiX includes the
install binaries that can be put right in your source tree. However the
binaries do not include the files necessary for Custom Actions (CAs),
How do I hide the directory selection dialog during any upgrade. I have tried
using a lot of different approaches and it shows every time. Below is the
relevant code for the ui that does not work.
Publish Dialog=LicenseAgreementDlg Control=Next
Event=NewDialog
@Mark:
Yep, that's what we've gone with, but we had issues getting the right set
of properties to set up the paths properly because there's a number of
cascading properties. Also, we had issues in that we have to do this with
every .wixproj. (I guess we might create a customized .wixproj which
I was talking specifically in your MBA, on the ApplyComplete handler. I was in
the 3.8 codebase, but Wix doesn't check for e.Error but rather e.Status.
-Original Message-
From: Nick Miller [mailto:nmil...@livetechnology.com]
Sent: Thursday, May 30, 2013 8:54 AM
To: General discussion
Hi,
While I was looking at refactoring our wxs code, I noticed something odd.
I have a structure like this
File\File.wixproj
File.wxs
Install\Install.wixproj
Product.wxs
CustomAction1.wxs
CustomAction2.wxs
InstallExecuteSequence.wxs
(Note
That is from the ApplyComplete handler in my MBA...
public void OnApplyComplete(object sender, ApplyCompleteEventArgs e)
{
Bootstrapper.Engine.Log(LogLevel.Standard, APPLY COMPLETE,
e.STATUS: + e.Status);
...
}
-Original Message-
From:
Ahh, then that is your answer. E.Status != 0 means apply failed.
From the Wix BA,
private void ApplyComplete(object sender, ApplyCompleteEventArgs e)
{
WixBA.Model.Result = e.Status; // remember the final result of the
apply.
...
// Set the state to
Hi,
I was trying to create the Site and App-pool. The site folder getting
created on [INSTALLLOCATION] Whcih was passed through command line and
webapp is getting installed. But When I go and look in inetmgr site getting
created on Default Website and not as separate site and WebApp-pool getting
Awesome, thanks!
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Thursday, May 30, 2013 12:48 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] CA Error with MBA
Ahh, then that is your answer. E.Status != 0 means
Actually, to be accurate it's not a = 0 but rather:
internal class Hresult
{
/// summary
/// Determines if an HRESULT was a success code or not.
/// /summary
/// param name=statusHRESULT to verify./param
/// returnsTrue if the status is a success
Cool, I think we'll go with this approach. Comparing what's in my registry with
what seems to be going on below and since I have no experience with registry
searches or ExePackages, I have some questions:
1) The Java version seems to be the value HKLM\SOFTWARE\JavaSoft\Java Runtime
A perfect, I understand now, thanks.
And I assume [WixBundleLog_Java7Runtime] is the location you want the Java
installer log to output.
Alain
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: May 30, 2013 13:43
To: afor...@cmu.edu; 'General discussion
1.7.0_21 is not a normal version number that WiX can compare so that is why I
need the two stage search, the first one gets the registry key and then once
you have that you can search for the proper version number in the MSI sub key.
Specifying v7.0.210 in the comparison makes WiX treat what
Well, for your website to be created, it needs to be in a component:
Fragment
?include ConfigurationInitialize.wxi ?
iis:WebSite Id=CoreWebservicesV3 Description='CoreWebservicesV3'
Since your iis:WebSite element is outside of a component, it serves only as a
locator and the site is not
Have a look at the vital setting for the file. You may find it's not vital
in the Info message case.
MSI File table:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa368596(v=vs.85).as
px
If the file is external and you are replscing it at the last moment make
sure you don't make a
Hi Steve! Excuse me where did you exactly put the solution? in the
Product.wxs or where?
Thanks!
Alfredo
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/variables-not-working-tp7580709p7586225.html
Sent from the wix-users mailing list archive at
Classification: Public
Yes in the Product.wxs file
-Original Message-
From: Pelusin [mailto:thisispowerfulmagik_magikmu...@hotmail.com]
Sent: May-30-13 3:03 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] variables not working...
Hi Steve! Excuse me where did you exactly
I can't figure out why Candle doesn't seem to find the RegistrySearch element
in the util namespace, as it throws this error:
Fragment element contains an unhandled extension element 'util:RegistrySearch'.
Please ensure that the extension for elements in the 'http://schemas.microsoft.
Do you have the Util extension added as a reference to your Burn project?
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From:
Thanks Phil, I'll take a look when I get a chance. I have a feeling it's
still in the hash table.
Thanks again.
On 30 May 2013 19:28, Phil Wilson phil.wil...@mvps.org wrote:
Have a look at the vital setting for the file. You may find it's not
vital
in the Info message case.
MSI File
Hm, I've just been using Candle and Light thus far. Since I'm now including an
EXE in my MSI, I take it I now need to use Burn? If so, is there a Burn
tutorial somewhere? I've been unable to find one.
Alain
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: May
I've just found this:
http://wix.sourceforge.net/manual-wix3/authoring_bundle_intro.htm
I'll read through it and hopefully it'll answer my questions (assuming I need
Burn, which I'm guessing I now do).
Alain
-Original Message-
From: Alain Forget [mailto:afor...@cmu.edu]
Sent: May 30,
Not if you are embedding exe in msi. The other way around maybe.
-Original Message-
From: Alain Forget [mailto:afor...@cmu.edu]
Sent: May-30-13 4:55 PM
To: 'John Cooper'; 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Including UtilExtension a Fragment
Now I'm really confused. :-)
So to explain a bit more, the EXE is the Java Runtime Environment installer,
and the MSI is my installer.
So I want to include the EXE in my MSI, and (silently) run the JRE EXE if it
isn't already installed (determined by util:RegistrySearch elements), before
the
I think probably using burn to chain both the JRE installer and the MSI is
the best idea.
I'm pretty sure the JRE installer is just a bootstrapped MSI, so including
it in your MSI won't work (the nested MSI transaction issue).
On 30 May 2013 21:06, Alain Forget afor...@cmu.edu wrote:
Now I'm
Classification: Public
Why don't you create a bundle and have the JRE installed first then your MSI?
-Original Message-
From: Alain Forget [mailto:afor...@cmu.edu]
Sent: May-30-13 4:07 PM
To: 'Wesley Manning'; 'General discussion for Windows Installer XML toolset.';
'John Cooper'
Burn is for the bootstrapper only (creates bootstrapper exe) but I think you
knew that? If you are using MSI only then I think you can embed exe in the MSI
like any other file. Never did that to run install so others would have to
comment on how to get it to run.
Wes
-Original
Nested or concurrent installs are deprecated/unsupported. If you need to chain
multiple installers, use burn.
-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca]
Sent: Thursday, May 30, 2013 3:21 PM
To: afor...@cmu.edu; 'General discussion for Windows Installer XML
I think creating a bundle is what I need to do. I've just never used Burn
before, so I'm just learning now how it works. If I understand correctly, I
Candle and Light my own installer into an MSI as usual, but then use Burn to
package the MSI and JRE EXE together? And there will be some way to
This might help you get started
http://neilsleightholm.blogspot.co.uk/2012/05/wix-burn-tipstricks.html
Neil
-Original Message-
From: Alain Forget [mailto:afor...@cmu.edu]
Sent: 30 May 2013 21:26
To: 'Steven Ogilvie'; 'General discussion for Windows Installer XML toolset.';
'Wesley
There's a book (only one I know) that you can buy here:
http://www.packtpub.com/windows-installer-xml-3-6-developers-guide/book. Might
want to get that to get up to speed quick. It was updated for burn.
Yes use burn to group them together in one installer exe. This exe can contain
your
Hi John,
I was able to create the site after including the Website in the component
as below.But Site is not getting created as intended.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7586241/Capture.png
*ComponentGroup Id=MyWebIssConfiguration
ComponentRef
Sorry error. I meant: (i.e. last one in chain is first one to get
uninstalled).
The order they appear in chain is order get installed and reverse order for
uninstall (i.e. last one in chain is first one to get installed).
Chain
PackageGroupRef Id=package a/
PackageGroupRef
Hi Steve, i'm beginning with WIX and i don't have any experience, si i hope
you could help with some doubts i have:
i have some files one is called ConfigurationInitialize.wxi and it contains
this
?xml version=1.0 encoding=utf-8?
Include
!-- +++ VIRTUAL_DIR_VAL
It's time for me to step on the Burn noob school bus. :-)
So I have the following file named MyBundle.wxs:
?xml version='1.0' encoding='windows-1252'?
Wix xmlns='http://schemas.microsoft.com/wix/2006/wi'
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;
Bundle UpgradeCode=MY-GUID
If you have Visual Studio, the Votive/integration that Wix provides hides most
of this for you and it just works. You don't use burn to build the bundle, use
candle/light to build it.
From a rough point of view, the burn exe is the starting point for your bundle
and some magic happens to cab
Unfortunately, I'm not using Visual Studio, so I don't think that's an option.
So what I'm currently trying to do is use candle/light to make
MyMSIProductPackage.msi (which works great on its own), and then use burn.exe
to package it up with the Java Runtime Environment 7 exe installer, to make
You use candle and light to compile the burn bundle as well.
Sent from my iPhone
On May 30, 2013, at 5:26 PM, Alain Forget afor...@cmu.edu wrote:
Unfortunately, I'm not using Visual Studio, so I don't think that's an option.
So what I'm currently trying to do is use candle/light to make
More simply: it's just a .wxs file. You compile and link the .wxs file like
you do any other .wxs files. The burn.exe is in a strange place because
it's just an implementation detail. Building your Bundle is just like
building your MSI or your MSP or your MSM...
On Thu, May 30, 2013 at 4:00 PM,
Classification: Public
Place the custom action elements in your product.wxs file with the
installexecutesequence and installuisequence
You also need to include your ConfigurationInitialize.wxi in your product.wxs
Via:
?include the path to this file\ ConfigurationInitialize.wxi ?
-Original
48 matches
Mail list logo
