I am building an msi to deploy a
website, when there is only the default web site under the IIS, it works.
But when there is already 2 websites under IIS, when I run the
msi, It return an error Failed to read IISWebs table and
the installation failed.
Any help on where I should look to
SourceForge.net offers a service like this; see
https://sourceforge.net/people/
Albert
-Oorspronkelijk bericht-
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Namens Stefan Krueger
[MVP]
Verzonden: vrijdag 23 juni 2006 18:06
Aan: wix-users@lists.sourceforge.net
Onderwerp: Re:
First I tried following:
CustomAction Id=MyEXECA Property=[SourceDir][REDIST_DIR]\my.exe
ExeCommand= Return=ignore /
And next following:
Property Id=PROP_MYEXE Value=[SourceDir][REDIST_DIR]\my.exe /
CustomAction Id=MyEXECA Property=PROP_MYEXE ExeCommand=
Return=ignore /
In both cases
WixCop produced the same
code as I tried, so the syntax is right. But Votive still says:
error
CNDL0200 : The Component element contains an unhandled extension element
'difx:Driver'. Please ensure that the extension for elements in the
You need to place WixDifxAppExtension.dll
and the difx wixlib file (I dont know its name) in the same directory
with candle, lit, light, etc Then when calling candle, you need to
provide ext WixDifxAppExtension on the command line. Im not
sure if this is possible from within Votive at this
Hi!
I downloaded votive2.msi (Votive-2.0.4221.0.zip)
and the file doesn't work. I get this error: "This installation package could
not be opened! Contact the application vendor to verify that this is a valid
Windows Installer package".
Using Tomcat but need to do more? Need to support web
Try changing:
WebAddress Id='DefaultWebSiteAddress' Port='81' Secure='no'/
To:
WebAddress Id='DefaultWebSiteAddress' Port='nn' Secure='no'/
**Where 'nn' represents another Port Number that may not be used on your web
server
like 82**
If this fixes your problem, I will guess that you install
Sorry about that, the file somehow gotten corrupt. It should be fixed now.
Van: [EMAIL PROTECTED] namens Florin Adrian RaduVerzonden: ma 26/06/2006 13:39Aan: wix-users@lists.sourceforge.netOnderwerp: [WiX-users] [Wix-users] Votive 2.0.4221.0 doesn't work
Hi!
I downloaded votive2.msi
Hello all,
I am currently trying to get some extended stored procedures registered in
SQL.I did not found any samples for this. So maybe my code can be of any
help in the tutorial ;-)
Altough, I'm having some problems with extended stored procedures for
SQL.
I use the following piece of
Ok, but then I still cannot point to my main exefile for the version?
So what I should do in my nightly build is generate a file with the
version and buildnumer in it (like MyVersion.wxi) in which the version
and buildnumbers are defined.
This file I can then add tou my wxs file and done..
IMHO
I am trying to add new files to my WiX project inside of Visual Studio
2003 and it does not work. I have installed version 2.0.4221.0. So do I
anything wrong or it is a failure.
I can create create new projects and have no problems. The first .wxs
file will be created but adding more does not
Hello, I am just newbie in the word of MSI and WiX. Could you help me and say
what I am doing wrong way?
I'm interested in MSI Upgrade mode (not patch, only upgrade). I have built
sample SampleUpgrade got from Gábor DEÁK JAHN's Tutorial
(http://www.tramontana.co.hu/wix/lesson4.php). But I am
Unfortunately, extensions arent supported in Votive right now,
so youll have to build via the command line.
Justin
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Derek
Cicerone
Sent: Monday, June 26, 2006 4:00 AM
To: 'Harrborg Richard'; 'Bob Arnson'
Cc:
Adding the following element to a component causes the generated MSI to
throw error 2727:
Registry Root=HKCR Key=CLSID\{2ED33534-3318-4CE9-9D3D-40E5F7E930F5}
Value=USBPort Class Type=string /
I see the following in the log:
DEBUG: Error 2727: The directory entry 'WindowsFolder' does not exist
All Directory elements must be rooted in TARGETDIR/SourceDir.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Monday, June 26, 2006 12:05 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Registry element causes error
This is a common authoring mistake which is caught by MSI validation - be
sure to run validation on all your MSI files.
Derek
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Monday, June 26, 2006 12:30 PM
To:
Young,
I notice the Port number is 81. Are you trying to create a web site,
or are you expecting to install to an existing web site. I have seen this
error when I am expecting an existing web site to be there, and the installer
can't match either the port number or the ip address. Is
Hello,
When doing the uninstall how is the property [D4WSQLSERVER] resolved, it
could be that this has no value set and hence the installer can't locate the
database server when uninstalling.
Also its trying to uninstall the master database because its part of a
component. Try putting
Hi guys,
This is more of a general Windows Installer issue
than a WiX issue, butI thought I'd solicit the feedback of the list as
many of you will certainly have useful opinions.
Essentially, last year when I was still quite
newwith WiX and WI,I built an installer that really really should
Joe,
Have a look at the MSI Automation interface - through the ProductState
property of the Installer object you can find out the installed state of an
MSI- including that it is installed for the current or a different
user. At least it might show where the install is. The WMI interface
I am trying to create a new web
site , the port is 81, and the port is not used by other web sites.
Thanks
Young
From: Michael Osmond
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 27, 2006 5:53 AM
To: Young Yang (Worksoft);
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
22 matches
Mail list logo