I'm getting this error:
error LGHT0204: ICE61: Upgrade.VersionMax 7.0.32768.1 format is wrong
According to the doc, the Build component of version numbers can be up
to 65535. I think there's a signed/unsigned problem with the code
validating the VersionMax field. Devs agree? I'll log a bug if s
C++ in Visual Studio projects have a handy feature which allow you to
say Build This Project Only, which will cause the build dependencies be
skipped. This would save a lot of time with Wix projects using Votive,
when you are tweaking wix sources but not modifying anything else, and
really only wa
Are you using ServiceInstall? It should uninstall fine. There's a
strange issue that appears in some OS versions where if you have the
service control panel window open, the service will be locked and may
fail to uninstall, or require a reboot.
-Original Message-
From: MacDiarmid, James
Sounds like a dependency issue. Take a look at the event logs, are there
any WinSxS errors reported?
-Original Message-
From: Steven Chin [mailto:steven.c...@mathworks.com]
Sent: Friday, February 27, 2009 8:44 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] DLL failing to regi
Using iisext, I am able to attach my web application to a pre-existing
application pool. However, I can't seem to get it to leave the
application pool intact when the product is uninstalled. It removes it
regardless of whether the iis:WebAppPool element is in a component. Any
way to avoid this b
-
From: Jeremy Lew [mailto:j...@liquidmachines.com]
Sent: Monday, February 23, 2009 4:47 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Given an upgrade code,retrieve the installed
product code
Is there any relatively easy way to retrieve the product code of
Is there any relatively easy way to retrieve the product code of an
installed application, given its upgrade code?
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest
For clarification, let's say I don't know the SiteId, which is the
obvious answer to this.
-Original Message-----
From: Jeremy Lew [mailto:j...@liquidmachines.com]
Sent: Thursday, February 12, 2009 1:07 PM
To: General discussion for Windows Installer XML toolset.
Subject:
Does anyone know the minimal set of attributes which must be specified
on the iis:website/iis:webaddress directory to refer to a pre-existing
site? I don't want to create a new site or change the existing site in
any way.
Thanks,
Jeremy
---
redist for msvcrt.dll to install on
Windows 2000 and later because it is part of the OS. You don't
redistribute msvcrt.dll in the same way that you don't redistribute
kernel32.dl.
Phil Wilson
-Original Message-
From: Jeremy Lew [mailto:j...@liquidmachines.com]
Sent: Wed
Pull in the appropriate merge module similar to this:
C:\Program Files (x86)\Common Files\Merge
Modules\microsoft_vc90_CRT_x86.msm
This will install the CRT in the WinSxS directory so that it can coexist
with any existing version.
-Original Message-
From: Chad Petersen [mailto:chad.peter
discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Prevent 32 bit MSI install on 64 bit OS
I think a LaunchCondition with the property Msix64 will do what you
want.
-Ari
-Original Message-
From: Jeremy Lew [mailto:j...@liquidmachines.com]
Sent: Monday, January 26, 2009 2:49
Before I resort to a CA that tries to call IsWow64Process(), is there
any other simple way to bail out if attempting to run a 32 bit installer
on a Win64 OS? (My product requires the 64 bit installer on a 64 bit OS)
Thanks,
Jeremy
--
toolset.
Subject: Re: [WiX-users] InstallExecuteSequence in a fragment?
Jeremy Lew wrote:
> Problem is, the InstallSequence seems to be ignored. I'm guessing
that
> this is because it's not referenced in the Product element, which
lives
> in a different file. How can cause InstallS
Trying to be tidy, I pulled out the CustomAction declarations relating
to a particular aspect of my install into its own .wxs file.
I have
[...sequence the custom actions declared above]
Problem is, the InstallSequence seems to be ign
Do you have ConfigureIfExists="yes"?
-Original Message-
From: Yan Sklyarenko [mailto:y...@sitecore.net]
Sent: Wednesday, January 14, 2009 10:54 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] How to switch the Home Directory of a Default Web
Siteon instal
Sent: Tuesday, January 13, 2009 15:04
To: General discussion for Windows Installer XML toolset.
Subject: RE: Bug with Component/@Guid="*"?
Yes, bug. 64 bit folders aren't evaluated. Please open it against
"light" "v3.0".
-Original Message-
From: Jeremy Lew
I have a bunch of component/files rooted under ProgramFilesFolder64.
Using "*" for the Component's Guid gets me:
error LGHT0231: The component 'C__d8f4a26fe53142ebb42d1a9fdf527ac6' has
a key file with path 'TARGETDIR\lmdc
server\adminui\branchadmindisabled.aspx'. Since this path is not rooted
in
9 09:33
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Preventing reboot when unininstalling IIS app
Never seen that problem myself.
-Original Message-----
From: Jeremy Lew [mailto:j...@liquidmachines.com]
Sent: Monday, January 12, 2009 09:31
To: General disc
Using iis:WebApplication etc to install a couple of web apps. On
uninstall, the installer wants to reboot the system to unlock files
unless I issue a IIS reset first. Is there any way built into the iis
extension to do this, or do I need a custom action? If CA, where should
it be sequenced to ru
hrough custom action data, and that this is a bug.
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Thursday, January 08, 2009 1:26 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Privileged custom actions
Jeremy Lew wrote:
> T
Make sure you have specified both the User and Domain attributes. I
found that specifying the domain as part of the User attribute did not
work.
-Original Message-
From: Maruti Gouroji (Infosys Technologies Ltd)
[mailto:v-mag...@microsoft.com]
Sent: Friday, January 09, 2009 1:25 PM
To: G
PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Privileged custom actions
Jeremy Lew wrote:
> I hear you, but it doesn't look like I have much choice. If the
service
> fails to start, I need to either instruct the user to start it from
the
> contro
Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Wednesday, January 07, 2009 10:46 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] ServiceInstall fails due to CRT
Jeremy Lew wrote:
> Another question:
> I assume that if I were to deploy t
of your install.
-Original Message-----
From: Jeremy Lew [mailto:j...@liquidmachines.com]
Sent: Wednesday, January 07, 2009 10:04
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Privileged custom actions
Sorry, that was not entirely coherent. What I meant was, is it
Sorry, that was not entirely coherent. What I meant was, is it possible
for me to specify a manifest for the DTF process to force elevated
priveleges?
-Original Message-
From: Jeremy Lew [mailto:j...@liquidmachines.com]
Sent: Wednesday, January 07, 2009 12:56 PM
To: General discussion
In the thread titled "ServiceInstall Fails due to CRT", Bob mentions
that custom actions running after InstallFinalize will run in an
non-elevated context. I ran across this article on stackoverflow:
http://stackoverflow.com/questions/304353/mark-msi-so-it-has-to-be-run-a
s-elevated-administrator
Another question:
I assume that if I were to deploy the CRT locally instead of in WinSxS,
that would also solve the problem?
-Original Message-
From: Jeremy Lew [mailto:j...@liquidmachines.com]
Sent: Wednesday, January 07, 2009 9:42 AM
To: General discussion for Windows Installer XML
t for
real.
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Wednesday, December 31, 2008 1:36 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] ServiceInstall fails due to CRT
Jeremy Lew wrote:
> My installer is installing a .NET
My installer is installing a .NET service using ServiceInstall. The
ServiceInstall is failing to start the service, I'm pretty sure because
of a dependency on the C runtime library. The installer is installing
the CRT and policy merge modules, and the MergeRef for these is before
the reference to
ndows Installer XML toolset.
Subject: Re: [WiX-users] Repair mode condition
That seems to work...Need to do a little testing though...
Thank you very much...
Regards,
Surekha Vuchuru
-Original Message-
From: Jeremy Lew [mailto:j...@liquidmachines.com]
Sent: Tuesday, December 30, 2008 1:57
Maybe you want FailIfExists="no"? That would seem to make it a no-op on
repair, since you already have UpdateIfExists="no".
-Original Message-
From: Vuchuru, Surekha (SBT US EXT)
[mailto:surekha.vuchuru@siemens.com]
Sent: Tuesday, December 30, 2008 2:49 PM
To: General discussion for
ou probably have one), as I noted
before: there is no owner for heat today. It hasn't advanced since
Derek put the initial 3 months of dev effort into it. Lots of bugs and
feature requests sit idle against heat.
-Original Message-
From: Jeremy Lew [mailto:j...@liquidmachines.com]
S
ndows Installer XML toolset.
Subject: Re: [WiX-users] WIX 3 - Suggestions
Jeremy Lew wrote:
> Well, I was talking about the Id values not the Guid values. They
need
> to be unique as well, no? Or only within their directory?
>
Heat should already be generating unique (though *not *st
Installer XML toolset.
Subject: Re: [WiX-users] WIX 3 - Suggestions
You mean like the Directory/@ComponentGuidGenerationSeed?
-Original Message-
From: Jeremy Lew [mailto:j...@liquidmachines.com]
Sent: Monday, December 29, 2008 14:41
To: General discussion for Windows Installer XML toolset
file each... maybe. It's the closest we've
come. Still experimental (one reason it isn't documented well).
-Original Message-----
From: Jeremy Lew [mailto:j...@liquidmachines.com]
Sent: Monday, December 29, 2008 13:41
To: General discussion for Windows Installer XML toolset.
Sub
)
I am working on something like this at the moment, if I get it working
I'll post details.
Neil
-Original Message-----
From: Jeremy Lew [mailto:j...@liquidmachines.com]
Sent: 29 December 2008 20:36
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WIX
Can you elaborate on which of the component rules #2 presents problem
for? I wrote a tool to auto-gen my components from my web structure as
well. It puts every file in its own component with a new Guid for the
id. Is this approach problematic? Is it different than what Visual
Studio Installer d
localized wix projects.
Jeremy Lew wrote:
> When I added a Resources_en-US.wxl file to my Wix 3.0 wixproj, the msi
> is now being placed in a subdirectory of $(TargetPath) with the name
> "en-US". Fine, except the value of $(TargetPath) is the original
> subdirectory (one le
When I added a Resources_en-US.wxl file to my Wix 3.0 wixproj, the msi
is now being placed in a subdirectory of $(TargetPath) with the name
"en-US". Fine, except the value of $(TargetPath) is the original
subdirectory (one level up from en-us) and no .msi exists there. I have
a postbuild step whi
40 matches
Mail list logo
