Talk:Dynamic-link library
This is the talk page for discussing improvements to the Dynamic-link library article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
![]() | Computing C‑class Mid‑importance | |||||||||
|
![]() | Microsoft Windows: Computing C‑class Mid‑importance | ||||||||||||
|
![]() | Libraries C‑class | |||||||||
|
![]() | Links from this article which need disambiguation (check | fix): [[GDI]], [[lib]]
For help fixing these links, see Wikipedia:WikiProject Disambiguation/Fixing a page. Added by WildBot | Tags to be removed | FAQ | Report a problem | ![]() |
Comment on GUIDs
which places the DLL's location and its globally unique ID (GUID) in the registry. Programs can then use the DLL by looking up its GUID in the registry to find its location.
This is wrong DLLs don't have GUIDs. A DLL can have one or more components inside and those are the ones that have unique GUIDs. For example:
[HKEY_CLASSES_ROOT\CLSID\{00000105-0000-0010-8000-00AA006D2EA4}\InprocServer32] @="C:\\Program Files\\Common Files\\Microsoft Shared\\DAO\\dao360.dll"
[HKEY_CLASSES_ROOT\CLSID\{00000106-0000-0010-8000-00AA006D2EA4}\InprocServer32] @="C:\\Program Files\\Common Files\\Microsoft Shared\\DAO\\dao360.dll"
different GUIDs pointing to the same DLL. --87.196.95.140 11:05, 22 January 2007 (UTC)
User:67.10.10.66 introduced many small factual errors in his (obviously good-faith) edits, so I decided to revert them and merge the valuable additions gradually.
E.g. DLLs aren't limited to PE files (they were NE in 16-bit Windows); SYS, DRV and FO? have not