"Sigurd Stenersen" <[EMAIL PROTECTED]> wrote
> I'm trying to create a rather simple installer (it should just install two
> files, but I want to customize the GUI), and I keep getting one error
> message :
>light.exe : error LGHT0100 : File of type 'Bina
I'm trying to create a rather simple installer (it should just install two
files, but I want to customize the GUI), and I keep getting one error
message :
light.exe : error LGHT0100 : File of type 'Binary' with name 'wixca.dll'
could not be found.
That dll is installed in the Wix install fo
nder the Feature element work just
> as well?
>
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Sigurd
> Stenersen
> Sent: Thursday, March 08, 2007 5:29 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] property in a conditional statem
"Divya Abrol (Aditi)" <[EMAIL PROTECTED]> wrote
>Is there any way I can use this property as a conditional statement in wix
>to install a feature something like below?
>
>
>
The preprocessor directives are evaluated when you compile the .wxs file,
while the properties are set w
"balakrishna" <[EMAIL PROTECTED]> skrev
>I have created MSI Package using Visual Studio 2005 (Using Setup &
> Deployment),
>But it supports only one language, Now i want a
>Single MSI Package which supports other languages
http://www.tramontana.co.hu/wix/lesson9.php
Sigurd
"Tobias Bengtsson" <[EMAIL PROTECTED]> skrev
>how do one make a property public?
Use uppercase letters for the property name.
Sigurd
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay p
Is it possible to assign a value to a property based on the value of some
other property ?
E.g. something like
if ALLUSERS='2' then Root='HKLM' else Root='HKCU'
And/or do condition tags work with properties ?
Sigurd
It's not entirely clear to me in which order properties are assigned values.
For instance, a property might be assigned a value by default, by
declaration, by command line, by registry search and so on. All but one
method will have to override some of the others by assignment order.
(E.g. ALLU
Is there any difference between 1.0.0 and 1.00.00 ?
How about the sorting of 1.1.0, 1.01.0, 1.10.0, 1.9.0 ?
Sigurd
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with
Jonas Jonsson L (AL/EAB) wrote:
> Not
> Installed
But that's even later - the "Not Installed" part quits working much earlier.
I don't mind doing the actual action later, in fact I already moved it to
After='InstallFinalize', but there must be a way to tell if the product is
being installed at
I'm using a custom action that accesses the INSTALLDIR directory, and thus
it must run after the directory is created. I do it like this :
This works fine, except it runs on uninstall as well. So I try :
NOT Installed
Now, that does NOT work, and I suspect it may be because [Installed
John Ludlow wrote:
>>> I ported your code to C++ and it does indeed work.
>>>
>>> That is, it hides features. It doesn't seem to work for features
>>> with "children", but I can live with that. Thanks a lot for
>>> sharing.
>>
>>
>> Hmmm, interesting. I assumed that this would work recursively b
John Ludlow wrote:
>> Another option is to use a custom action - that's what this vbscript
>> code does:
>>
>> Set installer = Session.Installer
>>
>> Set database = Session.Database
>>
>> Function SetFeatureVisible(feature, order)
[snip]
I ported your code to C++ and it does indeed work.
That is
Bob Arnson wrote:
> Sigurd Stenersen wrote:
>> Is it at all possible to modify the number of features in the
>> feature tree, from a DLL or using some sort of action ?
>>
>> I'm able to set the state of features, but I would like to present
>> users with d
Is it at all possible to modify the number of features in the feature tree,
from a DLL or using some sort of action ?
I'm able to set the state of features, but I would like to present users
with different trees depending on selections made in a previous dialog.
Functionally, this is similar to
I am successfully changing properties from a custom install helper DLL, and
these properties trigger conditions within the MSI.
I'm wondering if there is a way to access attributes directly from the DLL,
as this would allow me to get rid of all the condition tags.
E.g. rather than setting a pro
Removing a number of files on uninstall, e.g.
...
Is it possible to use wildcards instead ? E.g.
Sigurd
-
Take Surveys. Earn Cash. Influence the Future of IT
Join
Arnette, Bill wrote:
> the [...] system will package the .msi up
> in a self-extracting zip file for the user to download.
Why ?
Sigurd
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsa
18 matches
Mail list logo