I am trying to allow users to select which WebSite they wish to install a
virtual directory under. I have used the method describe here which gives me
the list however the virtual directory is still installed under the default
web site since the port of the Web Address is the same. This is my
decl
I am also interested in moving to WiX v3 from v2. I already have a wixproj
file I am maintaining for SharpDevelop and would like to move this into
Visual Studio. The only thing I am cautious of is that I will need to do
patch creation and on http://wix.sourceforge.net/faq.html it has What's New
in
SFP is a WinMe feature that no one every used (you are the first person to ever
ask about it). I don't think we'll bother with it unless someone actually has
a scenario where it is used... which seems unlikely since WinMe isn't even a
supported platform any longer (thank goodness).
-Origin
Just trying to add visual support for those elements at WiXAware 1.1,
but I'll take it out from the release until is working, since it seems
to not be needed by now.
K-ballo.-
Rob Mensching escribió:
> Yes, SFP support doesn't work. What are you trying to use it for?
>
> -Original Message-
Actually, for us, we use a common settings file at the top of the file.
In the settings file, we have . This element can be
overridden in each project file.
If you go to the property pages for a wix project, there is a button on the
compiler tab for Advanced Properties, or something like that
Hello,
I'm getting the following warning when trying to compile my module,
using Wix3.0
ICE03: String overflow (greater than length permitted in column);
Table: File, Column: File, Key(s):
Maybe.the.name.for.this.file.is.too.long.dll.F69460F1_7FD1_421A_9422_D6FFD3AB741C
Is there a
You must use two different command lines to install this. One for an upgrade,
which you referenced earlier with REINSTALL and REINSTALLMODE and another
without them for a new install.
http://msdn2.microsoft.com/en-us/library/aa371182.aspx says
v
Use to run from the source package and re-cache
You can edit that property () in the property pages if
you're using Votive. Just right mouse click the project in Solution Explorer
and click "Properties." Alternatively, you can edit the .wixproj file
directly and add Name=Value;Name2=Value2
within an existing . Make sense?
Justin
From: [E
Using self registration in an installer is not recommended. See the
remarks for the SelfReg table.
http://msdn2.microsoft.com/en-gb/library/aa371608.aspx
You can instead use tallow to extract the registry keys that are
installed by SelfReg and add those registry keys to your installer.
-Brian Sim
No I have same product ID and same upgrade code for package. I just want to
change the version and my features are not going to change too.
I think it means minor upgrade so questions are:
1- I found this about Upgrade table
http://msdn2.microsoft.com/en-us/library/aa372379.aspx it says
On Sun, 4 Feb 2007 11:57:23 -0800 (PST), Mike Robertson wrote:
Mike,
> The list of Wix localizations has a fairly large number that are
> listed as complete
> and that presumably should then be available with the Wix project
> files. But they
> don't seem to be there, only English, Dutch, German
I am trying to install a web app and I want to let the user select the Identity
that the App Pool uses. They should be able to select between Network Service
and a domain account that they provide. The problem that I am running into is
when I try to use a property in the Identity parameter of
Sorry I'm kind of new to this. Is that the msbuild file for the
specific project correct? Is there a way to edit that in VS/TFS?
From: Cullen Waters [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 07, 2007 1:01 PM
To: Scott Sam; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Wi
Yes, SFP support doesn't work. What are you trying to use it for?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Agustín Bergé
Sent: Wednesday, February 07, 2007 10:10 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] SFP elements
I'm trying t
I'm trying to use a SFPCatalog element, but when setting the
src/SourceFile member the following error appears:
Error[CNDL0104]: Support for binary column types are not-yet-implemented
in WiX toolset: WiX element 'SFPCatalog'; WiX attribute 'src'; MSI table
'SFPCatalog'; column 'Catalog'.
Does th
What I did was set a property called in my MSBuild file.
Then, when candle is executed, the WixTasks convert that semicolon separated
list of variables into -d= when passed into the candle command
line. The only thing you might have to do is change the env. prefix to var.,
if nant was settin
Bob Arnson wrote:
>
> You're going to run into problems: Component rules say that you
> shouldn't have two of them writing the same key (even with a different
> value). The easiest solution is to create a third component that
> writes a property value, then use A and B feature action states to s
follow this item:
http://sourceforge.net/tracker/index.php?func=detail&aid=1585281&group_id=105970&atid=642717
..and until that is fixed, you can probably define the variables yourself
appropriately..
Quote Justin:
As far as Votive is concerned, you can define the preprocessor variable by
ent
Thanks, I've gotten the wxs files updated, and added them to the
projects in TFS. How do you handle the source path for the files being
added to the msi? Before I used a nant variable in the wix as part of
the path. Is there a similar way to do this using MSBuild? It looks
like the path will ch
On 2/7/07, Bob Arnson <[EMAIL PROTECTED]> wrote:
> Johan Appelgren wrote:
> > A possible cause for this is that the ReinstallMode is set to 'ecmus'
> > VerifyReadyDlg. If I interpret the documentation correctly 'e' means
> > to always repair files. So even if the file isn't missing or broken it
> >
I have some windows scripting files to add as part of my install. Up until
now I have manually been seleing the "Register" option from within windows
explorer and then "Unregister" when software is removed.
I'd like to automate this in the installer so how do I call regsvr32 from
with the install
Sorry another question then is where I can download the latest full SDK from?
Dave Cory
P Please consider the environment - do you really need to print this email?
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 07 February 2007 16:31
To: [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
The version of candle and light being used is 2.0.4820.0
But the version of MSIMSP being used is 3.1.4000.1830
I presume I should be using the same throughout.
They're not tied. MSIMSP is in the Windows SDK and it makes sense to get
the latest version for a
Sorry Bob,
I will remember that in future, I'm wondering if you have hit the nail on the
head with your response.
The version of candle and light being used is 2.0.4820.0
But the version of MSIMSP being used is 3.1.4000.1830
I presume I should be using the same throughout.
Rega
Dana Gutride wrote:
From the msdn documentation (and this is my guess as to why the WiX
team choose this course of requiring the components also be marked as
64-bit).
http://msdn2.microsoft.com/en-us/library/aa368007.aspx
Set this bit to mark this as a 64-bit component. This attribute
facilita
Robert Randall wrote:
Can I simply use two packages -- one for 64bit and one for 32bit?
Would that solve the problem without having to use conditions in
components?
Yes. And you can share your WiX authoring between them, using
preprocessor variables, for example, to set the components'
Johan Appelgren wrote:
> A possible cause for this is that the ReinstallMode is set to 'ecmus'
> VerifyReadyDlg. If I interpret the documentation correctly 'e' means
> to always repair files. So even if the file isn't missing or broken it
> is repaired.
>
> Shouldn't 'ocmus' be enough? 'o' to repai
Please keep /wix-users/ on the thread so everyone can participate.
[EMAIL PROTECTED] wrote:
I'm currently working on this so in order to understand the problem a
little bit more I downloaded the samplePatch code from the Wix Demo.
When I build the patch I get the error
"Failed to create
Alexander wrote:
Could you please kindly show me an example how to do that?
Take a look at the src/Setup/Votive.wxs in WiX v3. It uses properties
like VS2005_ITEMTEMPLATES_DIR in its directory hierarchy.
--
sig://boB
http://bobs.org
--
If a component contains items that need to be in those 64-bit locations,
than they need to be marked as such in the component tag (Win64="yes"). It
seems that all components are 32-bit by default (even in a 64-bit package).
You might want to mock up a few quick installers to see this behaviour so
Can I simply use two packages - one for 64bit and one for 32bit?
Would that solve the problem without having to use conditions in components?
It feels like most folks are ignoring Itanium ;-)
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 06, 2007 10:57 PM
To: Ro
Hi,
I've run into a minor issue when repairing an install built with wix
3.0.2420.0.
I'm using Microsoft_VC80_CRT_x86.msm and if I repair
C:\WINDOWS\winsxs\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b128700\msvcr80.dll
is reported as in use. This causes a reboot prompt at the en
Thanks for your answers, I'm almost there, I think...
> There will be a hierarchy that will
> be setup toward the bottom of your wxs file that you can modify to have the
> right TARGETDIR that you want.
The wxs file is auto generated, so can you elaborate how I change the
targetdir without modif
Hi,
I have a COM+ installation (built with Wix 2.0.4820.0) that works on W2K Pro
machines but not on any servers. I tested the install on 3 clean W2K clients
but when it comes to any server install (W2K or W2K3 SP1) I get the following
error:
MSI (s) (24:FC) [10:12:17:137]: Invoking remote
...only if your CA is scheduled after InstallValidate, so pay attention to that.
Dacian
- Original Message
From: "Wilson, Phil" <[EMAIL PROTECTED]>
To: wix-users@lists.sourceforge.net
Sent: Tuesday, February 6, 2007 6:24:24 PM
Subject: Re: [WiX-users] Custom Action to run only on uninst
35 matches
Mail list logo
