A DLL is a library that contains code and data that can be used by more than one program at the same time. For example, in Windows operating systems, the Comdlg32 DLL performs common dialog box related functions. Each program can use the functionality that is contained in this DLL to implement an Open dialog box.
It helps promote code reuse and efficient memory usage. By using a DLL, a program can be modularized into separate components. For example, an accounting program may be sold by module.
Each module can be loaded into the main program at run time if that module is installed. Because the modules are separate, the load time of the program is faster. And a module is only loaded when that functionality is requested. Additionally, updates are easier to apply to each module without affecting other parts of the program. For example, you may have a payroll program, and the tax rates change each year.
When these changes are isolated to a DLL, you can apply an update without needing to build or install the whole program again.
The following list describes some of the files that are implemented as DLLs in Windows operating systems:. An example of an ActiveX control is a calendar control that lets you select a date from a calendar. An example of a. Each item is a specialized DLL. When multiple programs use the same library of functions, a DLL can reduce the duplication of code that is loaded on the disk and in physical memory.
It can greatly influence the performance of not just the program that is running in the foreground, but also other programs that are running on the Windows operating system. A DLL helps promote developing modular programs. It helps you develop large programs that require multiple language versions or a program that requires modular architecture. An example of a modular program is an accounting program that has many modules that can be dynamically loaded at run time.
Additionally, if multiple programs use the same DLL, the multiple programs will all benefit from the update or the fix. This issue may more frequently occur when you use a third-party DLL that is regularly updated or fixed.
The program is no longer self-contained, and the program may experience problems if the dependency is broken. For example, the program may not run if one of the following actions occurs:. These actions are known as DLL conflicts. If backward compatibility is not enforced, the program may not successfully run. The following list describes the changes that have been introduced in Windows and in later Windows operating systems to help minimize dependency issues:.
In Windows File Protection, the operating system prevents system DLLs from being updated or deleted by an unauthorized agent. Private DLLs use version-specific information or an empty. Then, for new programs, add version-specific information to the DLL. For old programs, use an empty. Each method tells the operating system to use the private DLLs that are located in the program root folder.
Several tools are available to help you troubleshoot DLL problems. The following tools are some of these tools. When you open a program in Dependency Walker, Dependency Walker does the following checks:. It may help prevent and correct DLL problems that may occur in the future.
Dependency Walker is located in the following directory when you install Visual Studio 6. The following list describes the utilities that make up the DUPS tool:.
This utility enumerates all the DLLs on the computer and logs the information to a text file or to a database file. This utility compares the DLLs that are listed in two text files and produces a third text file that contains the differences. This utility loads the text files that are created by using the Dlister.
This section describes the issues and the requirements that you should consider when you develop your own DLLs. The two methods of linking are load-time dynamic linking and run-time dynamic linking. In load-time dynamic linking, an application makes explicit calls to exported DLL functions like local functions.
To use load-time dynamic linking, provide a header. When you do this, the linker will provide the system with the information that is required to load the DLL and resolve the exported DLL function locations at load time. When you use run-time dynamic linking, you do not need an import library file.
The following list describes the application criteria for when to use load-time dynamic linking and when to use run-time dynamic linking:. If the initial startup performance of the application is important, you should use run-time dynamic linking. In load-time dynamic linking, the exported DLL functions are like local functions.
This makes it easy for you to call these functions. In run-time dynamic linking, an application can branch to load different modules as required. It is important when you develop multiple-language versions. When you create a DLL, you can optionally specify an entry point function. The entry point function is called when processes or threads attach themselves to the DLL or detached themselves from the DLL. You can use the entry point function to initialize data structures or to destroy data structures as required by the DLL.
Additionally, if the application is multithreaded, you can use thread local storage TLS to allocate memory that is private to each thread in the entry point function. The following code is an example of the DLL entry point function. When the entry point function returns a FALSE value, the application will not start if you are using load-time dynamic linking.
If you are using run-time dynamic linking, only the individual DLL will not load. The entry point function should only perform simple initialization tasks and should not call any other DLL loading or termination functions.
For example, in the entry point function, you should not directly or indirectly call the LoadLibrary function or the LoadLibraryEx function. Additionally, you should not call the FreeLibrary function when the process is terminating.
I think this is what you're after at least for Windows 7. If you are targeting different windows versions with your application, it is a really good idea to set up a virtual test environment for each of the primary target platforms, for example, using VMware , MS Virtual PC or Oracle Virtual Box.
If you then still need the list of all available DLLs, just look in the windows folders after a fresh install in the virtual machine by yourself. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more.
Where to find list of default dll files available on Windows XP, Vista, 7, Ask Question. Asked 11 years, 6 months ago. Active 3 years, 11 months ago. Viewed 8k times. Rabarberski Rabarberski I'm not really sure how useful that would be. In addition to what DLLs are available in a default install, you also have to worry about what versions they are. The application might use a function that was added to a DLL sometime after the initial release.
This seems like a question only the authors of py2exe could answer. Add a comment. Active Oldest Votes. And here's the Windows XP version.
Skilldrick Skilldrick Doc Brown Doc Brown
0コメント