The references you would see about Wix would only be scheduled to run if your
installer is ran with a UI, which by default you won't want to do with burn.
Assuming you are using WixStdBA, take a look at
Variable Name=LaunchTarget
Value=[ProgramFilesFolder]\Path\To\Your\Program.exe/
This
If I had to guess, it would happen on your machine as well if you renamed the
image after compiling. I don't think you want an absolute path, but rather a
relative one. Then use a Payload element under the BootstrapperApplicationRef
and have Burn compress the image into the bundle.
Hey,
Yes, I'm using the WixStdBA it seems (I'm assumign
bal:WixStandardBootstrapperApplication is just that).
Sorry for my denseness — where would I put the Variable element?
Inside the BootstrapperApplicationRef ?
Thanks so much!
marc.
2012/9/26 Hoover, Jacob jacob.hoo...@greenheck.com:
The
It looks like it might be a fairly simple extension to the OSInfo part
of WixUtilExtension/wixca. I will see if I can put something together for this.
Pete
From: peterhul...@hotmail.com
To: wix-users@lists.sourceforge.net
Date: Tue, 25 Sep 2012
awesome!
yes, the problems were a twofold:
1. i was using absolute paths to an image element. I just changed the
Image back to logo.bmp
2. I wasn't including the logo.bmp file in my final setup package. I added:
Payload SourceFile=logo.bmp/
to BootstrapperApplicationRef as per Jacob's
How do you get a hold of that information within the bootstrapper? Most of the
EventArgs given in the BootstrapperApplication class events only contain
PackageId, and I've looked through the BootstrapperApplication, Command and
Engine classes without finding any way to get from package ID to
answer my own question: put it under the Bundle element. Works
perfectly. Thanks!
2012/9/26 Marc Wandschneider marc...@chipmunkninja.com:
Hey,
Yes, I'm using the WixStdBA it seems (I'm assumign
bal:WixStandardBootstrapperApplication is just that).
Sorry for my denseness — where would I
Hey,
The info is available in BootstrapperApplicationData.xml. I don't know if
there's an easier way, but if all else fails :)
//Caisa
--
View this message in context:
If you need to make sweeping changes that can't be fixed easily, its best to
do a major upgrade and make that your new baseline.
-Original Message-
From: Justin Hull [mailto:justin.h...@assetpoint.com]
Sent: 25 September 2012 20:20
To: General discussion for Windows Installer XML
Thank you Peter,
I should be able to make it work using your information! That's what I was
looking for.
Dirk
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat
A couple of corrections. I must have been half asleep yesterday:
I missed out
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall
is the key for per-user installations for the current user.
for 64-bit MSIs or 32-bit MSIs on 32-bit OS. Should be, of course, for
64-bit MSIs on 64
Problem is that Silverlight by license is not distributable... So we
want to check to see if it is installed and if not put up a message
saying it is required before installation. I have not found a way in the
Bootstrapper to get this to work.
Thanks,
Bob Morrison
robert.morri...@ge.com
Phone:
I'd be very interested in testing it.
Wes
-Original Message-
From: Peter Hull [mailto:peterhul...@hotmail.com]
Sent: September-26-12 4:18 AM
To: WiX Users
Subject: Re: [WiX-users] Installing Device Metadata Package
It looks like it might be a fairly simple extension to the OSInfo part
Thanks for the info. Always wondering what exactly that does.
Wes
-Original Message-
From: Nick Ramirez [mailto:nickra...@hotmail.com]
Sent: September-21-12 10:28 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] What is a rollback boundary?
Reading through the source
To just display a message try adding a bal:Condition e.g.
bal:Condition Message=Silverlight not installedsilverlight test
here/bal:Condition
Neil
Problem is that Silverlight by license is not distributable... So we
want to check to see if it is installed and if not put up a message
saying it
That is what I have been trying but have not had any luck getting it to
work. It seems to me that the Bal:Condition only seems to work on Built
in Variables Does anyone have an example where it works with a
Registry Search defined variable...
Thanks,
Bob Morrison
robert.morri...@ge.com
This is for detecting net 3.5 in windows server 2008 R2.
!-- Just detect .net3.5 sp1 as it is installed by default on windows server
2008 r2 and we can warn if they have removed it.--
util:RegistrySearch Id=netfx35
Variable=NETFX35SP
Root=HKLM
Just to clarify this is not Bundle/@Condition it is a condition inside
your Bundle element.
Neil
This is for detecting net 3.5 in windows server 2008 R2.
!-- Just detect .net3.5 sp1 as it is installed by default on windows
server
2008 r2 and we can warn if they have removed it.--
That's the correct way.
On Wed, Sep 26, 2012 at 1:59 AM, Miss Parker caisa.westl...@gmail.comwrote:
Hey,
The info is available in BootstrapperApplicationData.xml. I don't know if
there's an easier way, but if all else fails :)
//Caisa
--
View this message in context:
This is what I tried, and even if Silverlight is installed it is not
working, it keeps telling me that Silverlight needs to be installed.
?xml version=1.0 encoding=utf-8?
?ifndef Version?
?define Version = 1.0.0.0 ?
?endif ?
Wix RequiredVersion=3.6.2830.0
I have an installer that is using the minimal ui and all I lack is putting in a
database setup dialog that takes in the sql user, password, and server name.
NO. 1 Can I add a custom dialog to the minimal ui to do this? Is it possible
to extend this way?
NO. 2 How do I set the properties for
Fixed it. There were 2 issues, the File/@Source should be File/@Name as
Peter's suggested but also ComponentGroup/@Source needs a trailing \ on
the path e.g.:
Source=$(var.SolutionDir)output\
Having a trailing slash doesn't match directory use anywhere else so I
think this is probably a bug.
Uhh, would it not be:
util:RegistrySearch Id=SILVERLIGHTVERSION
Variable=SILVERLIGHTVERSION
Root=HKCR
Key=AgControl.AgControl\ CurVer
Result=value/
Though looking at
Thanks that did it.
Bob Morrison
robert.morri...@ge.com
Phone: (508) 698-7816
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Wednesday, September 26, 2012 10:52
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn to
Add a condition of '1' to each Publish directive, and see if that helps. The
WiX help links to the MSDN pages for Windows Installer for a reason. From
the ControlEvent Table you will find the following statement:
Condition
A conditional statement that determines whether the installer activates
Hi bill,
Thank you so much for your reply, I found that out late yesterday evening
and forgot to update..:) Thanks
-Original Message-
From: bpackard [mailto:bill.pack...@kepware.com]
Sent: 26 September 2012 16:16
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Problems
I have two installers that share 4 services... each service creates its
service and uninstalls its service:
InstallExecuteSequence
Custom Action=SetStartESService After=CostInitializeNOT
Installed/Custom
Custom Action=StartESService Before=StartServicesNOT
Installed/Custom
I believe this is where you would use a Wixlib (or merge module), so that the
service configs lived inside the same component Ids in both installers. In
theory then the refrencing counting on the shared component ID's should not
trigger the service to be uninstalled.
-Original Message-
logged as #3097 Wix install kicked off from BootStrapper doesn't show
progress bar progress..
Steve
attached both the bootstrapper log and the main install log
--
View this message in context:
The 4 services are each a separate merge module, with common files between
them in two wixlibs
The services creation/removal of services is code within the merge
modules...
(a side issue, a majority of the files do not get uninstalled either :(
Steve
--
View this message in context:
Can you show the component containing the Service executable, along with the
ServiceInstall element (and their relation)? Are they in the same component?
When you said the creating and removing of the services in code, do you mean
that you are using a custom action to do this instead of the
I was able to specify a component with an empty guid
Component Id=SilverlightXap Guid=
The installer compiled, linked, ran. The reason I found this problem was that
when I went to uninstall the product it left the silverlight xap file the
component was needing to uninstall.
Thanks!!!
Allan
From the docs,
Component identifier; this is the primary key for identifying components. If
omitted, the compiler defaults the identifier to the identifier of the resource
that is the explicit keypath of the component (for example, a child File
element with KeyPath attribute with value 'yes'.
The other option would be to have the application invoke an out of process COM
server which runs with elevated privileges. This would allow the installer to
not care, and for the application to run as least privileges and only escalate
as needed.
-Original Message-
From: Christopher
I have a separate merge module that creates the infrastructure of NServiceBus
host I have a custom action that runs NServiceBus.Host.exe
/installinfrastructure
Then the 4 service merge modules install files ONLY common to that service and
custom actions that create/uninstall the service on
Hello all,
I am new to this mail-list thing, so hopefully I am doing this right.
I am having trouble installing a program, using a WiX-built installer on a
vanilla Windows XP install. WiX 3.0.5419 is being used to author the installer.
I cannot update to a newer WiX toolset at this point.
I
Hi. I came up against this too. I had the server SSL certificate in (Local
machine\my) already. I wrote a custom action in C# to take the name of the
website as a parameter and install the certificate into the website given the
certificate's 'friendly id' using the Microsoft.Web.Administration
If you are using Wix 3.0, then you must be using some other 3rd party boot
strapper/chainer since burn wasn't a production version until 3.6. The only
other option would be that you are attempting concurrent installations which
are not supported
I tried setting a condition:
/Bundle Name=My Software
Condition=VersionNT = 500
.../
But it always evaluates as false.
/Condition 'VersionNT = 500' evaluates to false.
Bundle global condition check didn't succeed - aborting without loading
application./
A Windows 7 machine
Just like Rob stated, use:
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:bal=http://schemas.microsoft.com/wix/BalExtension;
Bundle ...
bal:Condition Message=Your error message about the OS goes here.VersionNT
= v5.0/bal:Condition
/Bundle
And ensure your project has a reference
Based on Neil Sleightholm's blog,
http://neilsleightholm.blogspot.com/2012/05/wix-burn-tipstricks.html, it
seems that the VersionNT is a value like v6.1. Strange that it's not the
same format as the Windows Installer property, but now the condition
evaluates as expected.
/Condition=VersionNT =
Thanks Jacob. Looks like I did gloss over that part in the documentation.
Interesting that the VersionNT value was changed though.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-conditions-tp7580784p7580875.html
Sent from the wix-users
Burn has native support for versions. It works immensely better than the
MSI string based versions. That's why we chose to use it. It works so much
better. The doc explicitly calls out the differences.
On Wed, Sep 26, 2012 at 8:24 PM, Nick Ramirez nickra...@hotmail.com wrote:
Thanks Jacob.
That is exactly how you specify an unmanaged Component.
On Wed, Sep 26, 2012 at 10:50 AM, Allan Edwards
allan.edwa...@pointsolutionsllc.com wrote:
I was able to specify a component with an empty guid
Component Id=SilverlightXap Guid=
The installer compiled, linked, ran. The reason I found
Experimenting a bit.
Installing a newer version bundle over an older one causes the old bundle
entry in Add/Remove Programs to be overwritten with the new one, such as
going from bundle version 1.0.0.0 to 1.1.0.0. In the end I only get one
entry. The MSI that's packaged gets a major upgrade. (I
45 matches
Mail list logo
