For all the problematic components, i see the following:
MSI (c) (14:9C) [16:11:09:263]: Disallowing installation of component:
{06F9816A-71E7-4B8E-860B-90E3BBF0B06C} since the same component with higher
versioned keyfile exists
MSI (c) (14:9C) [16:11:09:265]: Disallowing installation of
I am working with WiX from last 5 month with no issues. Recently, i am in
need to have StartIn property in App Desktop shortcut. By default, its
empty.
I am working with below code:
*Component Id=myapplication.EXE DiskId=1
Guid=D42BBB80-579B-42B3-A65D-130829F2982D File
Thanks for replying.
I'm sure that there is no dependency problems.
If I run the msi installer with elevated privilege on that user's computer,
the install will finish successfully.
It turns out Windows Installer failed to extract the custom action dll to
temp directory during the
Thanks Bryan and Phil,
Using only 'UPGRADINGPRODUCTCODE' worked to differentiate between Uninstall and
Install cycle of an Upgrade.
However this condition is false if Uninstalled from Add Remove Programs.
I want the custom action to run in below two scenarios:
1. During Uninstall cycle of an
-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: Friday, April 25, 2014 11:30 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How implement installer to update single file ?
Upgrade? Patch?
If you have the old MSI, there are a couple of options
Hello,
I'm using wix 3.8 in Visual Studio 2010.
If I have 2 components in a fragment in a wxs file and I only reference one of
them in a feature I get an ICE21 error.
If I have a wxs file with components where none of the components are part of a
feature I get no error, the components are
Classification: Public
I tried rollback but it isn't between installinitialize and installfinalize so
it errors when you start the MSI :(
-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: April-27-14 1:13 PM
To: General discussion about the WiX toolset.
Subject:
Ok, I have discovered something else. For other reasons I've started developing
a little notification application for our users. This is to run at login and
stay running while they go about their use. It will from time to time remind
them of things they should be doing and that sort of thing.
All the assemblies and config files are present after upgrade
Le Vendredi 25 avril 2014 17h57, John Cooper jocoo...@jackhenry.com a écrit :
Something is definitely wrong with the code. Are all the assemblies and config
files present after upgrade? I never see this unless something is
I have an installer that invokes InstallUtilLib.dll via a set of CAs as
documented in
http://blogs.msdn.com/b/josealmeida/archive/2004/11/08/253831.aspx
http://avinashkt.blogspot.co.uk/2007/05/how-to-create-installer-using-wix-which.html
If I simply double-click on the MSI or run it using
The shortcut should be under the Component tag, not the file tag, as
described in the Stack Overflow answer to your question there. If
that's not working then you could supply a bit more info about what
you've tried.
---
Phil Wilson
On Sun, Apr 27, 2014 at 11:18 PM, Satbir Singh
By default immediate custom actions run with limited user rights (even
if the user is admin) because the UI sequence isn't elevated by
default. So it might be a security issue on UAC systems.
---
Phil Wilson
On Mon, Apr 28, 2014 at 1:50 AM, Uni Gauldoth unigauld...@gmail.com wrote:
I'd back up from the error 2869 and see what's before that. That
error is when it's decides to show you an error but doesn't like the
error dialog, and the actual error is prior to that. Where did you get
that error dialog from? That's a common error in Visual Studio setup
projects, so did you
Thank you Phil.
I am trying the Using Patch Creation Properties approach. I made two
subfolders, 3.8.1 contained only the original DLL I wished to replace, and
3.8.2 the updated DLL.
http://wixtoolset.org/documentation/manual/v3/patching/patch_building.html
Should both UpgradeCode and Product
While I have not used that process, my understanding is that you are creating
a 'small update' patch for the original version of the two MSI files (used
in that process). (The updated version of the two MSI files is not
distributed. Only the original MSI and the patch which targets only that
Are there others experienced in patching/updating that can share an example or
offer advice?
I followed the Using Patch Creation Properties tutorial which installs an
updated sample.txt file. This worked well.
http://wixtoolset.org/documentation/manual/v3/patching/patch_building.html
Phil,
Many thanks for the comments.
To answer your questions ...
So far as I recall, there were no other errors recorded in the log file - I'll
check again in the morning.
So far as I know, the error dialog is standard WiX 3.8. I haven't consciously
imported anything from Visual Studio. I
Dit mailadres is niet meer in gebruik. Mail kan je voortaan sturen naar
basti...@careercontrol.nl.
--
Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+
Hello,
I know you said the installer prompts for elevated but do you have this?
InstallPrivileges=elevated
InstallScope=perMachine/
In the package ID section in your product.wxs file.
On Mon, Apr 28, 2014 at 5:46 PM, b.ras...@leonit.nl wrote:
Dit mailadres is niet meer in
19 matches
Mail list logo
