Thanks--I got it to work! For others interested, I posted more details here:
http://stackoverflow.com/questions/3304624/cancel-an-msi-without-showing-the-installation-interrupted-dialog
-
A. Logan Murray
http://pihole.org/
--
View this message in context:
http://windows-installer-xml-wix-to
Hi all. I would like to avoid showing that last dialog when the user clicks
"Cancel" before installation has begun. I would still like the dialog to be
shown if the user cancels an installation that has been started, as this
tells them the cancellation was successful, but if no install is taking
p
> documentation.
>
> That said, if you learn something and have a suggestion how we can improve
> the WiX toolset to help the next person learn faster, I would be very
> interested in hearing those suggestions.
>
> Thanks.
>
>
> -Original Message-
> From:
"{)/];)^{";$,+=(++$,);$_.=">&$,";`$_`;
>
>
> -Original Message-
> From: chaiguy1337 [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 24, 2008 3:38 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Run CA on uninstall, but not when
ey both have to be per-user or per-machine. You can't mix and match as
> far as major upgrades go.
>
> -Original Message-
> From: chaiguy1337 [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 24, 2008 2:23 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re
er
installation.
Bob Arnson-6 wrote:
>
> chaiguy1337 wrote:
>> My WiX msi has no ALLUSERS property at all, wheras my original product
>> had
>> ALLUSERS=2. However, I want my new product to be per-user.
>>
>
> You can't do "cross-context"
I logged the install and found this, but I can't make any sense of it:
Action ended 17:16:57: InstallFinalize. Return value 1.
MSI (s) (B8:58) [17:16:57:583]: Doing action: RemoveExistingProducts
MSI (s) (B8:58) [17:16:57:583]: Note: 1: 2205 2: 3: ActionText
Action 17:16:57: RemoveExistingProdu
I'm having a problem: turns out the removal is not taking place at all. I
guess I didn't notice this before. When I install my update overtop of an
existing installation and look at add/remove programs, there are two
entries: one for each version.
Can someone give me a clue as to what's wrong? I'
Ideally I prefer the simplicity of a messagebox over a wizard for
uninstalling, since a yes/no answer is all that is needed, but I think I
might just move the data directory to the recycle bin and not bother the
user with a question at all, since this still gives them the ability to
restore it if
Aha! Thanks for the warning; that would have surely caused headaches as
currently my custom action is scheduled before RemoveExistingProducts.
Do I need to also schedule FindRelatedProducts in order for
RemoveExistingProducts to work?
Alexander Shevchuk wrote:
>
> Remember that UPGRADINGPRODUC
Rob Mensching-2 wrote:
>
> Can you just use the native MSI functionality to remove the application
> data?
>
No, the path is determined at runtime based on the user's AppData directory
(and is theoretically customizable, though I haven't added ui to do that)
and moreover I want to either:
a)
upgrade.aspx
>
> Also, when a major upgrade runs the UPGRADINGPRODUCTCODE property is
> passed into the version being uninstalled.
>
> -Original Message-
> From: chaiguy1337 [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 24, 2008 8:52 AM
> To: wix-users@lists.sour
Back when I wrote my installer using Visual Studio's setup project, there was
a flag RemovePreviousVersions that would allow future versions of my program
to update previous versions simply by removing the previous version and
installing the new one overtop of them.
My first question is how to do
Thanks! Got it working.
Bob Arnson-6 wrote:
>
> chaiguy1337 wrote:
>> Is there a particular reason the example in the help file didn't use
>> "normal"
>> exe custom actions? I don't want to do something that might cause
>> problems
>>
wrote:
>
> chaiguy1337 wrote:
>> Is there a particular reason the example in the help file didn't use
>> "normal"
>> exe custom actions? I don't want to do something that might cause
>> problems
>> later.
>>
>
> Because a mor
Is there a particular reason the example in the help file didn't use "normal"
exe custom actions? I don't want to do something that might cause problems
later.
Bob Arnson-6 wrote:
>
> chaiguy1337 wrote:
>> Hi all. I'm looking for a way to pass command line
Hi all. I'm looking for a way to pass command line arguments to my app
launched when the installation is complete, so that my app knows it was
launched by the installer.
I basically copied the example from the help file:
Where might I add my "-installer" switch? I tried changing the Value of
Wow, AutoIt is really great! I'm totally loving it. It's a simple, easy to
use syntax and it's quite sophisticated. Compiles to a native app, very
small footprint. I've got a nice little custom bootstrapper now, combined
with my WinRAR self-extractor and WiX installer, and this is shaping up to
be
WinRAR! I've been using WinRAR for years as my main compressed archive
viewer, but only just recently discovered it has support for creating
self-extracting archives (SFX it calls them) as well! Not only that but it's
by far the best out of all of the ones I've tried.
Namely, it does everything I
Thanks for the tip! I will look into the AutoIt language. To get me started,
could you provide me with a sample piece of your script that checks the .NET
version and downloads/launches the installer?
Logan
DEÃK JAHN, Gábor-2 wrote:
>
> On Sun, 19 Oct 2008 10:41:05 -0700, Rob Mensching wrote:
Well the problem was that the bootstrapper was not working properly, in a
number of ways. (I'm attempting to use the NetFx35ClientSetup.exe
bootstrapper)
First of all it was always running, even if the user has the framework
installed, which I don't like because it detracts from my app's setup
ex
I'm able to successfully sign my msi post-build, but when the installer runs,
although the Vista UAC shows that it is signed and verified as coming from
my organization, the name of the file is some random a29fc82b.msi type of
thing. I was wondering if there's any way at all to change the (apparen
22 matches
Mail list logo
