If you wish to have a bootstrapper (such as uninstall.exe) called by ARP
instead of having MSI called directly to remove your program, you need to do
three things:
1. add the ARPSYSTEMCOMPONENT property to your MSI.
2. populate the "legacy" Uninstall key. This will include adding your
uninstall co
I'm playing with the DTF / WPF embeddedUI sample. Being new at writing
external UI's, something has me puzzled.
I've read before that when you run with an external UI that you basically have
to drive the whole ui sequence yourself. That said, what if I want to leverage
say AppSearch? I trie
Uhh, that still won't remove Products across context (per-machine vs.
per-user) though right?
On Thu, Jan 28, 2010 at 12:10 PM, Neil Sleightholm wrote:
> I may be missing the point but you can remove any other MSI with this:
>
>
>
> IncludeMinimum="yes" IncludeMaximum="no" Property="REMOVEOLD
Hi all,
I have a component that contains both a category and a file. This is a new
component that didn't exist in the old MSI. I've added this component to my
patch, and the file is getting updated correctly but the category isn't
touched. I used Orca and applied my msp to the original MSI a
HI,
How to execute uninstall.exe when I push the "Remove" button in the Add or
Remove Program?
Or how to create a bootstrapper for uninstall ?
Thanks, Akihiro
--
The Planet: dedicated and managed hosting, cloud storag
That dialog usually means that the product code is already used by an
already installed product.
In WiX v3, use a produ...@id value of "*" (and never set the packa...@id
value to anything except "*" under any conceivable condition) The
ProductCode will always be different, automatically generating
That isn't a setting you can do on a per-msi basis (only on a per-computer
basis, that is, remove it for all msi files on that computer).
-Original Message-
From: Sam Strasser [mailto:sam.stras...@microsoft.com]
Sent: Thursday, January 28, 2010 1:16 PM
To: wix-users@lists.sourceforge.net
I've checked the How to, and the tutorial. I tried using the example in the
tutorial. I generated guid's for all the appropriate bits, and tried to install
the upgrade from the tutorial example, and in every case it throws up a dialog
box to the effect "that is already installed, please use Add
Absolutely. Upgrading resolved the issue. Thank you.
--
View this message in context:
http://n2.nabble.com/RegistrySearch-Type-raw-causes-a-1-to-be-written-in-RegLocater-table-should-be-a-2-tp4468104p4476425.html
Sent from the wix-users mailing list archive at Nabble.com.
Wow, that's incredibly ancient - an early development build from 2004 or
earlier. The bits have probably rotted. The release version of WIX 2.0
is 2.0.5805.0 which was released in 2008; since WiX 3.0 was released in
July 2009 though, even that is obsolescent.
If you want to stick to WiX 2.0 (perha
Hello,
I'm generating an .msi, and in my .wxs file I say to disable repair from ARP as
follows:
Repair is disabled correctly in ARP. When I right click on the .msi in Windows
Explorer, though, I see the option to repair, which I don't want the user to
see or use (see attached image). How c
>From the behavior listed, it would appear to me that the old MSI has a
ResolveSource action AND that they use their bootstrapper to ensure that the
"source" is available to successfully uninstall.
The HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
registry key supports tw
For the 2.0 release, the latest is 2.0.5805.0 from August 2008. Your version
is way old. Please upgrade.
Even 3.0 has been released (no longer in beta). 2.0 is now considered
legacy.
-Original Message-
From: Toews, Margaret [mailto:margaret.to...@wolterskluwer.com]
Sent: Thursday, Januar
OK, I think I know the answer to this before I ask, but I'm earnestly hoping
that this is not a dead-end. Here's the situation:
We're moving from InstallAware to WiX. We have an application installed from an
InstallAware-generated EXE and MSI. If you go to Add/Remove Programs and remove
it, it
I may be missing the point but you can remove any other MSI with this:
(The odd values in UpgradeVersion/@Maximum are due to a bug in one of
the ICE validations.)
You can add as many of these as you like to remove old installs. Hope
this helps.
Neil
-Original Message-
From: Dave
Are you sure you're using WiX 3.0 / is it possible the version of
WiXIISExtension you're using is from WiX 3.5? I don't believe the
"WriteIIS7ConfigChanges" custom action existed until WiX 3.5.
Regardless, looks to me like a bug; I'd file one on sourceforge with as much
repro information as you
Thanks for the pointer to the log. FindRelatedProducts was failing because my
install was per-user and the previous was per-machine. Fixed that, and got past
that problem. Now the uninstall is starting but failing. So I'll probably be
posting again soon Thanks!
-
Properties like WindowsVolume end with a \ and I'd guess that the user input
doesn't.
Phil Wilson
-Original Message-
From: Andy.Kruger [mailto:appr...@gmail.com]
Sent: Thursday, January 28, 2010 1:12 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Keyboard Enter key press
It's possible that it could be a permissions issue, but it doesn't seem to
be. After changing the local security policy to give the Administrator
account the "log on as a service" account, the same behavior remained. I
didn't see any other privileges that seemed to suggest that they'd
specifically
No, for a major upgrade the Product/@Id must be different.
It appears that your authoring is correct. At this point, I'd fall back to
looking at the verbose log file and double checking the UpgradeCode GUIDs
everywhere. Since your using lots of preprocessor variables, I'd also
carefully look at th
Wix version 2.0.1605.0
Margaret Toews
Programmer Analyst
ProSystem fx Engagement
CCH, a Wolters Kluwer business
Phone: 316.612.5148
Fax: 316.612.3406
E-Mail: margaret.to...@wolterskluwer.com
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Wednesday, January 27, 2010 11:20 P
I think what you're missing is the Product ID must also match, else Windows
Installer sees it as a completely different product, not just a different
version of the same product. Try putting the same GUID in your mailto:dave_mat...@ntm.org]
Sent: Thursday, January 28, 2010 7:49 AM
To: wix-users@
Hi to everybody,
I'm struggling against an issue since last week and I need help.
Fatcs follows:
I created a MSI for an application using Wix 3.0.5419.0 RTM.
This MSI creates also some web virtual directories and an application pool on
the IIS server and all works fine.
My troubles started when
We are moving our installer generation to WiX. Unfortunately, we delayed on
this too long and we now find ourselves needing to switch *NOW* because we have
pretty much hit a brick wall with our current installer software and there is
no fix coming from the company. So, expect several questions i
You can also see the "New Link in the Chain" section on the following link:
http://www.tramontana.co.hu/wix/lesson2.php
Or even this link maybe useful
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html
On Thu, Jan 28, 2010 at 5:00 PM, Anu Dev wrote:
> Hi
>
> I would like
Hi
I would like to add a new dialog to the WIXUI_INSTALLDIR. I saw a method
defined in this article
http://www.dizzymonkeydesign.com/blog/misc/adding-and-customizing-dlgs-in-wix-3/
Is this the only way to solve. Is there any method with which i can extend the
behaviour of the default dialog s
I have added a condition INSTALLDIR <> WindowsVolume to the "Next" button of
the InstallDir dialog
to prevent installation to the windows root drive.
This condition gets validated and next button gets disabled if the condition
is true when the user clicks the button.
But if the user enters the w
27 matches
Mail list logo
