Re: [WiX-users] RegistrySearch example in tutorial
An MSI itself can be either 32-bit or 64-bit package, and it targets installing
for that bitness (a 64-bit package cannot be used on a 32-bit platform, while a
32-bit package cannot access 64-bit sections of the filesystem).
Typically your build settings set the bitness of the packages you create using
the WiX toolset.
> From: rob...@softdev.net
> To: wix-users@lists.sourceforge.net
> Date: Wed, 28 Aug 2013 07:33:17 +
> Subject: Re: [WiX-users] RegistrySearch example in tutorial
>
> Hi Phil/Blair,
>
> I'm just trying to get through the tutorial on a x64 machine. The problem was
> resolved by creating the key in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node. I
> removed the key I had created in HKEY_LOCAL_MACHINE\SOFTWARE. It now works.
>
> I don't understand "Do you have a 32-bit MSI" or "if you have an x86 platform
> install". Are you referring to the WiX install? I don't remember being
> offered a selection between x86 and x64 during the install - in fact there
> wasn't one.
>
> Regards,
> Robert Clancy
>
> -Original Message-
> From: Phil Wilson [mailto:phildgwil...@gmail.com]
> Sent: Wednesday, 28 August 2013 3:26 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] RegistrySearch example in tutorial
>
> The original registry search you posted doesn't have Win64="yes" so it will
> be a 32-bit registry search if you have an x86 platform install (and it looks
> like you do).
>
> Phil Wilson
>
>
> On Tue, Aug 27, 2013 at 2:29 AM, Blair Murri wrote:
>
> > If you are intending to use the 32-bit registry in a 64-bit platform
> > in RegEdit, you need to start from the
> > HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node
> > (which is the 32-bit HKEY_LOCAL_MACHINE\SOFTWARE key).
> > You make TARGETDIR conditional by setting a property by that name to
> > the full path (hopefully with a backslash ('\') at the end) before
> > costing starts in whatever sequence starts first. Same with INSTALLDIR.
> > Subdirectories will automatically use the path set for their parents
> > if a path is not presupplied. During costing, properties will be
> > created for all directories that didn't already have properties (and
> > each one will be set to the full path of that directory).
> > AppSearch, et. al. will set the property you specify. So will the
> > command-line. By default, the *Search actions will override the
> > command-line.
> >
> > > From: rob...@softdev.net
> > > To: wix-users@lists.sourceforge.net
> > > Date: Mon, 26 Aug 2013 23:52:18 +
> > > Subject: Re: [WiX-users] RegistrySearch example in tutorial
> > >
> > > Thanks for both replies. I am indeed on a x64 machine and have no
> > > idea
> > how to distinguish between x86/x64 registries. I've probably created
> > the key in the wrong one. Any pointers? To open the editor, I type in
> > "regedit"
> > >
> > > If not that, then how should I make this conditional:
> > >
> > > > >
> > > > >
> > > > >
> > > > >
> > >
> > > -Original Message-
> > > From: Phil Wilson [mailto:phildgwil...@gmail.com]
> > > Sent: Tuesday, 27 August 2013 4:49 AM
> > > To: General discussion for Windows Installer XML toolset.
> > > Subject: Re: [WiX-users] RegistrySearch example in tutorial
> > >
> > > What often happens is that there is a custom action to set the
> > > default
> > INSTALLDIR location to the program files folder, and people forget to
> > make it conditional, with a condition like NOT INSTALDIR. You may
> > find that if you set INSTALLDIR on an msiexec command line it would
> > also get overwritten. The NOT INSTALLDIR condition just means "don't
> > set it to default if it's already set".
> > >
> > > Phil Wilson
> > >
> > >
> > > On Mon, Aug 26, 2013 at 3:42 AM, Blair Murri wrote:
> > >
> > > > "Adding" is not overridding, it is creating.
> > > > That would suggest that there is no InstallDir value at
> > > > HKLM\Software\Acme\Foobar 1.0 Do you have a 32-bit MSI and are
> > > > trying to read a 64-bit registry location, per chance? Or vice versa?
> > > >
> > > > > From: rob...@softdev.net
> > > > > To: wix-users@lists.sourceforge.net
> > > > > Date: Mon, 26 Aug 2013 06:31:51 +
> > > > > Subject: [WiX-
Re: [WiX-users] RegistrySearch example in tutorial
Hi Phil/Blair,
I'm just trying to get through the tutorial on a x64 machine. The problem was
resolved by creating the key in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node. I
removed the key I had created in HKEY_LOCAL_MACHINE\SOFTWARE. It now works.
I don't understand "Do you have a 32-bit MSI" or "if you have an x86 platform
install". Are you referring to the WiX install? I don't remember being offered
a selection between x86 and x64 during the install - in fact there wasn't one.
Regards,
Robert Clancy
-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: Wednesday, 28 August 2013 3:26 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] RegistrySearch example in tutorial
The original registry search you posted doesn't have Win64="yes" so it will be
a 32-bit registry search if you have an x86 platform install (and it looks like
you do).
Phil Wilson
On Tue, Aug 27, 2013 at 2:29 AM, Blair Murri wrote:
> If you are intending to use the 32-bit registry in a 64-bit platform
> in RegEdit, you need to start from the
> HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node
> (which is the 32-bit HKEY_LOCAL_MACHINE\SOFTWARE key).
> You make TARGETDIR conditional by setting a property by that name to
> the full path (hopefully with a backslash ('\') at the end) before
> costing starts in whatever sequence starts first. Same with INSTALLDIR.
> Subdirectories will automatically use the path set for their parents
> if a path is not presupplied. During costing, properties will be
> created for all directories that didn't already have properties (and
> each one will be set to the full path of that directory).
> AppSearch, et. al. will set the property you specify. So will the
> command-line. By default, the *Search actions will override the
> command-line.
>
> > From: rob...@softdev.net
> > To: wix-users@lists.sourceforge.net
> > Date: Mon, 26 Aug 2013 23:52:18 +
> > Subject: Re: [WiX-users] RegistrySearch example in tutorial
> >
> > Thanks for both replies. I am indeed on a x64 machine and have no
> > idea
> how to distinguish between x86/x64 registries. I've probably created
> the key in the wrong one. Any pointers? To open the editor, I type in
> "regedit"
> >
> > If not that, then how should I make this conditional:
> >
> > > >
> > > >
> > > >
> > > >
> >
> > -Original Message-
> > From: Phil Wilson [mailto:phildgwil...@gmail.com]
> > Sent: Tuesday, 27 August 2013 4:49 AM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] RegistrySearch example in tutorial
> >
> > What often happens is that there is a custom action to set the
> > default
> INSTALLDIR location to the program files folder, and people forget to
> make it conditional, with a condition like NOT INSTALDIR. You may
> find that if you set INSTALLDIR on an msiexec command line it would
> also get overwritten. The NOT INSTALLDIR condition just means "don't
> set it to default if it's already set".
> >
> > Phil Wilson
> >
> >
> > On Mon, Aug 26, 2013 at 3:42 AM, Blair Murri wrote:
> >
> > > "Adding" is not overridding, it is creating.
> > > That would suggest that there is no InstallDir value at
> > > HKLM\Software\Acme\Foobar 1.0 Do you have a 32-bit MSI and are
> > > trying to read a 64-bit registry location, per chance? Or vice versa?
> > >
> > > > From: rob...@softdev.net
> > > > To: wix-users@lists.sourceforge.net
> > > > Date: Mon, 26 Aug 2013 06:31:51 +
> > > > Subject: [WiX-users] RegistrySearch example in tutorial
> > > >
> > > > I'm a novice user, going through Getting Started. I cannot get
> > > > the
> > > RegistrySearch to work, or FILEEXISTS - both from "Where to Install?"
> > > page in your tutorial.
> > > >
> > > > I suspect it is because this element:
> > > >
> > > >> > Key='Software\Acme\Foobar 1.0' Name='InstallDir' />
> > > >
> > > >
> > > > is overridden by the subsequent
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Meaning that if the registry sets a directory outside of program
> > > > files,
> > > then it seems to not work because later in the wxs file it is
> > >
Re: [WiX-users] RegistrySearch example in tutorial
The original registry search you posted doesn't have Win64="yes" so it
will be a 32-bit registry search if you have an x86 platform install (and
it looks like you do).
Phil Wilson
On Tue, Aug 27, 2013 at 2:29 AM, Blair Murri wrote:
> If you are intending to use the 32-bit registry in a 64-bit platform in
> RegEdit, you need to start from the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node
> (which is the 32-bit HKEY_LOCAL_MACHINE\SOFTWARE key).
> You make TARGETDIR conditional by setting a property by that name to the
> full path (hopefully with a backslash ('\') at the end) before costing
> starts in whatever sequence starts first. Same with INSTALLDIR.
> Subdirectories will automatically use the path set for their parents if a
> path is not presupplied. During costing, properties will be created for all
> directories that didn't already have properties (and each one will be set
> to the full path of that directory).
> AppSearch, et. al. will set the property you specify. So will the
> command-line. By default, the *Search actions will override the
> command-line.
>
> > From: rob...@softdev.net
> > To: wix-users@lists.sourceforge.net
> > Date: Mon, 26 Aug 2013 23:52:18 +
> > Subject: Re: [WiX-users] RegistrySearch example in tutorial
> >
> > Thanks for both replies. I am indeed on a x64 machine and have no idea
> how to distinguish between x86/x64 registries. I've probably created the
> key in the wrong one. Any pointers? To open the editor, I type in "regedit"
> >
> > If not that, then how should I make this conditional:
> >
> > > >
> > > >
> > > >
> > > >
> >
> > -Original Message-
> > From: Phil Wilson [mailto:phildgwil...@gmail.com]
> > Sent: Tuesday, 27 August 2013 4:49 AM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] RegistrySearch example in tutorial
> >
> > What often happens is that there is a custom action to set the default
> INSTALLDIR location to the program files folder, and people forget to make
> it conditional, with a condition like NOT INSTALDIR. You may find that if
> you set INSTALLDIR on an msiexec command line it would also get
> overwritten. The NOT INSTALLDIR condition just means "don't set it to
> default if it's already set".
> >
> > Phil Wilson
> >
> >
> > On Mon, Aug 26, 2013 at 3:42 AM, Blair Murri wrote:
> >
> > > "Adding" is not overridding, it is creating.
> > > That would suggest that there is no InstallDir value at
> > > HKLM\Software\Acme\Foobar 1.0 Do you have a 32-bit MSI and are trying
> > > to read a 64-bit registry location, per chance? Or vice versa?
> > >
> > > > From: rob...@softdev.net
> > > > To: wix-users@lists.sourceforge.net
> > > > Date: Mon, 26 Aug 2013 06:31:51 +
> > > > Subject: [WiX-users] RegistrySearch example in tutorial
> > > >
> > > > I'm a novice user, going through Getting Started. I cannot get the
> > > RegistrySearch to work, or FILEEXISTS - both from "Where to Install?"
> > > page in your tutorial.
> > > >
> > > > I suspect it is because this element:
> > > >
> > > >> > Key='Software\Acme\Foobar 1.0' Name='InstallDir' />
> > > >
> > > >
> > > > is overridden by the subsequent
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Meaning that if the registry sets a directory outside of program
> > > > files,
> > > then it seems to not work because later in the wxs file it is
> > > contained within ProgramFilesFolder. Logging reveals it is overridden:
> > > >
> > > > MSI (c) (50:AC) [16:21:36:966]: PROPERTY CHANGE: Adding INSTALLDIR
> > > property. Its value is 'C:\Program Files (x86)\... etc
> > > >
> > > > I realise the file is not read sequentially.
> > > >
> > > > Regards,
> > > > Robert
> > > >
> > > --
> > >
> > > > Introducing Performance Central, a new site from SourceForge and
> > > > AppDynamics. Performance Central is your source for news, insights,
> > > > analysis and resources for efficient Application Performance
> Management.
> > > > Visit us today!
> > &
Re: [WiX-users] RegistrySearch example in tutorial
If you are intending to use the 32-bit registry in a 64-bit platform in
RegEdit, you need to start from the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node
(which is the 32-bit HKEY_LOCAL_MACHINE\SOFTWARE key).
You make TARGETDIR conditional by setting a property by that name to the full
path (hopefully with a backslash ('\') at the end) before costing starts in
whatever sequence starts first. Same with INSTALLDIR. Subdirectories will
automatically use the path set for their parents if a path is not presupplied.
During costing, properties will be created for all directories that didn't
already have properties (and each one will be set to the full path of that
directory).
AppSearch, et. al. will set the property you specify. So will the command-line.
By default, the *Search actions will override the command-line.
> From: rob...@softdev.net
> To: wix-users@lists.sourceforge.net
> Date: Mon, 26 Aug 2013 23:52:18 +0000
> Subject: Re: [WiX-users] RegistrySearch example in tutorial
>
> Thanks for both replies. I am indeed on a x64 machine and have no idea how to
> distinguish between x86/x64 registries. I've probably created the key in the
> wrong one. Any pointers? To open the editor, I type in "regedit"
>
> If not that, then how should I make this conditional:
>
> > >
> > >
> > >
> > >
>
> -Original Message-
> From: Phil Wilson [mailto:phildgwil...@gmail.com]
> Sent: Tuesday, 27 August 2013 4:49 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] RegistrySearch example in tutorial
>
> What often happens is that there is a custom action to set the default
> INSTALLDIR location to the program files folder, and people forget to make it
> conditional, with a condition like NOT INSTALDIR. You may find that if you
> set INSTALLDIR on an msiexec command line it would also get overwritten. The
> NOT INSTALLDIR condition just means "don't set it to default if it's already
> set".
>
> Phil Wilson
>
>
> On Mon, Aug 26, 2013 at 3:42 AM, Blair Murri wrote:
>
> > "Adding" is not overridding, it is creating.
> > That would suggest that there is no InstallDir value at
> > HKLM\Software\Acme\Foobar 1.0 Do you have a 32-bit MSI and are trying
> > to read a 64-bit registry location, per chance? Or vice versa?
> >
> > > From: rob...@softdev.net
> > > To: wix-users@lists.sourceforge.net
> > > Date: Mon, 26 Aug 2013 06:31:51 +
> > > Subject: [WiX-users] RegistrySearch example in tutorial
> > >
> > > I'm a novice user, going through Getting Started. I cannot get the
> > RegistrySearch to work, or FILEEXISTS - both from "Where to Install?"
> > page in your tutorial.
> > >
> > > I suspect it is because this element:
> > >
> > >> Key='Software\Acme\Foobar 1.0' Name='InstallDir' />
> > >
> > >
> > > is overridden by the subsequent
> > >
> > >
> > >
> > >
> > >
> > >
> > > Meaning that if the registry sets a directory outside of program
> > > files,
> > then it seems to not work because later in the wxs file it is
> > contained within ProgramFilesFolder. Logging reveals it is overridden:
> > >
> > > MSI (c) (50:AC) [16:21:36:966]: PROPERTY CHANGE: Adding INSTALLDIR
> > property. Its value is 'C:\Program Files (x86)\... etc
> > >
> > > I realise the file is not read sequentially.
> > >
> > > Regards,
> > > Robert
> > >
> > --
> >
> > > Introducing Performance Central, a new site from SourceForge and
> > > AppDynamics. Performance Central is your source for news, insights,
> > > analysis and resources for efficient Application Performance Management.
> > > Visit us today!
> > >
> > http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.c
> > lktrk
> > > ___
> > > WiX-users mailing list
> > > WiX-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
> >
> > --
> > Introducing Performance Central, a new site from SourceForge
> > and AppDynamics. Performance Central is your source for news,
> > insights, analysis and resources for efficient Application P
Re: [WiX-users] RegistrySearch example in tutorial
Thanks for both replies. I am indeed on a x64 machine and have no idea how to distinguish between x86/x64 registries. I've probably created the key in the wrong one. Any pointers? To open the editor, I type in "regedit" If not that, then how should I make this conditional: > > > > > > > > -Original Message- From: Phil Wilson [mailto:phildgwil...@gmail.com] Sent: Tuesday, 27 August 2013 4:49 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] RegistrySearch example in tutorial What often happens is that there is a custom action to set the default INSTALLDIR location to the program files folder, and people forget to make it conditional, with a condition like NOT INSTALDIR. You may find that if you set INSTALLDIR on an msiexec command line it would also get overwritten. The NOT INSTALLDIR condition just means "don't set it to default if it's already set". Phil Wilson On Mon, Aug 26, 2013 at 3:42 AM, Blair Murri wrote: > "Adding" is not overridding, it is creating. > That would suggest that there is no InstallDir value at > HKLM\Software\Acme\Foobar 1.0 Do you have a 32-bit MSI and are trying > to read a 64-bit registry location, per chance? Or vice versa? > > > From: rob...@softdev.net > > To: wix-users@lists.sourceforge.net > > Date: Mon, 26 Aug 2013 06:31:51 + > > Subject: [WiX-users] RegistrySearch example in tutorial > > > > I'm a novice user, going through Getting Started. I cannot get the > RegistrySearch to work, or FILEEXISTS - both from "Where to Install?" > page in your tutorial. > > > > I suspect it is because this element: > > > >Key='Software\Acme\Foobar 1.0' Name='InstallDir' /> > > > > > > is overridden by the subsequent > > > > > > > > > > > > > > Meaning that if the registry sets a directory outside of program > > files, > then it seems to not work because later in the wxs file it is > contained within ProgramFilesFolder. Logging reveals it is overridden: > > > > MSI (c) (50:AC) [16:21:36:966]: PROPERTY CHANGE: Adding INSTALLDIR > property. Its value is 'C:\Program Files (x86)\... etc > > > > I realise the file is not read sequentially. > > > > Regards, > > Robert > > > -- > > > Introducing Performance Central, a new site from SourceForge and > > AppDynamics. Performance Central is your source for news, insights, > > analysis and resources for efficient Application Performance Management. > > Visit us today! > > > http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.c > lktrk > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > -- > Introducing Performance Central, a new site from SourceForge > and AppDynamics. Performance Central is your source for news, > insights, analysis and resources for efficient Application Performance > Management. > Visit us today! > http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.c > lktrk ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] RegistrySearch example in tutorial
What often happens is that there is a custom action to set the default INSTALLDIR location to the program files folder, and people forget to make it conditional, with a condition like NOT INSTALDIR. You may find that if you set INSTALLDIR on an msiexec command line it would also get overwritten. The NOT INSTALLDIR condition just means "don't set it to default if it's already set". Phil Wilson On Mon, Aug 26, 2013 at 3:42 AM, Blair Murri wrote: > "Adding" is not overridding, it is creating. > That would suggest that there is no InstallDir value at > HKLM\Software\Acme\Foobar 1.0 > Do you have a 32-bit MSI and are trying to read a 64-bit registry > location, per chance? Or vice versa? > > > From: rob...@softdev.net > > To: wix-users@lists.sourceforge.net > > Date: Mon, 26 Aug 2013 06:31:51 + > > Subject: [WiX-users] RegistrySearch example in tutorial > > > > I'm a novice user, going through Getting Started. I cannot get the > RegistrySearch to work, or FILEEXISTS - both from "Where to Install?" page > in your tutorial. > > > > I suspect it is because this element: > > > >Key='Software\Acme\Foobar 1.0' Name='InstallDir' /> > > > > > > is overridden by the subsequent > > > > > > > > > > > > > > Meaning that if the registry sets a directory outside of program files, > then it seems to not work because later in the wxs file it is contained > within ProgramFilesFolder. Logging reveals it is overridden: > > > > MSI (c) (50:AC) [16:21:36:966]: PROPERTY CHANGE: Adding INSTALLDIR > property. Its value is 'C:\Program Files (x86)\... etc > > > > I realise the file is not read sequentially. > > > > Regards, > > Robert > > > -- > > Introducing Performance Central, a new site from SourceForge and > > AppDynamics. Performance Central is your source for news, insights, > > analysis and resources for efficient Application Performance Management. > > Visit us today! > > > http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > -- > Introducing Performance Central, a new site from SourceForge and > AppDynamics. Performance Central is your source for news, insights, > analysis and resources for efficient Application Performance Management. > Visit us today! > http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] RegistrySearch example in tutorial
"Adding" is not overridding, it is creating. That would suggest that there is no InstallDir value at HKLM\Software\Acme\Foobar 1.0 Do you have a 32-bit MSI and are trying to read a 64-bit registry location, per chance? Or vice versa? > From: rob...@softdev.net > To: wix-users@lists.sourceforge.net > Date: Mon, 26 Aug 2013 06:31:51 + > Subject: [WiX-users] RegistrySearch example in tutorial > > I'm a novice user, going through Getting Started. I cannot get the > RegistrySearch to work, or FILEEXISTS - both from "Where to Install?" page in > your tutorial. > > I suspect it is because this element: > >Key='Software\Acme\Foobar 1.0' Name='InstallDir' /> > > > is overridden by the subsequent > > > > > > > Meaning that if the registry sets a directory outside of program files, then > it seems to not work because later in the wxs file it is contained within > ProgramFilesFolder. Logging reveals it is overridden: > > MSI (c) (50:AC) [16:21:36:966]: PROPERTY CHANGE: Adding INSTALLDIR property. > Its value is 'C:\Program Files (x86)\... etc > > I realise the file is not read sequentially. > > Regards, > Robert > -- > Introducing Performance Central, a new site from SourceForge and > AppDynamics. Performance Central is your source for news, insights, > analysis and resources for efficient Application Performance Management. > Visit us today! > http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
