Can anyone refer me to a link that tells all about the ins and outs of using
the .exe.local file to force applications to use the local folder for
components? (or anyone have anything good or bad to say about it).

I read about in it VBPJ vol10 #7 (June 2000) article "Reduce DLL hell in
Windows 2000". I figured there was more updated info on it, and wanted to see
how it works in XP, 2003, etc.

Thanks -

Well, I've been using it for a few years now, on and off (more on now).
Specifically, I drop the gdiplus.dll I use in the local folder and use the
local.exe to force load my copy of gdiplus.dll.  I've not experiences any
problems to date.  I've also seen other developers use it for the
msdao35.dll when installing the DAO runtime.

- Kev

Show quoteHide quote

Show quote Hide quote I believe the article mentions that if the Dll has a dependancy on some
specific system dlls (forgot the names) the work-around won't work.

I have discovered that occasionally you can create a Dll (ATL/C) that also
will not work. Never really figured out why. If a dll fails - all dlls that
depend on that dll will also fail.

If you find something come back and let us know. It was never an "official"
feature of Windows, thus there is no "official" documentation. The procedure
therefore comes under the heading of "unsupported".

It can be traced back to a development hack that were in the Beta versions -
and somehow got shipped. It was and is real handy for testing multiple
components side-by-side.

-ralph

Why ?? (Path/File access error (Error 75)
VB.NET or C++.NET or C#
Password Change
Using the replace command, please help
NTFS File Access in VB6
Sub or Function is not defined
How to open a chm file nicely ?
Testing for "Access Denied" without trying to change the file
Control similar to MS Access List Box
write to disk and permissions