There is an outstand bug in the progress bar
(http://sourceforge.net/p/wix/bugs/3139/) that probably accounts for this.
My extended BA (http://wixextba.codeplex.com/) gets around this cosmetically
(that is, the problem is still there but not so obvious).
Neil
-Original Message-
From: K
Iam tried with all UI references like Wix_Mondo,Wix_UIinstallDir.
When I use Installdir,iam selecting c:drive but it is going to another drive
which is having more free space.
When I use these various Windows folders in my DIRECTORYREF its not taking.
How can I overcome this problem.
-Original
Hi,
Am using wix 3.7. In our project having more than hundreds of files shipping
from msi. My question is progress bar almost complete 75 to 80 percent
within few seconds before started to ship those files. Remaining 20 percent
running more than 4 minutes for shipping those files.
Could you plea
The default command-line would be "msiexec /i your.msi"
Those properties are documented in the MSI SDK. I'd suggest starting there.
On Mon, Jan 7, 2013 at 12:18 PM, Wang, Zhongsheng wrote:
> Thanks Rob for analyzing this issue with me. I really appreciate your help.
>
> So what if the user cli
Thanks Rob for analyzing this issue with me. I really appreciate your help.
So what if the user clicks installer.msi file to run the installation? What
would be the default command line switch? What if I don't specify /i from the
command line at all?
Can you be more specific about the Installed
You can't do a minor upgrade with the /i commandline switch. If
REINSTALLMODE is set it'll show up in the log file by default.
It sounds like you have a major upgrade and repair, no minor upgrades. So
you can use the Installed and REMOVE and UPGRADINGPRODUCTCODE properties to
sort out all your st
We don't do anything special for REINSTALLMODE at all. For MSIEXEC option, we
only use /i and log enabling. We let MSIEXEC to figure out whether it is doing
REINSTALL or fresh install.
How do I log REINSTALLMODE information to the log file?
Thanks,
zhongsheng
-Original Message-
From: R
That only defines a major upgrade. A minor upgrade is handled by
recachine/repairing the MSI (msiexec /fv switch). A repair is just when the
product is installed again and the REINSTALLMODE is set to something that
would cause files to get written again.
How are you handling the REINSTALLMODE?
O
Rob,
Here is how we handle Major and Minor upgrade. I don't even know how to handle
Repair so I think Repair is as default.
Thanks,
zhong
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Monday, January 07, 2013 11:05 AM
To: General discussion for
Can you share how you are launching the Repair vs. Minor Upgrade vs. Major
Upgrade?
On Mon, Jan 7, 2013 at 10:34 AM, Wang, Zhongsheng wrote:
> however, the behaviors of minor upgrade and repair are not the same. I
> hope there are some clarifications.
>
> My installer works with Repair but not
however, the behaviors of minor upgrade and repair are not the same. I hope
there are some clarifications.
My installer works with Repair but not with Minor Upgrade.
With Repair, InstallInitialize is called once. With Minor Upgrade and Major
Upgrade, InstallInitialize is called TWICE. Sometimes
Minor upgrade is just a repair. It's a recache (stomp the MSI in your
cache) then repair using that. That's why I was saying you can't really
tell the difference between (force) repair and minor upgrade.
On Mon, Jan 7, 2013 at 10:05 AM, Wang, Zhongsheng wrote:
> Thanks Neil and Rob for your co
Thanks Neil and Rob for your comments.
To uninstall a filter driver that is used by OS, reboot is always required to
remove the service. The solution here is NOT to uninstall the filter driver
during the maintenance mode (repair, minor upgrade, and major upgrade) in my
opinion, but I don't know
In addition to that you might want to read up on the ROOTDRIVE property as it
appears it is somewhat involved in the symptoms you are describing.
http://msdn.microsoft.com/en-us/library/aa371372(VS.85).aspx
Also, don't forget about the well-known properties that identify various
Windows folder
Burn bundles provide tremendous advantages when distributing software over
the internet. I'd go as far as to say, "Never ship a naked MSI on the
Internet". I do wonder what is in a 86K MSI though.
On Mon, Jan 7, 2013 at 9:09 AM, Pally Sandher wrote:
> My Burn bundle is 105 MB (110,669,784 bytes
Posted an answer on StackOverflow: probably a bug in the CA. :(
On Mon, Jan 7, 2013 at 8:38 AM, Richard.Oliver wrote:
> Hi
> I'll swing this one around again before filing a bug report in case it was
> missed during the holiday period.
> Apologies if this is bad etiquette.
>
> Richard Oliver
> D
Zhong's scenario with a filter driver is probably harder to get to shutdown
than a typical windows service. I expect that's the big difference.
On Mon, Jan 7, 2013 at 9:00 AM, Neil Sleightholm wrote:
> I don't think this is the issue, I only do major upgrades and the service
> stops just fine.
>
The tutorial explains how to use WiXUI_InstallDir ->
http://wix.tramontana.co.hu/tutorial/user-interface/ui-wizardry
Do you have an INSTALLDIR under your TARGETDIR or are you simply setting
WiXUI_INSTALLDIR to TARGETDIR?
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F:
Surely it is the same, the UI gives you the choice of which SQL - the only
difference is that the UI is in burn not the MSI.
I may not follow what you are doing but SQL Express exe is a wrapper around
many MSIs - if you are running it from another MSI it will fail when I runs as
you cannot have
My Burn bundle is 105 MB (110,669,784 bytes) when built however the 3 MSI's
which go into it total 108 MB (113,602,560 bytes). I assume Burn is compressing
the MSI's to account for the smaller size of the bundle compared to the
individual MSIs (I use 'high' compression on my embedded cabs, might
You can create your own managed bootstrapper for Burn, which can show a UI
of your own design and set Burn variables, or control the results of the
Detect phase. That's what we do in our product, which has also let us set
a few other options and give the user the option to choose their SQL Server
Once again that is not how our PM wants it...
However, the SQL express installer is an EXE initially...
steve
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: January-07-13 12:03 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-us
Are you installing SQL from a CA in the MSI? If so that is not supported as you
are effectively running one MSI from another. You could put the choice for SQL
in the burn UI and then use burn to install SQL (or not).
Neil
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@ti
I don't think this is the issue, I only do major upgrades and the service stops
just fine.
I think there is some timing issue between stopping the service and windows
installer or SCM removing them and consequently the service is marked as
deleted in the registry and not removed until a reboot
Because our PM wants the user to have a choice, use their own SQL Server server
(which most likely they will already have) OR choose a dedicated SQL Server
(2012 Express that we will install (most likely for testing purposes)...
Steve
-Original Message-
From: Nicholas Pierce [mailto:nic
Why not just use Burn to run the SQL Server installers?
Nicholas
On 7 January 2013 16:31, Steven Ogilvie wrote:
> Hi,
>
> In my Database dialog I am allowing the user to choose whether to use
> their own copy of SQL Server or use a dedicated SQL Server Express 2012.
>
> If they choose the dedic
Hi
I'll swing this one around again before filing a bug report in case it was
missed during the holiday period.
Apologies if this is bad etiquette.
Richard Oliver
Developer, Systems Architecture, IT Development
Information Technology
The Open University
Berrill Building, Level 2 North
01908 6 547
Hi,
In my Database dialog I am allowing the user to choose whether to use their own
copy of SQL Server or use a dedicated SQL Server Express 2012.
If they choose the dedicated SQL Server on Next Click I run a custom action
that determines if the OS is 32 or 64 bit and run the appropriate SQL Se
Our installs support multiple languages and we would like to add a few
languages that are not currently supported: English (United Kingdom, en-gb)
and Spanish (Mexican, es-mx)
We created the two new .wxl files using the WixLocalization Culture="en-gb"
and Culture="es-mx"
Then using Studio 2010 to
If you can't get the service to stop in time then you do need to do restart
avoidance.
Unfortunately, in an minor upgrade, I cannot think of anything set natively
by the Windows Installer that will tell you you are in a minor upgrade.
Minor upgrades are basically just a recache/reinstall so if you
Burn will elevate the install much the same way that the Windows Installer
elevates the install. Make sure you put all your stuff that modifies the
machine (aka: requires elevation) in the Chain and it will be elevated.
On Mon, Jan 7, 2013 at 3:27 AM, Raphael DUCOM wrote:
> Hello,
>
> I'm worki
Nothing in the engine to do that. I delete things by hand. I've toyed with
creating a tool to do it but never got around to it. Too much code to
write.
On Mon, Jan 7, 2013 at 12:04 AM, Amadeus wrote:
> SCENARIO
> Burn keeps a cache of the packages it downloads. Sometimes, after a broken
> inst
Cool, thanks for confirming.
On Sun, Jan 6, 2013 at 11:54 PM, Amadeus wrote:
> Hello again,
>
> Just posting to let you know I found (and fixed) the issue. We had custom
> behavior in the PlanPackageBegin event that lets us remove packages based
> on
> user types. This messed up Burn's upgrade
Hello,
I'm working on a boostrapper wich really needs elevated privileges in order to
completly install our solution. (I know I normally should'nt do that, but we
don't have choice because of the specific components needed to be install).
I'm searching a way to define a specific manifest file fo
SCENARIO
Burn keeps a cache of the packages it downloads. Sometimes, after a broken
installation, some files remain in this cache. When Burn sees that they're
in the cache, they're not downloaded again. Sometimes, these files are the
cause of a broken installation - and should be downloaded again.
35 matches
Mail list logo
