@lists.sourceforge.net
Subject: Re: [WiX-users] Shared files/registry question
Thanks for clarifying. It is not that complex yet but just for my
curiosity, would it be possible for you to outline the benefits of
wixlib vs MSM?
Thanks!
On 10-08-23 7:04 AM, Pally Sandher wrote:
ComponentRef
: Blair [mailto:os...@live.com]
Sent: Friday, August 20, 2010 1:12 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: RE: [WiX-users] Shared files/registry question
wixlib
-Original Message-
From: Sohail Somani [mailto:soh...@taggedtype.net]
Sent: Thursday, August 19
Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Sohail Somani [mailto:soh...@taggedtype.net]
Sent: 21 August 2010 06:11
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Shared files/registry question
Awesome, thanks. I'm probably going to stick
wixlib
-Original Message-
From: Sohail Somani [mailto:soh...@taggedtype.net]
Sent: Thursday, August 19, 2010 1:14 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Shared files/registry question
Hi,
I have 4 products for which I need installers. Each installer requires 3
Actually, wixlib and ComponentGroup/ComponentGroupRef.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Friday, August 20, 2010 1:12 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: RE: [WiX-users] Shared files/registry question
wixlib
-Original
: Friday, August 20, 2010 1:12 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: RE: [WiX-users] Shared files/registry question
wixlib
-Original Message-
From: Sohail Somani [mailto:soh...@taggedtype.net]
Sent: Thursday, August 19, 2010 1:14 PM
To: wix-users
Hi,
I have 4 products for which I need installers. Each installer requires 3
DLLs from another of my products.
In my reading on the Internets, it appears that the right way to share
these DLL components is to use a merge module. However, the WiX way
appears to be to use a ComponentRef.
Bob Arnson wrote:
Yeah, I've found this article before ... but how would I do this within
my app? Do I have to create multiple (identical) File-elements like
this:
Yes. You can use CopyFile to install one and copy it elsewhere but it's
about the same amount of work and CopyFile isn't
Bob Arnson wrote:
I didn't find an obvious way to include a file only once in the MSI and
install it to serveral locations ...
Generally you don't. Instead, you can use WiX's support for smart
cabbing so that only a single copy of the file is included in your MSI
package regardless of
Henning Eiben wrote:
Yeah, I've found this article before ... but how would I do this within
my app? Do I have to create multiple (identical) File-elements like this:
Yes. You can use CopyFile to install one and copy it elsewhere but it's
about the same amount of work and CopyFile isn't
Hi,
I'm fairly new to wix, and I want to create a msi-file to distribute my
.net application. My app consists of several components, which require
certain assemblies. These assemblies are required in the same folder as
the application (I don't want to place them in the GAC right now).
So I have
Henning Eiben wrote:
I didn't find an obvious way to include a file only once in the MSI and
install it to serveral locations ...
Generally you don't. Instead, you can use WiX's support for smart
cabbing so that only a single copy of the file is included in your MSI
package regardless of
Hello All,
This has got to be a common problem with a known solution.
We are installing 35 - 40 files into a \system\bin directory in an XP
Windows environment with two separate but similar module WIX/MSI
installers.
By design, it is possible for the user to install this file list once or
In our product, we have a bunch of features that are usually all
installed on the same machine, but were designed to be able to be
installed as stand alone programs on separate machines. As a result,
there are a bunch of files that are shared between the different
features. Currently I have all
Put any components that can be shared into a shared folder. The just list the
required components
under whichever features need them. It's OK to have components under multiple
features. Windows
Installer will take care of it for you.
Rob
Scott Sam wrote:
In our product, we have a bunch
on the right track so far?
Regards,
Richard
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam
Sent: Wednesday, March 14, 2007 11:12 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Shared files question?
In our product, we
than one place.
Am I on the right track so far?
Regards,
Richard
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam
Sent: Wednesday, March 14, 2007 11:12 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Shared files
Ed Abshire wrote:
I have a question concerning how I can get a set of shared files into
2 different locations.
Separate products can install shared files into different directories
but a single product can install them to just one.
--
sig://boB
http://bobs.org
I have a COM DLL that I want to place in a common place for all products
installed by my company. E.g. \Program Files\Company Name\Common
For the Component I set SharedDllRefCount=yes.
I'm wondering about the best way to install and how the GUID for the
component is involved. Do I use the
PROTECTED] On Behalf Of Scott Palmer
Sent: 25 January 2007 19:39
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Shared files
I have a COM DLL that I want to place in a common place for all products
installed by my company. E.g. \Program Files\Company Name\Common
For the Component I
On 1/25/07, Mike Dimmick [EMAIL PROTECTED] wrote:
...
For best results, you should ensure that any common files are members of
the same component (i.e. have the same component GUID) in all packages
that distribute them. Further, the component should have the same
composition (*exactly* the
Scott Palmer wrote:
One follow-up question regarding the composition of a Component. The
rules say to only have one .exe, .dll, or .ocx per component. I'm
not sure what the motivation is for that in the case of non-shared
files, e.g. non-COM DLLs. It certainly makes the WiX source a lot
22 matches
Mail list logo
