Clever Geek Handbook

What does logical grouping of modules in an assembly mean?

What does logical grouping of modules in an assembly mean? Can someone explain how the .NET CLR works with assembly?

+1


source to share


3 answers


You can organize modules using namespaces. With Namespaces, you can make one for each logical grouping of modules in your assembly.



So, if you have a Utlity assembly with some line helpers and some file helpers, you can put the line helpers in a namespace called Utility.StringHelper and the file module helper in a namespace called Utility.FileHelper .

+1


source


The dotNet assembly is a container for all executable code. A package containing executable code for your program, in other words. Perhaps your question is confusing Microsoft's term with another term. You can clarify your question.



0


source


I think you can mislead assembly (which is Microsoft .NET terminology for DLL or EXE file - binary package of compiled code) with assembly language (low-level programming languages ​​based on symbolic representations of machine code instructions below)

In the context of Microsoft .NET assemblies, logical grouping of modules means organizing your code namespaces according to their role - for example, System.Data.SqlClient

vs. System.Data.OledbClient

- and organized into an assembly (usually .DLL files) so that each assembly forms a cohesive, well-defined set of functions and classes.

For example, all Microsoft library code for working with HTTP, HTML, and other web technologies is packaged in a DLL System.Web

, and there are multiple namespaces in that DLL, so you can selectively include different parts of that technology. This minimizes the number of physical DLLs you need to manage, while the different responsibilities in those DLLs are clearly separated using namespaces.

0


source






More articles:


All Articles