Who is using dll

Home All Products Forum Groups. Getting Started. Expand search. Log in Account Management. Ask a Question. How to find out what DLLs are loaded by a process. Environment Manager.

Applies to. Martin Ba Martin Ba Gerhard Powell 5, 5 5 gold badges 48 48 silver badges 57 57 bronze badges. Ivaylo Strandjev Ivaylo Strandjev Bali C Bali C Since this is a programming site and not helpdesk, I suspect that the OP is interested in the APIs that this Process Explorer is using, rather than the tool itself. Well 4 other people have posted PE as a solution, so we will soon see if this is what the OP is after.

Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Does ES6 make JavaScript frameworks obsolete?

Podcast Do polyglots have an edge when it comes to mastering programming Featured on Meta. An assembly physically exists as a. An assembly file contains an assembly manifest, type metadata, Microsoft intermediate language MSIL code, and other resources. The assembly manifest contains the assembly metadata that provides all the information that is required for an assembly to be self-describing. The following information is included in the assembly manifest:.

The MSIL code that is contained in the assembly cannot be directly executed. By default, when you create an assembly, the assembly is private to the application. To create a shared assembly requires that you assign a strong name to the assembly and then publish the assembly in the global assembly cache.

The following list describes some of the features of assemblies compared to the features of Win32 DLLs:. When you create an assembly, all the information that is required for the CLR to run the assembly is contained in the assembly manifest. The assembly manifest contains a list of the dependent assemblies. Therefore, the CLR can maintain a consistent set of assemblies that are used in the application. In an assembly manifest, version information is recorded and enforced by the CLR.

Additionally, version policies let you enforce version-specific usage. In Win32 DLLs, versioning can't be enforced by the operating system. You must make sure that DLLs are backward compatible.

Assemblies support side-by-side deployment. One application can use one version of an assembly, and another application can use a different version of an assembly. Starting in Windows , side-by-side deployment is supported by locating DLLs in the application folder. Additionally, Windows File Protection prevents system DLLs from being overwritten or replaced by an unauthorized agent.

An application that is developed by using an assembly can be self-contained and isolated from other applications that are running on the computer. This feature helps you create zero-impact installations. An assembly is run under the security permissions that are supplied in the assembly manifest and that are controlled by the CLR.

An assembly can be developed by using any one of the supported. NET languages. For example, you can develop an assembly in Microsoft Visual C , and then use the assembly in a Visual Basic. NET project. Deploying and Configuring Applications. Run-Time Dynamic Linking. Thread Local Storage. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services.

Privacy policy. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. More information A DLL is a library that contains code and data that can be used by more than one program at the same time. Control Panel. Device driver. DLL advantages The following list describes some of the advantages that are provided when a program uses a DLL: Uses fewer resources 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.

Promotes modular architecture A DLL helps promote developing modular programs. Eases deployment and installation When a function within a DLL needs an update or a fix, the deployment and installation of the DLL does not require the program to be relinked with the DLL.

For example, the program may not run if one of the following actions occurs: A dependent DLL is upgraded to a new version. A dependent DLL is fixed. A dependent DLL is overwritten with an earlier version. A dependent DLL is removed from the computer. The following list describes the changes that have been introduced in Windows and in later Windows operating systems to help minimize dependency issues: Windows File Protection In Windows File Protection, the operating system prevents system DLLs from being updated or deleted by an unauthorized agent.

Dependency Walker checks for program files or DLLs that are not valid. Dependency Walker checks that import functions and export functions match. Dependency Walker checks for circular dependency errors. Dependency Walker checks for modules that are not valid because the modules are for a different operating system.