Best Practice - Use of DLL

 Abstract - best practise of creating dll
A dynamic-link library (DLL) is shared code and data that an application can load and call at run time. Advantages of using DLLs include reduced code footprint, lower memory utilization due to single-copy-sharing, flexible development and testing, modularity, and functional isolation. 

 

Use of DLL (Dynamic Link Library) - http://www.devasp.net/net/articles/display/342.html

 

Here are the key points that will guide you in understanding DLL.

• When we want to hide our code from the user then we make DLL (Dynamic Link Library) and add these in other application now no body can open this.
• When we want to use same code in different applications (REUSABILITY) then we make DLL of that code and add that code in other applications.
• When you want to use Functions of C# in Vb.net then you will make DLL of C# and add this library in VB.net and can easily use its functions.

 

Advantages of Using DLLs
http://msdn.microsoft.com/en-us/library/dtba4t8b(v=VS.100).aspx

Upgrades to the DLL are easier. When the functions in a DLL change, the applications that use them do not need to be recompiled or relinked as long as the function arguments and return values do not change. In contrast, statically linked object code requires that the application be relinked when the functions change.

 

Saves disk space. Many applications can share a single copy of the DLL on disk. In contrast, each application built with a static link library has the library code linked into its executable image as a separate copy.