Re: Internationalization

Actually, you need to worry about all those other DLLs. And there's nothing you can do to
make them go away as dependencies. And this ignores some of the key DLLs, such as GDI32,
KERNEL32 or USER32, which introduce interesting problems if you are using, for example,
newer versions of MFC with older operating systems.
joe

On Fri, 28 Dec 2007 17:58:56 -0600, "Thomas Mooney" <tfm3@xxxxxxxxxxxxxxxxxxx> wrote:

"Pete Delgado" <Peter.Delgado@xxxxxxxxx> wrote in message
news:%232XCMyZSIHA.1528@xxxxxxxxxxxxxxxxxxxxxxx

<snipped prior message history>

The other problem I find is that there are many software installation
programs that act as if they are the only software that will be running on
a user's machine. During the installation of such a program, the installer
will overwrite settings, DLLs and environment variables that sometimes
cause all of the other software on the machine to fail.

In a sense this is the other benefit to running statically linked. Not only
am I not dependent (OK, less dependent) on the target machine, I have less
of an impact on the target machine. Because my application is more
self-contained, I don't have a need to assure myself that the dependent DLLs
are up-to-date and consequently don't have a need to carry them along with
me during installation. When my application is installed, there should be
virtually no chance of my impacting any other application(s).

Note: I acknowledge the performance advantage of several applications
sharing the same code. For the application in question this is a relative
non-factor. Moreover, it is a tradeoff that I and my client are happy to
make.

Finally, if I were writing code for a single entity who had tight control
over the software distribution and configuration of all of the workstations
in the enterprise, I might well go the other way. But that's the exact
opposite of the circumstance for this particular application.

TFM3
Joseph M. Newcomer [MVP]
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.

Relevant Pages

  • Re: Internationalization
    ... During the installation of such a program, ... am I not dependent on the target machine, I have less ... if I were writing code for a single entity who had tight control ...
    (microsoft.public.vc.mfc)
  • Re: test whether ocx is registered from VB, possible?
    ... Microsoft doesn't follow the KISS standard. ... Certain Microsoft DLLs seem to have dependencies upon ... that on some old installation routines. ... Both have a CLSID ...
    (microsoft.public.vb.winapi)
  • Re: Error loadin VS 2005 DLLs in Windows Vista
    ... how it will work deploying our new DLLs using Thinstall. ... fees per installation is a deal breaker for us, unless it is very afordable, ... The scenario is a Legacy VC 6.0 application which we are adding new mixed ... Have you tried a "Thinstall Solution"? ...
    (microsoft.public.vc.language)
  • [Info-ingres] FW: Patch install - DLLs in use
    ... installation. ... I'm not a windows expert but I think that if the ingres service is ... To: Paul White ... Subject: Re: Patch install - DLLs in use ...
    (comp.databases.ingres)
  • Re: HELP! Deploy Visio
    ... should have been just copying files is NOT going to ... >> How do I deploy an application built using the Visio Viewer? ... > target machine I have included all DLLs under C:\Program Files\Microsoft ... > Dynamic DLL detector to identify all used DLLs. ...
    (microsoft.public.visio.developer)