In article blu111-ds1a8e9f279888902a16435cd...@phx.gbl,
Blair os...@live.com writes:
What is considered best practice is to fail the installation attempt from
InstallExecuteSequence with an error message indicating that the previous
product must be removed first. This should then show up
IIRC the error dialog will be suppressed, but the text that would have been
in the dialog will be in the error log.
-Original Message-
From: Richard [mailto:legal...@xmission.com]
Sent: Wednesday, July 28, 2010 1:48 PM
To: WiX Users
Subject: Re: [WiX-users] Executing user-interactive
Blair Rob,
I appreciate you both taking the time to explain how MSI (and subsequently WiX)
interact with this problem space. That type of foundational knowledge isn't
found in manuals. I'll be able to rethink a couple parts of my installer now.
Hi,
The problem is solved XP machines but same previledge error I am getting for
Windows 2008 server machine. Is there any other settings need to be done.
Thanks,
Rahul
-Original Message-
From: rahul.ekb...@sungard.com [mailto:rahul.ekb...@sungard.com]
Sent: Wednesday, July 28, 2010
I've done something similar for testing purposes using a custom written
Bootstrapper (in .NET) and some tools from the Windows SDK.
Needed Tools:
- msitran.exe
- WiRunSql.vbs
- WiSumInf.vbs
(all embedded as Resources in the Bootstrapper)
Approach was as follows:
- Extract all tools into the TEMP
Someone has looked at the LocalSystem problem that you're describing for a
rather long time and found that impersonating localsystem is a no go. Give up
:) We did exactly that: removing test connection buttons in the LocalSystem
scenarios.
You should consider not reinventing the wheel and
Hello,
We're currently using WiX 3.5.1902 but for the last couple of releases
we've intermittently been getting access violations in light with the
following information in the event log:
Application: light.exe
Framework Version: v4.0.30319
Description: The process was terminated due to
Agreed. I ended up doing exactly what you suggest. Impersonating local
system requires privileges that even an admin shouldn't have. So you
should not
consider adding this as a requirement in your installer.
dB. wrote:
Someone has looked at the LocalSystem problem that you're describing for a
Hey wix users!
I have an installer which uses the built in WixUI_InstallDir dialogs.
I also have some deferred custom action running between
InstallInitialize and InstallFinalize.
What i am trying to do, is display an update message in the ProgressDlg
when a custom action is executing.
Correct
Msitran.exe is not in the redist list. The vbs scripts were described as
samples so if that's still the case you can do whatever you want with
them.
-Original Message-
From: Thomas Terhaar [mailto:thomas.terh...@voicint.com]
Sent: Thursday, July 29, 2010 3:35 AM
To: General discussion
I haven't used it, but I think what you want is:
ProgressText Action=EventLogConfiguration
Template=[1]!(loc.EventLogCreationProgressBarMsg)/ProgressText
ProgressText Action=EventLogConfiguration_Rollback
Template=[1]!(loc.EventLogDeletionProgressBarMsg)/ProgressText
ProgressText
If it is possible just add some Thread.Sleep(3000); or some WinAPI analog
like ::Sleep(DWORD); to simulate long process work, in this case you'll be
able to see the text.
Hope this helps.
-Original Message-
From: Stelios Kyprou [mailto:stelios.kyp...@formicary.net]
Sent: Thursday, July
Hi WiX users,
I'm brand new to WiX and was just a bit confused about the difference
between INSTALLDIR and INSTALLLOCATION. The WiX tutorial and samples seem to
use INSTALLDIR as the Id of the Directory tag, but when I create a new WiX
project in Visual Studio 2010, that value is automatically
Thanks for the suggestion. I found that return value 3 happens during
'SxsUninstallCA' when it tries to remove the VC++ runtime libs. There are
thousands of lines between action start and action ended for 'SxsUninstallCA',
and I don't see anything obvious there. If I use Orca to remove
In article 009c01cb2f4d$58a5a8b0$09f0fa...@gmail.com,
ALive aliv...@gmail.com writes:
If it is possible just add some Thread.Sleep(3000); or some WinAPI analog
like ::Sleep(DWORD); to simulate long process work, in this case you'll be
able to see the text.
I believe the progress text
I have a strange issue with automating visual studio with votive: I create
several projects (in particular winforms and wix) and modify them in several
ways (remove/add files, modify build properties) using automation objects. But
there is one thing that I cannot achieve this way: adding import
I'm in the process of converting from Wix 2.0 to 3.0.5419.0. Getting a
few ICE errors I need help with.
Here's the first error I get.
C:\Installation\Packages\E3_3_0\Components\comAuthManager.wxs(15) :
error LGHT0204 : ICE03: Bad conditional string; Table: Component,
Column: Condition, Key(s):
Hi All,
I am using using wix v 3.0.5419.0. I have written components for
installing on Windows 2008 to configure IIS by using the XmlConfig and
XmlFile wix custom actions. In my file I have three components to do
similar things, one for when the install is creating the user to be used
for the
You are missing a final )?
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Thursday, July 29, 2010 12:11 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] ICE03 errors
I'm in the process of converting from Wix 2.0 to
Thanks for the ICE03 help. I've only got a couple of other errors and
I'll be converted.
I'm getting a couple of ICE32 errors like this. I assume I have a
Feature name that is too long, using a string of 38 chars while the
Class only supports string lengths of 32. Would that be a correct
When doing a major product upgrade I want to pass a certain value from
the new installer to the existing install. The idea is that the new
install will pass this value to the old install and the old install will
use this value to run a process before it removes its old files. I want
that the
I have figured it out. I created 2 of the 3 components by copying an
existing component, and failed to update the ElementId in the copied
components to reference the correct elements.
A
-Original Message-
From: Amy Rosewater [mailto:arosewa...@spectrumhr.com]
Sent: Thursday, July 29,
There's no way to pass it directly. You would have to store it somewhere and
have the old install retrieve it (via AppSearch or a custom action).
-Original Message-
From: Joe Osman [mailto:joe.os...@taitradio.com]
Sent: Thursday, July 29, 2010 1:40 PM
To: General discussion for Windows
This means that your Class table definition is incorrect (the `Feature_`
column should be s38). Where did you get your Class table definition from?
From http://msdn.microsoft.com/library/aa368585.aspx feature identifiers
should be a max of 38 chars long.
-Original Message-
From: Chad
Hello,
We are seeing a weird case where the rollback sequence is incorrect. Our
product does a major upgrade on every install and schedules
RemoveExistingProduct before InstallInitialize. For most of our customers
this works really well and we see the following during an upgrade. We've had
a
That is what I do and I see the text.
Neil
-Original Message-
From: Stelios Kyprou [mailto:stelios.kyp...@formicary.net]
Sent: 29 July 2010 17:28
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Progress Text update
Hey wix users!
I have an installer
You would need to use a method like this:
http://robmensching.com/blog/posts/2010/5/2/The-WiX-toolsets-Remember-Pr
operty-pattern and then a RegistrySearch to reload them.
Neil
-Original Message-
From: Joe Osman [mailto:joe.os...@taitradio.com]
Sent: 29 July 2010 21:40
To: General
27 matches
Mail list logo
