Thanks for all the replies.
My problem is that our tool is calling the WiX compiler, binder and linker
directly, without light.exe - light.exe is 32-bit only, probably because
winterop.dll (interop to Windows CabBuilder) is 32-bit only. Now calling the
WiX binder directly from our 64-bit tool,
I got it working. I compiled winterop.dll as 64-bit.
Back on Route 64...
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
-Original Message-
From: Sebastian Brand (Instyler Software) [mailto:wix+us...@instyler.com]
Sent:
Hi,
I am using C# in VS2008 to access an MSI and delete some rows. I am
using the latest weekly WIX build, 3.5.0626. When I try to use the
View.Delete method I receive the InstallerException Cursor in invalid
state. I've simplified the code and replicated the error with the
sample below:
You have a boolean operator right in that very example... I'm just winging
this, but try:
Condition Message=Required prerequisite (PowerShell 1.0) is not found.
![CDATA[Installed OR ((POWERSHELL = 1.0) And (MYFLAG))]]
/Condition
On Wed, Jul 1, 2009 at 12:21 AM, sandun css sandun...@gmail.com
I am trying to create an MSI which will install a windows service multiple
times on the same machine with a clientname appended to the end of each
service instance (ServiceNameClientA). I take the servicename as input from
the user and create the service with that name(e.g clientname). It will
I am trying to create an MSI which will install a windows service multiple
times on the same machine with a clientname appended to the end of each
service instance (ServiceNameClientA). I take the servicename as input from
the user and create the service with that name(e.g clientname). It will
From memory so this may not be 100% - Windows Installer evaluates
properties as true if they are set, and false if they are not. i.e.
setting MYFLAG=true on the command line will result in boolean condition
tests on MYFLAG returning true, but so will setting MYFLAG=false, as the
MYFLAG property
Hi all,
I have a question about setting permissions on SYSTEM temp environment
directory:
If I will read information from registry about location of SYSTEM TEMP,
how can I use it to set permissions?
Should I write custom actions to do that? Can I reuse PermissionEx
element from Util extensions?
I already figured out, I need to specify Directory element and not
DirectoryRef element, which I tried before.
If somebody interested, there is code to do that:
Property Id=SYSTEM_TEMP_FOLDER
RegistrySearch Id=SystemTempFolder
Key=SYSTEM\CurrentControlSet\Control\Session
All,
I have a couple third-party installers, such as the SOAP toolkit, I need
to kick off during my installer. This file does not get installed with
the rest of the application. How would I go about setting that up?
Thanks,
Jim
Note that if you set permissions to a folder with PermissionEx element,
the permissions are set recursively for all descendants. This means if
your TEMP folder exists and is full of folders/files, the installation
time will increase...
-- Yan
-Original Message-
From: Igor Paniushkin
I assume you have some nifty tool to do this?
I like the style of the CHM documentation very much, so I would like to
create my own CHMs from XSDs in this way...
Thanks
--
View this message in context:
We are getting the following error and are not sure why. We have been
successful at creating virtual directories in several other environments
(development, integration, etc.), however the environment we are currently
deploying to is having issues :(
Action 14:41:11: StartMetabaseTransaction.
A *lot* has changed in the IIS custom actions since WiX v3.0.4805, including an
error that looks very similar to this. First, I would upgrade to the latest WiX
3.0 build (v3.0.5419) and see if you still have a problem after that.
Thanks,
Mike Carlson
-Original Message-
From: troy
That's correct - they're uncomfortably like some C /C++ types, to use that as
an approximate analogy. People trip over this sometimes with the standard
properties. For example the Installed property isn't set to true or false. It's
a string which (IIRC) is a date.
Phil Wilson
-Original
Mike -
Installed version 3.0.5419, built msi, and am now getting this error during
install:
Action 18:36:40: StartMetabaseTransaction. Starting IIS Metabase Transaction
Action 18:36:40: RollbackMetabaseTransaction. Rolling back IIS Metabase
Transaction
Action 18:36:40: CommitMetabaseTransaction.
I have an interop assembly that breaks my patching.
When patch is installed verbose log shows this:
MSI (s) (78:E8) [16:12:06:987]: Baseline: INTEROP.SERVICELIB.DLL not touched in
this transaction, verification required.
MSI (s) (78:E8) [16:12:06:989]: Baseline: Existing INTEROP.SERVICELIB.DLL
Think of boolean properties acting the same way that properties act
when you connect them to a checkbox. The property is empty if the
checkbox is cleared and set to some value when the checkbox is
checked.
If you follow this convention with your own properties then MyProperty
will evaluate to
FWIW .. I passed in the IP address of the existing web site .. the new WiX
looks like:
iis:WebSite Id=WS__kCTools.WebServices
Description=[kCTools.WebServices.WebSite]
iis:WebAddress Id=WA__kCTools.AllUnassigned
Port=[kCTools.WebServices.Port] Header=[kCTools.WebServices.Header] IP=
For what it's worth, Chris Jackson was able to reproduce this problem,
and confirmed that it is a bug in Windows 7. The fix won't make it into
the RTM but should be in a Windows Update coming soon.
--Quinton
-Original Message-
From: Quinton Tormanen [mailto:quint...@deltacompsys.com]
Does your website have a component associated with it?
The log sounds as though you're using a website locator record (which is simply
a website with no associated component), and the website it's trying to locate
on the machine doesn't exist (in which case the install is intended to fail).
If
No .. it does not have an associated component. The website does exist on
the server. Here's what we have in the IIS metabase file .. so it does
exist:
IIsWebServerLocation =/LM/W3SVC/1438500861
AuthFlags=0
LogExtFileFlags=LogExtFileDate | LogExtFileTime |
LogExtFileClientIp
Thanks for the replies. I was able to get it done with 'MYFLAG~=true'
approach.
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
Hi,
I set few env variables from my msi. But they don't get deleted when I
uninstall them. This is my code,
Environment Id='ENVVAR' Name='CONFIG' Action='set' Part='all'
Value='[INSTALLDIR]etc\middleware.cfg' System='yes' Permanent='no'/
What can be the problem?
Thanks,
Sandun
24 matches
Mail list logo
