Hi,
I have a question regarding the proper use of the ProgId element under
a TypeLib/Class element (COM Registration) and specifically related to
version-independent and version-dependent ProgId's.
I've previously had my definition like:
...
But for some
Regarding the ability to "search for" and include a source file during wix
compilation/link I've
proposed to extend the WiX preprocessor with a FileExist functionality.
For details see "[1932721] Using FileExist() in preprocessor condition
statements" available at
http://sourceforge.net/tracker/
Hi Arun,
I've been experiencing the same kind of problems and I posted a question about
it recently. See
the
http://n2.nabble.com/Heat-problem-harvesting-class-from-type-library-td1303554.html
I believe the problem is that for executables (.exe out-of-process COM Servers)
the WiX heat tool
can
Hi,
I have a problem harvesting a type-library from an executable
file (a COM Server) with heat.exe, version 3.0.4513.
If I run heat (as normal-user in Vista) I get something a la:
...
But it does
Hi,
As far as I've understood, and irrespectively of your port issue, a WebSite
element under a
Component element will always create a WebSite (even if it is the "Default Web
Site") and thus
also remove it on uninstall. You THINCTRAX_PORT <> 80 sniffet should not
include a WebSite element
but r
Hi, just want to follow up on my own post.
Parts of the problem can now be handled. I'm still interesting in learning how
to resolve the
remaining parts.
Okay, so here's what I've learned (all relevant for WiX 3.0 at least up to
3.0.4401.0):
* IIS comes with a default web site. Installing IIS
Yes, I did receive the ICE69 warning - and with these responses the cause is
now explained. I have
too resolved it by using the "[DIR]filename" method and will remember in the
future to take ekstra
care about using the "[#fileid]" reference method.
Thanks again,
/Michael
---
Thanks for the clarifications.
As cemiles suggest I've
changed the code to exactly that of using "[DIR]filename"
It just show that you cannot headlessly be sure that
"[#fileid]" references always work across your components and
wix source files. Now you'll have to think (we hate that, right?)
Am I correct to assume that using [#fileid] syntax to refer to a file
does not work if that files' component is marked with
Permanent="yes" and/or NeverOverwrite="yes"?
I.e. it will only be correctly evaluated if the installer actually
"processes", e.g. installs, the file.
Example:
...
In Wix 3.0 we have both the XmlConfig and XmlFile elements.
I'm not totally clear about what is the difference between XmlConfig
and XmlFile. Can somebody explain? Why do we have two different elements
that seemingly can do the same (or can they)?
Accordingly to Bob Arnson [see
http://n2.nab
I want to create an install-experience which should support the
following:
* If the install-user selects a particular feature for install, that
feature should install a new virtual directory in the default IIS web
site.
* If IIS is not installed the install should not fail if the user
haven't
Hi,
Is it possible to create a new (text) file during the
install?
In my case I want to create an xml file (configuration
file like) which contains a few elements with values from some WiX
defines, e.g. if the following could be expressed:
$(var.CompanyName)
or
Hi,
I have problem with WiX in where I want to include a file into the
setup
only if that file exist. The problem can be illustrated by the
following
WiX-like snippet:
That is, only if the Spanish user guide (pdf) file exist (it may not
be
available due to t
Hi,
Does anybody have a good working example of using the iis:WebDir
element?
I'm using WiX 3.0.3907.0 with the following illustrated example:
But it does not work as expected. I would expect that a "C:\Inetpup\wwwr
14 matches
Mail list logo