mailing list archives
Re: Fwd: Re: Double clicking on MS Office documents from Windows Explorer mayexecute arbitrary programs in some cases
From: Brett Glass <brett () LARIAT ORG>
Date: Thu, 21 Sep 2000 16:56:15 -0600
I was very hopeful when I read this.
Unfortunately, while it is useful, it does not seem to be a solution
to the problem at hand. It does provide a good way to avoid DLL name
collisions and version conflicts by allowing each app to keep a preferred
version in its own directory.
But it does not remove "." from the search path if the required DLL
is not found there. As the last paragraph says, the "normal" search
path is used.
Darn. So close and yet so far.
At 11:43 AM 9/20/2000, Chip Andrews wrote:
More resources for a possible solution for the MS Office document issue....
"Activating DLL/COM Redirection
DLL/COM redirection is activated on an application-by-application basis by
the presence of a ".local" file. The ".local" file is an empty file in the
same directory as the application's .exe file, with the same name as the
application's .exe file with ".local" appended to the end of the name.
For example, to activate DLL/COM redirection for an application called
"myapp.exe," create an empty file called "myapp.exe.local" in the same
directory where myapp.exe is installed.
Once DLL/COM redirection is activated, whenever the application loads a DLL
or an OCX, Windows looks first for the DLL or OCX in the directory where the
application's .exe file is installed. If a version of the DLL or OCX is
found in the directory where the application's .exe file is installed, the
application uses it regardless of any directory path specified in the
application or the registry. If a version of the DLL or OCX is not found in
the directory where the application's .exe file is installed, the normal
search path or server path is used.
Chip Andrews, MCSE+I, MCSD, MCDBA
Clarus Corporation; www.claruscorp.com
andrewsc () claruscorp com