Ah the same version upgrade problem - I have questioned this quite a bit
on this list and raised a defect http://sourceforge.net/p/wix/bugs/3065/.
There isn't a workaround in WiX other than changing the bundle version
(yet) but if you have your own BA I have put some code in the defect that
should
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 a
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
>
>
>
> The installer compiled, linked, ran. The reason I found this problem was
> that
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 wrote:
> Thanks Jacob. Looks like I did gloss ov
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 mailin
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 = v6
Just like Rob stated, use:
http://schemas.microsoft.com/wix/2006/wi";
xmlns:bal="http://schemas.microsoft.com/wix/BalExtension";>
VersionNT
>= v5.0
And ensure your project has a reference to WixBalExtension.dll.
The underlying problem is you missed the documentation on the Bundle/@Condi
I tried setting a condition:
//
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 should have a VersionNT property greater than 500. In
fact, even setting
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
(http://msdn.microsoft.com/en-us/library/windows/
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 l
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 ru
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 i
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 Pai
>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'.
I was able to specify a component with an empty 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
---
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 ex
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:
http:
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:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Progress-UI-isn-t-working-using-burn-on
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-
I have two installers that share 4 services... each service creates its
service and "uninstalls" its service:
NOT
Installed
NOT
Installed
Installed
Installed
for the fileset I have added: SharedDllRefCount="yes" which will ensure that
the files will not be unins
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 execu
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 the
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 c
Uhh, would it not be:
Though looking at the documentation, I don't see the registry search documented
for the bundle. If that hasn't been fixed in 3.7 then someone should log a
documentation bug.
-Original Message-
From: Morrison, Robert (GE Tech Infra, consultant)
[mailto:r
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
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 my
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.
http://schemas.microsoft.com/wix/2006/wi";
xmlns:bal="http://schemas.microsoft.com/wix/BalExtension";
xmlns:util="http://schemas.microsoft.com/w
That's the correct way.
On Wed, Sep 26, 2012 at 1:59 AM, Miss Parker wrote:
> 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:
> http://windows-installer-
Just to clarify this is not Bundle/@Condition it is a condition inside
your element.
Neil
>This is for detecting net 3.5 in windows server 2008 R2.
>
>
>
>Variable="NETFX35SP"
>Root="HKLM"
>Key="SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5"
>Va
This is for detecting net 3.5 in windows server 2008 R2.
-Original Message-
From: Morrison, Robert (GE Tech Infra, consultant)
[mailto:robert.morri...@ge.com]
Sent: 26 September 2012 14:29
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] B
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
Phone:
To just display a message try adding a e.g.
silverlight test
here
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 is required before installation. I have not found a way in the
>Bootstrap
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 cod
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
o
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: (5
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
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 l
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 toolset.
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:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Getting-at-the-DisplayName-of-a-package-in-a-custom-bootstr
answer my own question: put it under the element. Works
perfectly. Thanks!
2012/9/26 Marc Wandschneider :
> 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 element?
> Inside
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 pac
awesome!
yes, the problems were a twofold:
1. i was using absolute paths to an image element. I just changed the
back to "logo.bmp"
2. I wasn't including the logo.bmp file in my final setup package. I added:
to as per Jacob's suggestion, and now
it's all great.
Thanks so much!
m,
2012/9/
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 09:27
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 element?
Inside the ?
Thanks so much!
marc.
2012/9/26 Hoover, Jacob :
> The references you would see about Wix would only be scheduled
44 matches
Mail list logo
