Summary
This chapter provided essential details on naming, building, deploying, and revising assemblies. There is a wealth of information that you need to learn to properly build and distribute the software that you write with Visual Basic .NET. Consequently, your journey out of assembly purgatory has become longer than you might have initially expected.
Every assembly has a four-part name consisting of a friendly name, a version number, a culture setting, and a public key token. This four-part name gives every assembly a unique identity from the CLR's perspective. You can also control the name of an output assembly during the build process by applying the AssemblyVersion attribute and the Assembly-KeyFile attribute.
Strong names help to make ...
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.
