You need to set the codepage attribute to the Franch codepage. Than it will
work.
_
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris
Bardon
Sent: Wednesday, October 17, 2007 2:44 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-us
t
time for each user.
Regards,
Brett Kapilik
Kapilik.com
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Chris
> Sent: Tuesday, September 18, 2007 3:57 PM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] .NET user.conf
alog typically has a condition of Not Installed, a
> Maintenance/Change dialog a condition of Installed<>"".
>
>
> Phil Wilson
>
>
> -Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Brett Kapilik
> Sent
In the Registry, installers created with WiX make the entry:
UninstallString = Msiexec.exe /X{}
Which makes the uninstall run with a minimal UI. Is there a way to make
the ARP entry:
UninstallString = Msiexec.exe /I{}
So that it forces the change/remove/repair screen instead?
Thanks,
Brett
-
My understanding is that the order that shortcuts appear is usually
alphabetical. But ultimately it is a user-setting. Schortcut groups are
just folders and I believe that the arrange by setting applies.
- Brett
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of W
s also very cool). I just couldn't let
this thread end with someone wishing the InstallAware would make such a
tool. :)
- Brett Kapilik (Indigo Rose Corporation)
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Peterson,
Joel
Sent: Monday, June 25,
I have seen this several times as well. It seems to have something to do
with using an ALLCAPS directory id (COMBINEDPRODUCTFOLDER). Try putting
at least one lower case letter in and it will work. I do not know why
this happens. COuld it have something to do with the ALLCAPS directory
ID being trea
It looks like your components do not have key paths. Are you getting
build errors or runtime errors?
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike
Dimmick
Sent: Sunday, June 17, 2007 1:58 PM
To: 'Pierson Lee (Volt)'; wix-users@lists.sourcef
Add "-cultures:en-us" (or your supported language of choice) to the
light command line as well.
- Brett
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Afshin
Sepehri
Sent: Tuesday, June 12, 2007 1:40 PM
To: Bob Arnson
Cc: wix-users@li
be giving away a bunch of free licenses at the end. If you are
interested, please sign up here:
http://www.indigorose.com/sufwi/index.php
Hope to see you there! Feel free to email or call me directly if you
have any questions or problems signing up for the beta.
Regards,
Brett Kapilik
Indigo Ros
You can try using -sval to supress the MSI validation. That is what eats
up most of the time. But of couse, you miss out on validation...
However, for doing test builds, that should speed it up.
- Brett
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behal
Although I have not tested this, what about setting the ARPSIZE property
directly?
http://msdn2.microsoft.com/en-us/library/aa367748.aspx
- Brett
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Don
Tasanasanta
Sent: Tuesday, May 01, 2007 4:26 PM
file that's made up of both my software MSI and
the OEM MSI?
Or are you stating that I should write a simple program named
Setup.exe that runs both MSI files in the background?
- Michael Reiland
On 5/1/07, Brett
If the other installer does not use MSI then you could call it with a
custom action. If it is MSI then you will probably have to resort to
bootstrapping both it and your installer into one setup.exe routine.
- Brett
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
to go home for the weekend...
- Brett
> -Original Message-
> From: Rob Mensching [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 27, 2007 2:45 PM
> To: Brett Kapilik; WiX-users@lists.sourceforge.net
> Subject: RE: Why are VBScriptCall/JScriptCall required?
>
> O
g [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 27, 2007 2:52 PM
> To: Brett Kapilik; Matt Anderson; wix-users@lists.sourceforge.net
> Subject: RE: [WiX-users] Getting file versions
>
> We've had this debate before. We decided not to do this back
> then... I'm still unc
: [WiX-users] Getting file versions
>
> Brett Kapilik indigorose.com> writes:
>
> >
> > Matt,
> >
> > What do you mean by:
> >
> > "I just wanted to know if there was a way to determine
> automatically
> > in WiX if a file had ver
Matt,
What do you mean by:
"I just wanted to know if there was a way to determine automatically in
WiX if a file had version
information or not and set that attribute accordingly."
Where would you expect this to happen? WiX does, by default, determine
if the file has version information or not
A question for Rob and the others who are responsible for the WiX
architecture:
When using say a VBScript custom action (Type 6) with the BinaryKey
attribute set (the VBScript is in the Binary table), why was it designed
so that you HAVE to spcify a VBScriptCall attribute? The Windows
Installer do
Use the CustomAction element. There are a few ways to do it, but the one
the comes to mind as a general solution is to schedule it after
InstallFiles in the InstallExecuteSequence and set the Execute attribute
to "deferred" ot "commit". Make sure that you read the MSDN topics about
deferred custom
What about using the CompanionFile attribute (File element) for the
non-versioned file?
- Brett
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Matt Anderson
> Sent: Friday, April 27, 2007 7:28 AM
> To: wix-users@lists.sourceforge.net
> Subject
Why not schedule the SetMyProperty custom action into the
InstallUISequence instead of InstallExecuteSequence? Or into both. I
would imagine that the problem might be related to the
InstallExecuteSequence not being run until after the InstallUISequence.
Not sure about all that, but maybe it will ge
We (me and the company that I work for) are in the process of making a
setup tool (like InstallShield but laid out much better) that generates
WiX (3.0) files and then builds with candle and light. It generates 100%
pure WiX and has a visual interface as well as a full dialog editor. The
way that w
From: Ricardo Lopes [mailto:[EMAIL PROTECTED]
Sent: Friday, April 20, 2007 10:55 AM
To: Brett Kapilik
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Conditional registry key using CheckBox
control
Thanks,
Try making the property public (ALLCAPS):
Then reference it in the component condition as the all-uppercase
property name.
- Brett
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ricardo
Lopes
Sent: Friday, April 20, 2007 10:27 AM
To: wix-
Well, if the download is generic - just a file on a server - then I
don't see how you can do this. However, if you are running a Windows
server (ASP) theoretically I suppose you could make the download script:
- Make a copy of the msi file on the server
- Use the MSI Automation interface to open
I believe it is because your Package is marked as Compressed but your
Media (2) is not compressed. In this case, MSI expects the source files
to be in the same folder as the msi file. From the MSI docs:
Note that if the package is marked as compressed (Bit 1 is set), the
Windows Installer only in
Not sure about an official "rename" but what about using the CopyFile
element with Delete="yes".
- Brett
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Matt Anderson
> Sent: Thursday, April 19, 2007 9:15 AM
> To: wix-users@lists.sourceforge.ne
You can use a ComponentSearch Element to find the installed location of
an existing component on the system.
- Brett
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> teckJBMsia
> Sent: Thursday, April 19, 2007 3:27 AM
> To: wix-users@lists.sourc
Robert,
Where is the custom action called from - where is it scheduled? Is it
deferred?
- Brett
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Robert Randall
> Sent: Wednesday, April 18, 2007 9:40 AM
> To: wix-users@lists.sourceforge.net
> Su
Changing the drive letter is usually up to the user at runtime. You
specify something like Program Files\Whatever and then let the user
change the location if they want to. Do you have a specific need to
hard-code a drive letter into the installer? Perhaps if you can expand
on what you are trying t
Wow - how did I possibly miss that? My apologies. Thanks for the
response.
- Brett ;)
_
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Monday, April 16, 2007 12:21 PM
To: Brett Kapilik
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX
Working with WiX 3.0.2806.0. I am setting up a TTF file to be registered
as a font on the system:
The above works OK, except that I get:
G:\My Documents\Output\setup.wxs(53) : warning LGHT1076 : ICE51: Font
'EGGS.TTF' is a TTC\TTF font, but also has a title.
This is because FontTitle="Eggs (Tr
Scott,
I have not seen that problem with Advertised shortcuts. The only time I
have had problems is if I do not specify an icon for the shortcut at
all. I wonder if it has to do with the name of your icon. From the WiX
help file:
Identifier reference to Icon element. The Icon identifier should
a best practice recommendation.
- Brett
> -Original Message-
> From: Rob Mensching [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 11, 2007 1:00 PM
> To: Alex Steen; Brett Kapilik; wix-users@lists.sourceforge.net
> Subject: RE: [WiX-users] Custom Action that references C#
Yes, just specify them in the ExeCommand attribute.
- Brett
> -Original Message-
> From: Alex Steen [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 11, 2007 12:55 PM
> To: Brett Kapilik; wix-users@lists.sourceforge.net
> Subject: RE: [WiX-users] Custom Action th
You can certainly do that. You should include both the C# dll and the
executable that calls it in your installer. Then make a CustomAction
element that defines the custom action. Make sure to use the FileKey
attribute to reference the executable's file ID (i.e "Myfile.exe") as
well as any of the ot
The other thing that you could try is defining your constants in a wix
include file (.wxi) and then including it in your main wxs file. This
way your build environment just generates the wxi file and does not
touch your main wxs file. Just another approach to consider...
- Brett
> -Original
ess I should have made my answer more specific.
- Brett
_
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 14, 2007 2:55 PM
To: Brett Kapilik; wix-users@lists.sourceforge.net
Subject: RE: Re: [WiX-users] Set All Users de
Set the ALLUSERS property to "2". That should do it.
- Brett
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bei Liu
(Volt)
Sent: Wednesday, March 14, 2007 2:44 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Set All Users de
40 matches
Mail list logo
