I don't think it's all that common in 3rd party tools. MSI would need a lot
of new infrastructure for dealing with upgrades, updates, msp patches,
having the file used by features that could be uininstalled, what installer
component to associate it with, what to repair, etc. If it's a side-by-side
thing (or assembly etc) there might be a way to re-arrange folder structures
to minimize requirements for that file everywhere, but you've probably
looked at that already.
--
Phil Wilson [MVP Windows Installer]
----
[quoted text, click to view] "Steve McLellan" <sjm.NOSPAM AT fixerlabs DOT com> wrote in message
news:#rH4WLWLEHA.3712@TK2MSFTNGP10.phx.gbl...
> OK, thought as much. It swells the file size unacceptably. Presumably this
> can be done either manually or using one of the commercial tools out
there.
>
> "Phil Wilson" <Phil.Wilson@unisys.spamcom> wrote in message
> news:ufxVvhVLEHA.2400@tk2msftngp13.phx.gbl...
> > There isn't a way to do that in the IDE, so unless having the file four
> > times is a problem, just let it do it.
> > --
> > Phil Wilson [MVP Windows Installer]
> > ----
> > "Steve McLellan" <sjm.NOSPAM AT fixerlabs DOT com> wrote in message
> > news:uJxaquRLEHA.3300@TK2MSFTNGP10.phx.gbl...
> > > Hi,
> > >
> > > Is there a way to add a file multiple times to an Installer project
and
> > get
> > > the MSI compiler not to package that file multiple times? It seems to
me
> > > it'd make more sense for it just to set up four locations to install a
> > > single file to, rather than packing the file four times each with its
> own
> > > installation location. At least with my settings, the former seems to
be
> > > happening. Any help much appreciated because delving around in Orca is
a
> > > soul destroying experience.
> > >
> > > Steve
> > >
> > >
> >
> >
>
>