I do have a few custom action so that may well account for it - I am using
a custom BA so I will try tweaking that.
Neil
>I have looked at WixStdBA, and I do believe is not accounting for CA
>progress updates would cause overlap in the overall progress. I
>specifically remember seeing comments i
I have looked at WixStdBA, and I do believe is not accounting for CA progress
updates would cause overlap in the overall progress. I specifically remember
seeing comments in wiutil.cpp:
// HACK!!! this is a hack courtesy of the Windows Installer team.
It seems the script planning ph
Thanks Peter.
I have followed the manual and tutorials and created a basic installer, which
works with the WixUI_InstallDir extension:
---snip---
http://schemas.microsoft.com/wix/2006/wi";>
Thanks for that I think you might be right, when I upgrade I typically on
install 2 large MSIs and as you say they do appear to overrun. I'll have a
look at the code too and see if I can spot the issue.
Neil
>I can't help you with it, but I (1) can confirm the behaviour and (2)
>add that it has
My apologizes :)
You are correct sir!
The reg key was there...
Steve
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: November-14-12 2:15 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Help?
I am using SQLExpress 2012 a
Same results with versions 10.00.35.0004, 10.00.36.0004 (HF1), and
10.00.37.0004 (HF2).
I am changing the bundle version as well as the version of the msi, but
still the second patch for the bundle appears alongside the first one, not
replacing it as I would expect.
Do I need to do something to "
I can't help you with it, but I (1) can confirm the behaviour and (2)
add that it has nothing to do with ExePackages specifically or a mix of
types. I have a bundle of all MSIPackages and it does exactly the same
thing there. In fact, as the number of packages in the bundle increases,
the larger th
Is anyone able to help with this?
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 07 November 2012 22:20
To: General toolset. (wix-users@lists.sourceforge.net)
Subject: [WiX-users] ExePackage Progress
Can anyone tell me how the burn progress bar works for ExeP
Windows only prevents a second install from starting the "Install" phase. You
can open as many .msi files as you like into the user interface phase.
> -Original Message-
> From: Hans ter Horst [mailto:hoshis...@gmail.com]
> Sent: Thursday, 15 November 2012 2:47 AM
> To: General discussio
Personally that doesn't sound like a job for an installer; I would write a
support application that would work on those scenarios. I tend to install my
SQL databases in a folder of the root drive rather than in program files as it
tends to be less prone to compression but I guess master etc coul
Hello all,
I am trying to write an application that will go through the file table
in an msi and make sure the files on the system are the same version and
location. Basically a regression test for our installers. I have everything
good except I have no idea how to find the installer th
I can use the registry to detect the instance just fine. Unfortunately,
that doesn't handle all the situations.
Sometimes the user has uninstalled the software, and SQL doesn't always
clean the registry up completely, so the instance still appears to be there
when it isn't. Sometimes, the user h
I may not be the best to answer as I am new to Wix and Burn, but I was able
to hide the button using a custom Theme as indicated here:
http://neilsleightholm.blogspot.ca/2012/05/wix-burn-tipstricks.html
Regards, Dan
On Wed, Nov 14, 2012 at 2:33 PM, Miller, Nick (GE Intelligent Platforms) <
nick.
I have a bundle that uses the standard
It always shows the Repair button on the UI once it's installed. I want
to hide or disable that button.
I checked the bal: schema, and found the following attributes.
Attributes
Name
Type
Description
Required
LicenseFile
String
Source file o
I am using SQLExpress 2012 and this works for me - I have been using the same
logic for SQL2005 and 2008 so I am fairly sure it works.
Neil
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: 14 November 2012 18:32
To: General discussion for Windows Installer
Are you using the MajorUpgrade element? And what do you have for the
Product's Id? An asterisk? If it's the same Product ID, version and
UpgradeCode, I am surprised you are not seeing the Repair/Modify dialog when
the second MSI is run.
--
View this message in context:
http://windows-installer-
I have SQL Express 2012 installed and there isn't a \InstanceNames\ in the
registry so that would fail for SQL EXPRESS
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: November-14-12 11:45 AM
To: General discussion for Windows Installer XML toolset.
Subject: R
In my bootstrapper I have this:
-Original Message-
From: Chad McCune [mailto:c...@selerix.com]
Sent: November-14-12 10:59 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Help?
I'm new to WiX, started playing
In what way was it messy when removing ? Windows Installer should normally be
able to handle that.
-Original Message-
From: Hans ter Horst [mailto:hoshis...@gmail.com]
Sent: 14 November 2012 16:06
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to pr
Here is the code to detect whether your instance is installed:
This will set two variables SqlInstanceFound if the instance is present and
SqlVersion is the SQL version of the instance (you might not need the second
one but it is useful if you want to upgrade existing
Hi
I want to allow users to review log file after installs complete. I found on
mailing list that path to log file is in "WixBundleLog" variable, but for me
log file is created only if I close my MBA.
Is there any way to say Engine create log file after installation complete, but
before user c
I would suggest starting with WixStdBA. You should be able to configure the
bundle with a few DirectorySearch/FileSearch/RegistrySearch/ProductSearch
elements and then use the InstallCondition to tell the Exe/Msi package to
install and mark it as Permanent so that uninstalling doesn't remove it.
How would I go about to stop even the initial phase from being executed at
the same time?
To explain, in our case different features were selected in two
incarnations of the same installer and both were installed and the result
was very messy when trying to uninstall. We would certainly like to pre
I'm new to WiX, started playing with it last week.
Our current software installer works, but has issues. We are going to be
moving to VS2012 soon, and the MS Setup Project is no longer available, so I
was going to take this opportunity to update and improve it.
Scenario: Like most softwa
I think you can be in the non-elevated portion of the process multiple times
- the mutex only protects the execute sequence, where the system is being
modified.
-Original Message-
From: Hans ter Horst [mailto:hoshis...@gmail.com]
Sent: 14 November 2012 15:47
To: General discussion for Win
In case others run into the same question, I managed to address the problem
by adding the following lines to my dialog definition files:
1
Installed
On Wed, Nov 14, 2012 at 3:12 PM, Hans ter Horst wrote:
> Hello,
> I am using a treeview based installer and would allow the installation to
> be
I get reports that people managed to have our installer open several times
at the same time by accidentally clicking on the MSI file again while the
same installer was already open. I seem to recall that is normally not
possible due to the Microsoft installer MUTEX but somehow that seems to be
miss
Hello,
I am using a treeview based installer and would allow the installation to
be modified by starting the installer again and selecting some more
features.
When I installed a few of my features and then start the installer again,
it opens with the Welcome screen and upon clicking Next, it displ
28 matches
Mail list logo
