16/09/2011 20:10, Rob Mensching a écrit :
> Because StartServices can't start services before the files for the services
> are installed.
>
> 2011/9/16 Frédéric Viollet
>
>> Hi Rob,
>>
>> Do you mean that if I write:
>>
>>
>>
>>
>> O
Why would
guarantee me that it will be executed after InstallFiles?
Thanks.
Fred
Le 16/09/2011 11:56, Rob Mensching a écrit :
> Pick one.
>
> 2011/9/15 Frédéric Viollet
>
>> Hi All,
>>
>> I have defined two custom actions and I would like it to be tri
Hi All,
I have defined two custom actions and I would like it to be triggered
after InstallFiles, but before StartServices.
Lets say I want to setup the following sequence:
InstallFiles -> CustomAction1 -> CustomAction2 -> StartServices
I would have liked to write:
But, in the wxs, Before and
Office - Helix Building, West Of Scotland Science Park, Glasgow
> G20 0SP
> Email Disclaimer
>
> -Original Message-
> From: Frédéric Viollet [mailto:frederic.viol...@evidian.com]
> Sent: 22 March 2011 11:19
> To: 'General discussion for Windows Installer XML toolse
pgrades.
Could someone please tell me what I am doing wrong?
Thanks for your help...
Fred
--
*____*
*Frédéric VIOLLET* - Role Management Software Engineer
Tel: +33 (0) 1 30 80 77 34
Fax: +33 (0) 1 30 80 77 99
Std: +33 (0) 1 30 80 70 00
www.wise
Hi all,
I've been struggling for two days trying to achieve something that I
believe simple (obvioulsy not for me...)
Here's some part of my code:
... install some stuff here ...
... close all directories
On an initial installation, the UI allows me to set the 'A_DIRECTO
Hi,
I'm trying to use heat to generate a wxs fragment file out of a directory.
But it seems the heat does not support UNC paths neither for the "dir"
parameter nor for the "out" parameter...
Is this a "normal" behaviour?
Here are the two tested command lines:
heat.exe dir thedir -ag -sfrag -out
Bob Arnson a écrit :
> Frédéric Viollet wrote:
>
>> -I want to install a 64 bit product (my exes and dll are natively
>> compiled for 64bit) on a 64bit OS
>> -I build an x64 MSI (Platform=x64, Win64=yes in Components, etc...)
>> -I build a 32bit bootstrapper usin
Bob Arnson a écrit :
> Frédéric Viollet wrote:
>
>> -do I have to install the 64bit version of Wix? I guess not...the
>> 32bit version should still be working... am I right?
>>
>
> The 64-bit WiX installer exists to support MSBuild running as a
Hi,
I'm currently using setupbld (in Wix V3) as a bootstrapper for managing
my product upgrades.
My team is willing to build a native 64 product. Compilation will be
done on a 64 bit OS.
My questions are :
-do I have to install the 64bit version of Wix? I guess not...the 32bit
version should
Ok. I'll have a look at former discussions than.
Thanks.
Fred
Rob Mensching a écrit :
> This is discussed much in the list. You might search to get lots of options.
> Nothing is supported natively.
>
> -Original Message-
> From: Frédéric Viollet [mailto:frederic
Hi everyone,
I was wondering if it was possible to build a single installer that
embeds several languages (this installer would switch to the platform's
current language)?
Or do I have to build as many installers as I have languages to support?
I want my product to be able to be deployed in Fr
Johan Appelgren a écrit :
> On Tue, Jul 1, 2008 at 11:29 AM, Frédéric Viollet
> <[EMAIL PROTECTED]> wrote:
>
>> Johan Appelgren a écrit :
>>
>>> On Tue, Jul 1, 2008 at 10:07 AM, Frédéric Viollet
>>> <[EMAIL PROTECTED]> wrote:
>>>
Ok, thanks for your answer.
Fred
Nitin Chaudhari a écrit :
String manipulation is not supported in WIX, you will have to write a
C++/.net/vbs custom action to get substring.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Frédéric
Viollet
Sent
Hi everyone,
Let's say that I have a registry key HKLM\Software\MyProduct with a
String value "TheDir" = "c:\program files\My product\module"
I can easily get the value by using a RegistrySearch:
Here's the question: :)
Is there a way to extract a substring from the retrieved value
i.e. T
Johan Appelgren a écrit :
> On Tue, Jul 1, 2008 at 10:07 AM, Frédéric Viollet
> <[EMAIL PROTECTED]> wrote:
>
>> Hi everyone,
>>
>> I've got a real big problem here on applying minor upgrades to my
>> product. I really need your help here :)
>>
Hi everyone,
I've got a real big problem here on applying minor upgrades to my
product. I really need your help here :)
During the first install, I ask the user where the product should be
installed (by using the wix standard Gui)
But on minor upgrades, I do not ask him again. I just re-install
Bob Arnson a écrit :
Frédéric Viollet wrote:
Could someone please tell me which condition I should use to trigger a
custom action only on installations (initial installation and minor
upgrades).
This custom action must not be run on uninstall.
See http://msdn.microsoft.com/en-us
Hi,
Could someone please tell me which condition I should use to trigger a
custom action only on installations (initial installation and minor
upgrades).
This custom action must not be run on uninstall.
Thanks a lot.
Fred
--
Hi,
I have a package in which the MFC and MSVCRT runtime libraries are
needed. So I decided to use Microsoft's merge modules... so far so good...
The problem is that I have a custom action that calls an executable
which needs these MFC and Runtime libraries to be installed.
I'm calling the custo
Bob Arnson a écrit :
> Frédéric Viollet wrote:
>> The problem is that, according to the MSDN, REINSTALL=ALL only
>> reinstalls the previously installed features. So I am not able to add
>> new features on a minor upgrade.
>>
>
> You need to install new fea
arguments for
> the msiexec on the minor update. The arguments specify things like,
> replace files only if..., etc. I would make sure there isn't one that
> specifies to add files/features not previously present.
>
> Cheers,
> Lincoln
>
> Frédéric Viollet wrote:
&
News again
The error 2771 was indeed my fault. So please don't pay attention to
last message I posted.
But with packages that do not raise the 2771 error, I still can't add a
new feature with a new component :(
Fred
Frédéric Viollet a écrit :
> Hi,
>
> I've d
."
I don't understand this message since none of the existing components
have been removed.
I'm only trying to add a new component in a new feature :(
I'm really lost..... :(
Fred
Frédéric Viollet a écrit :
> Hi Rob,
> Thanks for your answer.
> Now I'm trying to
> A minor upgrade can be used to add new features and components but
> cannot reorganize the feature-component tree.
>
> You'll need to add the new Components to a new Feature.
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On B
Hi everyone,
Is it possible to add a component to an installed feature through a
minor upgrade?
The component I'm trying to add contains two files. And it seems, by the
behavior I'm experiencing, that the answer is *no*.
Could someone confirm this?
Point #1: The product, to which I'd like to ad
I've just found out how to manage this.
I changed ProductId, UpgradeCode (and UpgradeId). Then I added an
Upgrade entry with the old UpgradeCode (and I also removed the
OnlyDetect attribute).
Everything works fine now!
Thanks anyway :)
Fred
Frédéric Viollet a écrit :
> Oups...!
>
Oups...!
My mistake : changing the productId *does* trigger a new installation
(from scratch ... asking for install dir and all that) *but* my previous
version is not removed...
Any idea?
Thanks again.
Fred
Frédéric Viollet a écrit :
> Hi everyone,
>
> I've changed a lot of thi
Hi everyone,
I've changed a lot of things (files and directories) in my application,
and I'd like to remove any previously installed version of the product
before installing the new one.
Here's the situation
previous version of my product had the following items in the wxs:
Frédéric Viollet a écrit :
> Hi everyone,
>
> I'm using the setupbld tool to generate exe files from my msi files and
> this is working pretty well.
> I was wondering, though, how could I do to send the "/log" command to
> the msi
> I tried
> &
Hi everyone,
I'm using the setupbld tool to generate exe files from my msi files and
this is working pretty well.
I was wondering, though, how could I do to send the "/log" command to
the msi
I tried
"mysetup.exe /msicl "log c:\temp\msi.log"
"mysetup.exe /msicl "/log c:\temp\msi.log"
but no
Bob Arnson a écrit :
Frédéric Viollet wrote:
C:\temp\wix-3.0.2925.0-sources>make.bat ship
Please try a weekly release from http://wix.sourceforge.net/releases/
or a CVS checkout.
Hi Bob,
Thanks again for replying.
-I tried from a CVS checkout, I got the following error:
c:\t
Hi everyone,
I'm encoutering some problems while trying to build Wix v3 with nant
I get the following error message:
C:\temp\wix-3.0.2925.0-sources>make.bat ship
NAnt 0.85 (Build 0.85.2478.0; release; 14/10/2006)
Copyright (C) 2001-2006 Gerry Shaw
http://nant.sourceforge.net
Buildfile: file:///
Hi everyone,
I'm launching a .bat file through a custom action. Everything works well
except that I can see in the background (very quickly, because the batch
doesn't do much) a cmd window executing the batch file.
My question : is there a way to tell that the cmd window should be
hidden during
Hi everyone,
I'm trying to use a custom Eula.rtf file for the LicenseAgreementDlg dialog.
So I added the -dWixUILicenseRtf=Eula.rtf flag to my light command line
and I also added a -b with the base path to my Eula.rtf file.
The linker fails with the following error :
LicenseAgreementDlg.wxs(28)
Bob Arnson a écrit :
> Frédéric Viollet wrote:
>> Ok. I've just had a look at setupbld source code. And it seems that
>> REINSTALLMODE is set to vomus for a minor upgrade.
>> I guess I need it to be set to vamus to force all files to be
>> rewritten. Is there
Frédéric Viollet a écrit :
Bob Arnson a écrit :
Frédéric Viollet wrote:
When I perform a minor upgrade of my product using the generated
executable file, not all of the files are upgraded. Only the files
that have changed are updated.
I thought that even on a minor upgrade, all the
Bob Arnson a écrit :
> Frédéric Viollet wrote:
>> When I perform a minor upgrade of my product using the generated
>> executable file, not all of the files are upgraded. Only the files
>> that have changed are updated.
>> I thought that even on a minor upg
Hi all,
I have a question about the setupbld.exe tool.
I'm using this tool in WixV3 with the mcpsu options and I've noticed
some strange behaviour.
When I perform a minor upgrade of my product using the generated
executable file, not all of the files are upgraded. Only the files that
have cha
gramFilesFolder] with DestinationDirectory
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frédéric Viollet
Sent: Monday, September 17, 2007 12:14 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Silent install won't copy in files
Mike Menaker a écrit :
Hi,
I’m having a problem with a silent install.
I have a component that copies 2 files and writes to the registry
however it isn’t copying the 3 files correctly (yet writing the
registry correctly).
This is my component.
Guid="49861A79-A034-4e15-BA38-783D2FCC4D90">
Ok. This isn't really the behavior I'm looking for.
I managed to solve my problem by using Components with empty GUIDs to
install and modify the config files.
In that way, the component is not managed. Since it cannot be updated or
removed, my config files are not overwritten on upgrades any more
Hi,
I've got a new question for the community.
Could someone tell me if the element is called before or after
the action
Thanks in advance for your help.
Fred
-
This SF.net email is sponsored by: Microsoft
Defy all chall
Does nobody have a clue?
I'm really sorry to insist on my problem, but it's getting quite a
critical issue :(
Thanks again for your help.
Frédéric Viollet a écrit :
> Stefan Krueger [MVP] a écrit :
>
>> So you only want to condition the copy (which corresponds to a Mo
Stefan Krueger [MVP] a écrit :
> So you only want to condition the copy (which corresponds to a MoveFile
> table row I guess) but not the instalaltion of the component. To do this you
> need to put the copy element in a separate component, because rows in the
> MoveFile table can't have conditio
Stefan Krueger [MVP] a écrit :
> The component must have the msidbComponentAttributesTransitive bit set
> (don't know the WiX syntax for this). This should remove the component
> during (auto-)repair, modify and small and minor updates - probably not what
> you want. BTW in case of Major Upgrade
Hi everybody,
I have some problems while updating a product through Wix v3
I've written the following code :
NOT Installed
But, even on update, the file amengine.ref is copied to amengine.ini
Any idea?
Thanks for your help.
Fred
--
Bob Arnson a écrit :
> Frédéric Viollet wrote:
>> product's version is already installed, nothing happens. There isn't
>> even a notification to tell that the installation won't start because
>> the product is already up to date. What I would like is start
I forgot to say : I'm using WixV3 3.0.2420.0
Frédéric Viollet a écrit :
Hi everyone,
is there a way to force an upgrade even if the version I'm want to
install is already installed?
I'm using the bootstrapping possibility offered by Wix to generate a
executable file (setupbld)
Hi everyone,
is there a way to force an upgrade even if the version I'm want to
install is already installed?
I'm using the bootstrapping possibility offered by Wix to generate a
executable file (setupbld). The options I use are "mcpsu".
At the moment, if I double click on the setup file and tha
Bob Arnson a écrit :
Frédéric Viollet wrote:
Guid="924B3E41-7157-4927-B892-8D52D8A392BD">
MAXHEAPSIZE AND (MAXHEAPSIZE< 256)
Type="integer" Action="write" />
I get the error : Name cannot begin with the ' ' character,
hexadecimal valu
Bob Arnson a écrit :
Frédéric Viollet wrote:
-During install, I'd like to check for some registry entry (a DWORD.
Lets call it "myDword").
Use RegistrySearch to set a property.
Ok, but what if myDword doesn't exist? What does RegistrySearch return?
-If myDword doesn&#x
Hi everyone,
I'm looking for some good soul that could help to achieve the following
steps:
-During install, I'd like to check for some registry entry (a DWORD.
Lets call it "myDword").
-If myDword doesn't exist or is inferior to a given value x, then I
would like to create/set it to x.
Coul
Ok. Thanks.
I scheduled the action as deferred after InstallFiles (I needed the
custom action to be triggered after file installation and before service
start). I works fine.
Thanks again for your help.
Fred
Mike Dimmick a écrit :
Sorry, either mark as deferred and schedule between InstallIn
Ok, thanks a lot for your explanation.
So if I correctly understood what you said, I must declare my custom
action as deferred. So I guess I write it this way:
DllEntry='apm_edit_conf' Execute='deferred' Return='check' />
NOT
Installed
Is the "After='InstallFiles'" still corre
Hi everyone.
I'm using CustomActions to modify some files after installation. But I
don't really understand the order in which the actions are done.
In my source wxs, I have declared some elements, a
, a Name="APM_WEBSERVICE" Wait="yes" Start="install" /> and some custom
actions. The sequen
Bob Arnson a écrit :
Frédéric Viollet wrote:
Ok.Thanks. Is there a documentation somewhere on how to use the
setupexe bootstrapper?
Not really, no. Here's the command line I use to build one:
"%WIX%\setupbld" -out "%DIR%\foo.exe" -mcsp "%DIR%\foo.msi"
Hi everyone,
I've got a question about merge modules.
I've written a merge module and I would like the files of the merge
module to install themselves in the directory that the user selects
while installing the main package.
Example:
*Merge Module:
Program Files
My Product
bin
ApmFil
Bob Arnson a écrit :
Frédéric Viollet wrote:
Is there a way to perform a minor update without having to add on the
command line REINSTALL=ALL REINSTALLMODE=vomus ???
No. If you want to be able to double-click a package to get an
upgrade, it's got to be a major upgrade MSI package
Hi everyone,
I quite new to Wix and I'm using Wix V3. I've looked around for a
solution to my problem but I can't find anything maybe you will be
able to help me.
So here's the problem:
Is there a way to perform a minor update without having to add on the
command line REINSTALL=ALL REINST
60 matches
Mail list logo
