st 2010 16:23
> To: wix-users@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!
&g
http://robmensching.com/blog/posts/2008/10/10/What-are-.wixlibs-and-why-
would-you-use-them
-Original Message-
From: Sohail Somani [mailto:soh...@taggedtype.net]
Sent: 23 August 2010 16:23
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Shared files/registry question
Thanks
t; SC151456
> Registered Office - Helix Building, West Of Scotland 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
> Su
ted. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland 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-u
to: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.
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
---
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
DLLs
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) -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 i
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) -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 nece
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 reg
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
Are these files being installed in a shared location? If so, the Component
GUIDs need to be the same. That's what the Component Rules are all about.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roy Riegel
Sent: Friday, June 08, 2007 4:52 PM
To: wix-users@lists.sourceforge.net
[WiX-users] Shared files question?
Scott,
If I understand you correctly, you are saying that you currently have
the same source file included in multiple components. Is that right?
If so, presumably there is something stopping you from putting the
file(s) in as many components as you nee
Scott,
If I understand you correctly, you are saying that you currently have
the same source file included in multiple components. Is that right?
If so, presumably there is something stopping you from putting the
file(s) in as many components as you need and including a ComponentRef
to it/t
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 o
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
--
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
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
SharedDllRefCount='yes' is really for occasions when someone has or will be
distributing the file in a different way, i.e. not using Windows Installer.
Windows Installer can reference count the packages that install the
component, there's no need to have the additional overhead of reference
countin
19 matches
Mail list logo
