Blair
> > >
> > > > From: r...@robmensching.com
> > > > To: wix-users@lists.sourceforge.net
> > > > Date: Fri, 22 Nov 2013 00:32:25 +
> > > > Subject: Re: [WiX-users] InstallLocation (reg value) vs TARGETDIR vs
> > > Volume free space...
>
ation (reg value) vs TARGETDIR vs
> > Volume free space...
> > >
> > > Depends how you defined InstallLocation in your Directory tree. The
> > TARGETDIR behavior you noted is the Windows Installer documented
> behavior.
> > >
> > > -Original Message-
>
e
> defined
> > by well known system paths.
> >
> > -Blair
> >
> > > From: r...@robmensching.com
> > > To: wix-users@lists.sourceforge.net
> > > Date: Fri, 22 Nov 2013 00:32:25 +
> > > Subject: Re: [WiX-users] Ins
well known system paths.
>
> -Blair
>
> > From: r...@robmensching.com
> > To: wix-users@lists.sourceforge.net
> > Date: Fri, 22 Nov 2013 00:32:25 +
> > Subject: Re: [WiX-users] InstallLocation (reg value) vs TARGETDIR vs
> Volume free space...
> >
>
e advice to not use
> TARGETDIR for anything except the "parent" of directories that are defined
> by well known system paths.
>
> -Blair
>
> > From: r...@robmensching.com
> > To: wix-users@lists.sourceforge.net
> > Date: Fri, 22 Nov 2013 00:32:25 +
>
al Message-
>> From: MeCoco [mailto:vcotirl...@hotmail.com]
>> Sent: 09 March 2011 15:03
>> To: General discussion for Windows Installer XML toolset.
>> Subject: Re: [WiX-users] INSTALLLOCATION wrong value during uninstall (has
>> the default value, not the used one)
&
n as INSTALLDIR.
>
> -Original Message-
> From: MeCoco [mailto:vcotirl...@hotmail.com]
> Sent: 09 March 2011 15:03
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] INSTALLLOCATION wrong value during uninstall (has
> the default val
:03
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] INSTALLLOCATION wrong value during uninstall (has
the default value, not the used one)
Hi Michael,
Thanks again for the explanation.
Could you also tell me please what are the following lines of code
actually do
Hi Michael,
Thanks again for the explanation.
Could you also tell me please what are the following lines of code
actually do?:
Thanks!
MeCoco
On 3/9/2011 3:08 PM, Michael Urman wrote:
> That doesn't look like it creates a component whose Directory is
> INSTALLDIR. It may put the component's
That doesn't look like it creates a component whose Directory is
INSTALLDIR. It may put the component's file in the same directory, but
since custom actions could override this, it doesn't count. What you
need is the Directory_ column of the Component table to say INSTALLDIR
instead of MyApp.Binari
Hi Michael,
Thanks for your answer.
Is the following code not enough to preserve the INSTALLDIR directory?
As the file MyApp.app.config ends up going into the INSTALLLOCATION
directory?
I am not even sure what the:
is doing as the:
doesn't have any Name parameter, so it l
: 3
Date: Tue, 8 Mar 2011 10:31:20 +0100
From: MeCoco
Subject: Re: [WiX-users] INSTALLLOCATION wrong value during uninstall
(has the default value, not the used one)
To: "General discussion for Windows Installer XML toolset."
Message-ID:
Content-Type: text/plain; charset=&
Directories are only automatically preserved when there is a component
that installs to it. So make sure at least one component installs to
INSTALLDIR.
On Tue, Mar 8, 2011 at 03:31, MeCoco wrote:
> Hi all,
>
> I tried to create a small sample to reproduce the problem I'm having,
> and after a lot
Hi all,
I tried to create a small sample to reproduce the problem I'm having,
and after a lot of tries I managed to reproduce it. The problem is
described extensivly in my previous email, but a summary would be: if
the user, when installing, changes the default directory (eg: from
C:\Program F
:pshirtcli...@sdl.com]
Sent: Tuesday, July 20, 2010 1:28 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] {INSTALLLOCATION] Not Expanding to It's Value in a
Type 2 Custom Action
Deferred custom actions have access to a very limited set of properties.
This
taller XML toolset.
Subject: [WiX-users] {INSTALLLOCATION] Not Expanding to It's Value in a
Type 2 Custom Action
I have a Type 2 Custom Action that isn't working right.
LG_IIS7Installer.exe is running, but INSTALLLOCATION is not expanding.
INSTALLLOCATION is set as a property= on the msiexec c
I have a Type 2 Custom Action that isn't working right. LG_IIS7Installer.exe
is running, but INSTALLLOCATION is not expanding. INSTALLLOCATION is set as a
property= on the msiexec command line, and the files get installed into the
right places. But instead of he path expected, INSTALLLOCATION
sravi...@yahoo.com]
Sent: Tuesday, June 15, 2010 2:21 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] installlocation
Hi,
I mean my msi is not copying the files in the correct path(installed path of
an application) during modifying option.
How to get the installed path for an applic
Hi,
I mean my msi is not copying the files in the correct path(installed path of
an application) during modifying option.
How to get the installed path for an application during the install and how
to use that path during modify option of an msi.
Can any one give me an idea/example on how to
On 4/12/2010 3:26 PM, lewisv wrote:
> I figure a custom action called after costinitialize could get the locations
> just fine. Even return the default directories as needed. My question though
> is how to organize the directory xml, and put my directories in there.
>
If you're setting the targ
I have several subdirectories that need to be created and shared when i
install my app.
During the first time install they will look something like this
AppData
Photos
Reports
But each of these could hold a lot of data. So my app is built to be able to
look on different drives. The user c
You need a type 51 custom action that sets ARPINSTALLLOCATION.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Brown
Sent: Monday, November 27, 2006 11:16 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] InstallLocation
Hi,
I want to be able to complete an install such that the InstallLocation property
of the Win32_Product WMI class is properly filled in. Here is an example script
for enumerating Win32_Product instances and their properties:
--- cut products.js -
23 matches
Mail list logo
