Deploying Assemblies
So far, you have learned about the four parts that make up an assembly name as well as the mechanics for building an assembly with a version number and a strong name. Now let's move on to your options for deploying assembly DLLs on a developer workstation or a production machine.
The four-part name of an assembly is location independent. That is, no part of the name of an assembly DLL tells the CLR or a hosting application anything about the location of the actual assembly file. This location independence provides a valuable degree of flexibility, because a single assembly DLL can be deployed in several different ways and in many different places. It also means that the CLR must use something other than the assembly name ...
Get Building Applications and Components with Visual Basic .NET now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
