I'm trying to get my IIS site to only listen on the IP address that I'm
providing. When I use the following snippet of WiX code, though, I get two
addresses in the IIS site properties, and the one that is selected for it to
listen on is 'All Unassigned'. How do I replace All Unassigned with
Create a bootstrapper. Check out msdn documentation on the msbuild
GenerateBootstrapper task.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gareth at Serif
Sent: Thursday, March 29, 2007 10:23 AM
To: wix-users@lists.sourceforge.net
Subject: Re:
I have a bunch of one-file installers (one .wxs file per installer, many
installers).
Can I run candle once, with *.wxs, then run light separately on each wixobj?
Will there be any problems doing this?
Cullen Waters
SDET
Microsoft Office Live
Thanks, Rob
From: Rob Mensching
Sent: Tuesday, March 20, 2007 3:31 PM
To: Rob Mensching; Cullen Waters; WiX-users@lists.sourceforge.net
Subject: RE: Re: [WiX-users] multiple file compilation
Sorry, that's terribly ambiguous.
Yes, you can run candle once with all the .wxs files then link many
' directory,
that path is invalid when the wixlib is compiled.
From: Rob Mensching
Sent: Tuesday, February 13, 2007 10:26 AM
To: Cullen Waters; WiX-users@lists.sourceforge.net
Subject: RE: [WiX-users] ?Bug? in linker
No, .wixlibs are designed to be portable. There was actually a bug a long time
We've found a workaround for now, so it's not a critical issue for us, but
something that probably should be fixed.
From: Rob Mensching
Sent: Tuesday, February 13, 2007 10:37 AM
To: Cullen Waters; WiX-users@lists.sourceforge.net
Subject: RE: [WiX-users] ?Bug? in linker
That sounds like the bug
When I did this, I still got the ugly folders.
From: Justin Rockwood [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 08, 2007 12:51 PM
To: Cullen Waters; Justin Rockwood; 'Mark Capaldi';
WiX-users@lists.sourceforge.net
Subject: RE: [WiX-users] Votive - Adding File as a Link
Another thing you
If you edit the project file directly, you can do this.
In the
ItemGroup
Compile Include=my file.wxs /
/ItemGroup
Section, just add another entry like this:
Compile Include=PathToFileMySecondFIle.wxs/
Now, there is a catch. When you reload the project in VS, it's going to be
to var.,
if nant was setting an environment variable for you.
From: Scott Sam [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 07, 2007 8:58 AM
To: Cullen Waters; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Wix 3.0 and Votive?
Thanks, I've gotten the wxs files updated, and added them
explorer, right click again, and select Edit
MyProj.wixproj. It will open in the VS main window, with the XML editor open.
From: Scott Sam [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 07, 2007 11:00 AM
To: Cullen Waters; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Wix 3.0 and Votive
I just moved my whole team from v2 to v3.
In general, the update went really smoothly. You can use wixcop.exe to update
all of the xml for you. Wixcop doesn't, however remove shortnames, which might
cause you some headaches. I went through all my xml and manually deleted all
the short
Two answers:
1) use quot; in your xml, that should evauluate to at runtime.
4)you have to put in ICE64, not just 64. If you look at the build output,
you can see the command lines that get generated for light and candle. If you
look there, you'll see that the ICE you put in that field is
Heat replaced tallow in v3.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan Hoeger
Sent: Thursday, January 04, 2007 1:14 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] What happened to Tallow.exe
I'm having trouble with this on Vista so I thought I would download
The biggest difference, and the reason you're seeing the errors now when you
didn't before, is that wix 3 runs ICE validation on the MSI that is created by
light, while wix 2 didn't. Most likely, if you run ice validation on the msi
you created with wix 2, you'll see the same errors. You just
in your MSIs all along, but
which you didn't know about, because v2 didn't run validation.
Hopefully, someone else can help you with the custom dialogs.
From: Levi Wilson [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 21, 2006 1:25 PM
To: Cullen Waters
Subject: Re: [WiX-users] ICE20 with WiX
The build of v2 we were using was really old, and this code worked on that
build. Was there a known regression in the code from v2 to v3?
From: Rob Mensching
Sent: Thursday, December 21, 2006 2:51 PM
To: Cullen Waters; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] IIS CustomAction
, 2006 7:14 PM
To: Cullen Waters; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Comparing two MSIs
There's a script in the MSI SDK called WiDiffDb.vbs, I use it on occasion to do
this.
Michael
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
custom
actions before LaunchConditions, and then verify that the CAs worked properly
in LaunchConditions.
Because the InstallUISequence is being created, and populated with the default
actions, LaunchConditions is being called before my CAs have a chance to run,
and my install is failing.
Cullen
[FullPathToFile]WixUtilExtension.dll.
From: David Errick
Sent: Thursday, December 07, 2006 7:39 AM
To: Cullen Waters
Subject: error CNDL0036: Could not find extension
Dear Cullen,
Is the WixUtilExtension.dll the extension specified in the -ext
WixUtilExtension? If build from a different folder does
. The extension source is at wix/src/ext/
-Original Message-
From: Brent B. Powers [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 07, 2006 10:15 AM
To: Cullen Waters
Subject: Re: [WiX-users] error CNDL0036: Could not find extension
Cullen Waters wrote:
If you installed wix using the wixv3 msi
If you make your project use multiple .wxs files, rather than a single .wxs
with a bunch of .wxi (which all get added in to the main file), then candle
should seem faster, and the processing would show as spikes, rather than
constant usage.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Chris,
From the snippet you posted below, it looks like you're trying
to, at install time, choose what file gets included in the MSI. That doesn't
work. You have to author the MSI (call this build time) before you can try to
install it. At build time, you have to supply all
Is there a tool out there to compare two MSIs? I'm moving our MSIs to wixv3,
and I want to verify that the built MSIs are the same as previously.
Cullen Waters
SDET
Office Live
+1 425 706 6809
x 66809
-
Take Surveys. Earn
A lot of our installers are pretty complex, and use a bunch of tables. I was
hoping for something more automated.
From: Peterson, Joel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 06, 2006 3:36 PM
To: Cullen Waters; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Comparing two
Having the cert stuff moved to the util extension would be great for my team.
We had to write our own CA for cert work.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joe Kaplan
Sent: Tuesday, December 05, 2006 8:54 AM
To:
that IIsWebApplication.2 is a localizable string
with length 255, but the RegisterIIsSSLCertificate.ApplicationName_ column is a
non-localizable string with length 255.
Has anyone else seen this error? Is it possible I'm doing something wrong in
my wix code to cause this?
Cullen Waters
SDET
Office Live
? Should I just suppress
the ICE32 error?
Cullen Waters
SDET
Office Live
+1 425 706 6809
x 66809
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
In v3, you have to call candle with -ext WixUtilExtension to use elements from
that namespace. Same with light.
And, to help you abit, when you call light, you have to specify what cultures
to use (like -cultures:en-us)
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David
You have to include cultures:en-us (or whatever culture your installer is for)
on the light command line, in wix v3.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rennie Sawade
(Volt)
Sent: Monday, December 04, 2006 5:19 PM
To: wix-users@lists.sourceforge.net
Subject:
In my app, we are using a couple of CustomTable elements.
The data in one of my columns includes a colon in the string. It looks like
Light uses a colon to delimit the column names and values in the CustomRow
element in the .wixobj file.
Does anyone have any suggestions on how to include the
That error is thrown when an included file uses a prefix that is not declared
in the parent file.
I'm adding code to properly identify and report the error; it should be in the
next release after Monday.
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of
to the error message for this error, and
note that it is caused by malformed XML, rather than a .NET 1.1 SP1 bugfix.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cullen Waters
Sent: Wednesday, November 22, 2006 3:05 PM
To: [EMAIL PROTECTED]; Wix-Users
? This looks like
a possible Wix bug to me.
From: Justin Rockwood [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 21, 2006 10:59 AM
To: Cullen Waters; 'Wix Group'
Subject: RE: [WiX-users] Another strange error message
I may be wrong, but I seem to remember that Win2003 only comes with .NET
Check the CustomTable element
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brandon Tyler
Sent: Friday, November 10, 2006 1:36 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Creating and populating your own MSI table in WIX
I have a custom
The VisualStudio extension should have all the checks you need
for every version of the framework that has been shipped.
Did you check out those elements first?
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Wilson,
Phil
Sent: Wednesday, November 01, 2006 1:13 PM
My suggestion is to use a single script for the initial
installation. Any upgrades or patches, or subsequent versions should be broken
up.
On first installation, when you are creating the db, you can be
reasonably certain through testing that your script will succeed. On any
successive
Ive seen the same behavior with one of our installers.
I think this is a bug in the implementation.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Muzammil
Ahmed
Sent: Friday, October 13, 2006 2:57 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users]
it and declaring the SectionHandler to use with it)
David Adams
MSN MessengerID: [EMAIL PROTECTED]
From: Douglas Watts [EMAIL PROTECTED]
To: Cullen Waters
[EMAIL PROTECTED],wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] WiX XML Issue
Date: Wed, 11 Oct 2006 14:36:25 -0400
MIME-Version: 1.0
and rollback
and uninstall from vbscript is pretty hard. It's a lot easier from a managed
CA.
-Original Message-
From: Douglas Watts [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 11, 2006 1:25 PM
To: Cullen Waters; david adams; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] WiX
Message-
From: John Vottero [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 11, 2006 2:43 PM
To: Cullen Waters; david adams; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] WiX XML Issue
Also, since the machines you're installing on have the .net
runtime installed (or else
My first thought would be to create a third feature, which the
user has to install, which then does the modification of machine.config.
Then, you could put your xml modification in a new component, which gets
installed with the must install feature.
From:
[EMAIL PROTECTED]
If you downloaded the v3, youll also have an exe called wixcop
in the distribution. Run wixcop on your existing v2 .wxs files, and it will
automagically update them to the latest schema.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Friday,
The way we do it is using environment variables. Our build
process sets an environment variable for build type(called BuildType), then we
reference that in wix using $(env.BuildType)
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ed Abshire
Sent: Monday, September 25,
will be set.
That should also take care of your TFS build. Im not certain about the TFS
build, though, since I havent ever used that.
From: Ed Abshire
[mailto:[EMAIL PROTECTED]
Sent: Monday, September 25, 2006 1:04 PM
To: Cullen Waters; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] WiX3.0
Is there any demand for a built-in Wix custom action to
install/upgrade/repair /remove Sql Reporting Services reports? Please let me
know if this is something youd be interested in.
Cullen Waters
SDET
Office Live
+1 425 706 6809
x 66809
Here is a list the wix devs sent me a while back, when I asked the same
question:
• Improved standard UI library with much strong customization story
• Wixlibs, binary wixlibs
• Overridable sequencing
• Standard UI support
• Support for arbitrary binary columns
•
C# express doesnt support the same add-in model as the paid
versions of VS. Im pretty sure that Votive will not work on C# express.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ali-Akber
Saifee
Sent: Tuesday, September 12, 2006 9:56 AM
To:
47 matches
Mail list logo
