Hey everyone,
Which action evaluates which features to be installed? In my different
features I use conditions to decide what to be installed or not
(Condition Level=1NAME = test/Condition, installed If
NAME=test), and depending on if the property gets set with a
RegistrySearch or in my own
Hi All,
When I click on msi to install, I get an error message to install the
software using setup.exe only. How can I bypass this and install from msi
directly. Basically I need to create install log file.
msiexec /i file.msi /l*v file.log
I am expecting workarounds or
Balakrishna.BK wrote:
Hi All,
When I click on msi to install, I get an error message to
install the software using setup.exe only. How can I bypass
this and install from msi directly. Basically I need to
create install log file.
msiexec /i file.msi /l*v file.log
I am expecting
Hi,
My name is Mark Knox, I work for a large UK college where my job is to
ensure that the software that is needed by the student and staff is
installed on the network. i found WIX when I needed to install a small
program on the network with the capacity to remove it afterwards
silently. As
Friedrich, Oliver schrieb:
AFAIR its not the Value, that is too long, but the identifier, that should
not be longer than 255.
Qt_accessible_qtaccessiblecompatwidgets1Modul.57F8AC9F_2E4B_4879_A18C_172F2EB1.0
Try to shorten it a bit.
Oliver Friedrich
Consultant - Software Solutions
Well, ICE03 claims following in Windows-SDK:
The string's length is greater than the column width specified by the column
definition. Note that the installer does not internally limit the column width
to the specified value. See Column Definition Format.
So it seems to depend on the Table,
We have a .msi file built from Wix toolset which calls one of the VS SDK tool.
So if the .msi is ran in Vista, even if you are a member of Administrator
group, it will failed. However, if run it as Administrator (Right click
cmd.exe, choose Run as Administrator, then call the .msi from the
Hi there,
I manually create a logs folder during installation using the CreateFolder
option.
During the lifetime of the application this directory is written to with
some logs files.
Therefore, when I come along to delete this directory, because it contains
files the installer does not know
Friedrich, Oliver schrieb:
Well, ICE03 claims following in Windows-SDK:
The string's length is greater than the column width specified by the column
definition. Note that the installer does not internally limit the column
width to the specified value. See Column Definition Format.
So
Hello-
I read that permanent='yes' attribute in the Component tag makes the component
un-installable. I am facing the problem with one of the components in our
product when the permanent flag got included due to the infamous copy and
paste. I read that this sets a regKey but couldn't find the
You need to make sure that your bootstrapper has one of the magical Vista
strings within it like setup or install. This will instantly elevate
the priveledges within Vista unless it has a corresponding Manifest file
telling it not to.
I get the impression that you're calling the MSI file
Msi logging can also be enabled via the registry. The log will be created
in your %temp% folder (just type that in your windows explorer address bar
and you'll be taken to the correct location). In order to enable logging,
copy the following into a file with a .reg extension and then double
Some more info on my problems:
- The log file of msiexec /i shows this:
MSI (c) (C8:AC) [15:57:48:335]: Machine policy value 'Debug' is 0
MSI (c) (C8:AC) [15:57:48:335]: *** RunEngine:
*** Product: scheme48.msi
*** Action:
*** CommandLine:
Tobias Bengtsson wrote:
Which action evaluates which features to be installed?
CostFinalize
In my different features I use conditions to decide what to be
installed or not (Condition Level=1NAME = test/Condition,
installed If NAME=test), and depending on if the property gets set
with a
Jeelan Sheriff wrote:
I have an MSI, whose dependent files gets copied to %SystemDir%. If
these files are accidentally deleted by the user, I am having issues
while uninstalling the app. Is there a way for me to 'ignore' these
kind of errors during uninstall of the apps.
Depends on the
Xin Liu (Person Consulting) wrote:
We have a .msi file built from Wix toolset which calls one of the VS
SDK tool.
Please be more explicit. Which tool? As a custom action or a build-time
tool? Can you show a code fragment?
--
sig://boB
http://bobs.org
Saranath Aravamudhan wrote:
I read that permanent='yes' attribute in the Component tag makes the
component un-installable. I am facing the problem with one of the
components in our product when the permanent flag got included due to
the infamous copy and paste. I read that this sets a regKey
dave_c wrote:
Is there an easy way in Wix to delete this folder and the files contained in
it and if there is an example I'd appreciate it.
Take a look at RemoveFile and RemoveFolder.
--
sig://boB
http://bobs.org
-
Patrick, I'm looking at doing something very similar (albeit with Office
2003 for now). I'd be interested in what you find out, since I'm just
starting with WiX as well. If you want to detect Office 2007 though,
couldn't you just look at HKLM\Software\Microsoft\Office\12\ and see if
it exists?
Thanks Bob,
I've changed my code to
DirectoryRef Id='intface'
Directory Id='logs' Name='logs'
Component Id=logs Guid={6FA20250-4987-4196-8CEF-4EFFB7DB4683}
SharedDllRefCount=no KeyPath=no NeverOverwrite=no
Permanent=no Transitive=no
Win64=no Location=either
Chris,
You should look at the Creative Commons add-in:
http://blogs.msdn.com/robmen/archive/2006/06/20/641202.aspx
There is a tool in the wix toolset that allows you to generate wix XML out
of an existing MSI. With that, it might be easiest for you to
reverse-engineer the MSI of this add-in and
If you are an administrator and you install the MSI then it will elevate
when it goes to the InstallExecuteSequence (and work!) while the UI
sequence runs as standard user. If it's failing even though you are an
administrator then you are perhaps installing something from the UI
sequence. If this
Is there any documentation on the Wix NAnt tasks? In the assembly I can see
three tasks: LightTask, CandleTask and LitTask. But I can't find any docs
for them. I'm going to look at the source build files too see how they're
used (and I guess I could look directly at the task source). But docs are
Bob,
Thank you very much for that clarification.
Now that I have that error cleared-up, a new one appears when LIGHT is
running:
C:\...\TEST.msi : error LGHT0204 : ICE39: PID_WORDCOUNT value in Summary
Information Stream is not valid. Source image flags must be 0, 1, 2, or 3.
I've checked the
I'll try both. (I have tried to get an assignment agreement before but
never received a reply.)
Thanks
Neil
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 25 February 2007 18:21
To: Neil Sleightholm
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] WiX3 Error: The primary
Is there any documentation on the Wix NAnt tasks? In the assembly I can see
three tasks: LightTask, CandleTask and LitTask. But I can't find any docs
for them. I'm going to look at the source build files too see how they're
used (and I guess I could look directly at the task source). But docs are
Hi Everyone
I finally worked out why I was having issues uninstalling my patch and
thought I would share the solution in case others come across it. The
problem was the version of MsiMsp.exe and PatchWiz.dll that I was using
to create the patch - I was using Windows Installer 3.0 to install
I am attempting to create reusable Components that package up a few files,
etc., that are common to multiple installer packages. The windows
installer correctly uses reference counting to ensure that the elements of
my component get installed once and only once even (when I install multiple
MJW wrote:
Now that I have that error cleared-up, a new one appears when LIGHT is
running:
C:\...\TEST.msi : error LGHT0204 : ICE39: PID_WORDCOUNT value in
Summary Information Stream is not valid. Source image flags must be 0,
1, 2, or 3.
That doesn't seem right. The doc says that the
Emma Hanna wrote:
I finally worked out why I was having issues uninstalling my patch and
thought I would share the solution in case others come across it. The
problem was the version of MsiMsp.exe and PatchWiz.dll that I was
using to create the patch -- I was using Windows Installer 3.0 to
Stephen Walch wrote:
My problem occurs when I try to add CustomActions for registering and
deregistering my components. (If you must know, it involves making
STSADM.EXE calls to register a SharePoint Feature.) I have not
figured out a way to associate my CustomActions with specific
Emma Hanna wrote:
When I install then uninstall my app all registry keys created on
install are completely removed as expected. However if I apply a patch
to the install and then attempt to uninstall the original application,
the registry keys are left behind -- but everything else is
I want to set the following permissions on my folder:
read execute, list contents, read, write, modify.
How do I set these permissions? The Permission element has GenericAll which
gives full control. Setting both GenericRead=yes and GenericWrite=yes
gives read write permissions only, but
Thanks bob, I understand how to make them secure, but how do one make a
property public?
Regards,
Tobias
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: den 26 februari 2007 17:03
To: Tobias Bengtsson
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Propertys read in with
How to extract the registration information? I heard there are some tools which
can output a Wix include file containing the registration information. But
regit.exe doesn't provide that functionality.
Thanks,
Xin
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 27, 2007 11:31
35 matches
Mail list logo