RE: [GD-Windows] DLL location

[Jon W. <hp...@mi...>]

These days, Microsoft recommends that each application install the DLLs with
the EXE. The reason for this is that DLL versioning problems have bit too
many programs too many times.

For an ActiveX control or .NET Assembly module, that's not doable, of
course, although the .NET hierarchy seems to have space for third party
code, and ActiveX controls can go in Program Files/YourNameHere and use
RegSvr32 to tell the system where to find it.

Cheers,

			/ h+


-----Original Message-----
From: gam...@li...
[mailto:gam...@li...]On Behalf Of
Pierre Terdiman
Sent: Tuesday, January 27, 2004 8:16 AM
To: gam...@li...
Subject: [GD-Windows] DLL location


Hi,

Is there a standard place where third party libraries can store their DLLs ?

We want to release a SDK whose DLLs should be accessible by both the demos
(exes in their own \demos directory) and the programmers compiling the
examples or doing their own.

The obvious solution is to copy our DLLs in the System or System32 directory
at installation time, but it doesn't sound very nice to pollute that place
with extra DLLs (it's messy enough...)

Is it better to store the DLLs in some private directory (say Program
Files\MyProduct\MyDlls), and add that directory to the path env variable ?
If yes, is there a recommended way to do that ?

Else, is there an "official" way to do that ?

Pierre




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Gamedevlists-windows mailing list
Gam...@li...
https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows
Archives:
http://sourceforge.net/mailarchive/forum.php?forum_id=555