Can you post the entire verbose log somehere?
Phil
-Original Message-
From: Alain Forget [mailto:afor...@cmu.edu]
Sent: Saturday, June 15, 2013 11:11 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] Uninstall restart issue
I'm still wrestling with thi
I'm still wrestling with this request to restart on uninstall. To recap, I have
an MSI that when I install it, and then try to uninstall it, it usually tells
the user that some of the files to be uninstalled are in use and will require a
reboot. However, this should not be, because the services
Thanks very much for the information and the various ideas. Knowing that it
is possible to change the URL at run time is a big help. I will work
resolving the 'known unknowns' issue and may be able to take advantage of
another feature of our product to discover the web site. I am having a lot
of
A BA can override that behavior but I agree the default in the Burn engine
doesn't seem quite right in this case. The patch should be removed. I think
Burn should have enough information to know that it should pull out the
superseded patch in this case. Can you open a bug? If you're interested in
You automatically get a "free" upgrade RelatedBundle matching the
UpgradeCode. That way you're always able to upgrade your bundles. MSI
doesn't require this with MSIs which catches people by surprise sometimes
when they figure out at v2 that they can't upgrade v1.
On Sat, Jun 15, 2013 at 6:02 AM
Sure. The documentation is built from src\chm. If there is an improvement
in there we can make, feel free to submit a pull request. If you don't
actually want to fix the issue, you can open a bug and wait for someone
else to get around to it.
On Sat, Jun 15, 2013 at 12:34 AM, Simon Stevenson wr
Thanks.. do I also need RelatedBundle set in the MSI bundle or will suffice in the MSP bundle?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-not-visible-in-ARP-if-MSI-installed-via-Bundle-tp7586533p7586583.html
Sent from the wix-users ma
Hi all
I'm trying to set up a patching system using burn. We do cumulative
patching and previously had the msp patches set up to supersede one another.
After installing the main bundle, followed by the patch bundles in sequence
v1.1 => v1.2, I can either keep v1.1 displayed in ARPs updates (new
up
This is fixed in the newest build of 3.8 (less than a week old) where the
bitness of the AppPool is always set ignoring the default setting, so remove
that CA when you upgrade. It is based on the bitness of the component
installing the WebAppPool (which defaults to the bitness of the MSI).
It
1. Yes
2. The default scheduling has the searches run before the UI dialogs are ever
shown, so typically, registry searching after UI requires custom actions.
Blair
>
> I have a couple of questions:
> - Is the publish tag the only way to perform an action after a user input
> interface ev
Try:
Company© My Product Name™
The XML is parsed into Unicode, then that is converted to the indicated code
page, which either will or won't contain any given glyph. ™ isn't (tm) in
Unicode, and whatever it is in Unicode isn't in 1252.
Blair Murri
> From: r...@robmensching.com
> Date: Sat,
Sorry to break in here 10 days later, but this is important.
The section of the page pointed to by this URL seems to indicate that the
"/home" directory can be redirected to wherever you need it to be (e.g. a user
location instead of under program files).
http://www.rtems.org/wiki/index.php/M
Hi,
It depends on the type of component that installing Apppool whether to set
this bit. If your component is 32 bit then this bit will be set on App-pool.
So my suggestion is to include 2 conditional components that create the
same App-pool and conditions on them must be mutually exclusive
Regard
Ok. In the meantime could the docs be updated to note that the exit code will
get remapped as a HRESULT to be presented to the user?
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Saturday, 15 June 2013 09:22
To: General discussion for Windows Installer XML t
Technically you can install .NET 4 on XP SP2 if you install MSI and WIC
updates first (which we do), in this case the error code means you don't
have the prerequisites... but I'm not sure if you would get the same error
on SP1 to say that it's just plain not possible.
-Original Message-
Fr
15 matches
Mail list logo
