Hey again Blaine,
> Si - I wasn't as clear as I meant to be before.
> Because our automated packager builds at least 2 MSI's a day per product
> and has built up to 6 versions in a day when we are close to deadline I
> really don't want to open and update Wix by hand to change the
> variables.
Dear All,
I have decided to use the WiXUI.INSTALLDIR to create a file installer. I
want to know if I can manage the dialogs that are used in the WiXUI library.
Is it possible to use the dialogs in some other sequence, or put custom
dialogs between two of them?
In fact, I need a dialog to let the
Does it look like a UAC issue or something else. There's too much MSI/UAC
interaction to describe here, but does your MSI run elevated? You might be an
administrator but if your MSI doesn't elevate it will run as non-admin.
Phil Wilson
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
When you apply a patch during minor upgrade it will add PatchFiles action to
the AdminExecuteSequence table. Heath Stewart mentions that in his blog:
http://blogs.msdn.com/heaths/archive/2006/02/14/532200.aspx
Alex
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stas Klyachkov
Rob Hamflett wrote:
> They've always appeared for me in the order I've declared the Features in my
> .wxs file, but I'm not
> using FeatureRefs. Perhaps you could use Features that contain
> ComponentGroupRefs? That's what I do.
OK, they show up in the order I want if I put the s directly
un
I asked this before but didn't receive any replies. Given that there seems
to be considerable discussion on upgrades lately I thought I would ask it
again (maybe in a different form)
I have an installation script that installs code, service, everthing just
fine. The problem is that I have not f
They've always appeared for me in the order I've declared the Features in my
.wxs file, but I'm not
using FeatureRefs. Perhaps you could use Features that contain
ComponentGroupRefs? That's what I do.
Rob
Flavio Stanchina wrote:
> Bob Arnson wrote:
>> Flavio Stanchina wrote:
>>> [...] so I'm
Si - I wasn't as clear as I meant to be before.
Because our automated packager builds at least 2 MSI's a day per product
and has built up to 6 versions in a day when we are close to deadline I
really don't want to open and update Wix by hand to change the
variables.
Today, I use a VB script to o
Bob Arnson wrote:
> Flavio Stanchina wrote:
>> [...] so I'm asking: is there a way to set the order of features in
>> the custom setup dialog?
> MSI doesn't have a way of specifying the order of features, so there's
> no guarantee they'll show up in a particular order.
InstallShield allows you t
Hi there,
I've noticed that AdminExecuteSequence Element does not supported PatchFiles
standard action.
Is it a bug? Is there any reason for this? Workaround?
Thanks,
Stas
-
This SF.net email is sponsored by: Microsoft
Defy a
When installing applications that use shared assemblies that they add to the
GAC, does WIX implicitly handle the reference counts to ensure one
application can't pull the assemblies out during uninstall if another app is
still using them? Or does something like the SharedDllRefCount attribute
have
I apologize if this is old hat, but I am looking to validate a serial
number. There are two buttons "Next" and "Check Serial", along with a
maskededit box linked to the "Serial_Number" property.
When I click the "Check Serial" button it runs the validation DLL which
then reads the "Serial_Numb
Ryan
I thought this might help you, it is my bare minimum template install.
Neil
http://schemas.microsoft.com/wix/2003/01/wi";>
Ok, thanks :)
I think that would help
-Sneha
Rob Hamflett wrote:
>
> Yeah. I just use a response file because I have a fair few preprocessor
> defines. You can certainly
> just list them individually on the command line.
>
> Rob
>
> Sneha Gharpure wrote:
>> Hi,
>>
>> Thanks for the reply
Yeah. I just use a response file because I have a fair few preprocessor
defines. You can certainly
just list them individually on the command line.
Rob
Sneha Gharpure wrote:
> Hi,
>
> Thanks for the reply.
>
> What I understood from your reply is that say English.txt will have list of
> all
Hi,
Thanks for the reply.
What I understood from your reply is that say English.txt will have list of
all the preprocessor variables say $(var.LicenseFile). And these variables
are given at the time of compilation to candle. So rather than using a
text file, can it be done by supplying is as a
faheemitian wrote:
>
> Anybody for help!
>
> I have even reversed the setup to wix 2.0 stable version but all in vain!
>
> - Dev
>
I think I have figured it out. Problem was not with Registry or Service
Install tags but with a feature condition. If you look at
http://www.nabble.com/file/p
For the parts that can't be localised, I use preprocessor variables. All the
English specific stuff
is defined in English.txt and the Japanese stuff is defined in Japanese.txt.
In my Makefile I have
separate command lines for the English and Japanese builds, which take
parameters of @English
Thanks again Bob, using the right WiX elements seems to have done the
trick. All this registry hardcoded lark was added while I was on
holiday, I take no responsibility!
Simon
-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 05 March 2008 05:12
To: Simon Topley
Cc: wi
Hi,
The scenario is that the name of the license agreement file is to be
localized. The source file for the license agreement is specified as
follows.
This gives an error error LGHT0100 : File of type 'File' with name
'$(loc.LicenseFile)' could not be found.
Is there any way to localiz
Hi Blaine, cc'd to list.
> I really like your code sample, particularly the use of the variables.
> Which raises a question about managing sequential-multiple builds. May
> I ask how you get the $(var.ProductVersion) and
> $(var.PreviousProductVersion) to pass into Wix?
They're just WiX varia
21 matches
Mail list logo
