Building VB.NET Assemblies

Every VB.Net assembly has four parts in it. They are a user friendly name, a version number, culture setting, and a public key token. The version of an assembly by default would be 0.0.0.0 if you do not set any.

You can set the version number by placing the code <Assembly: AssemblyVersion (“1.0.30.3”)> at the top of the source code. For this you have to import the System.Reflection namespace too. The culture setting in the assembly localizes the assembly for a particular language.

The last part of the assembly is the public key and it is unique. Since the public key is very large a public key token which is an 8 byte value is used. Each public key token corresponds to one public key. This gives a strong name to an assembly. A public and private key pair is needed for a strong assembly.

The private key is for generating the digital signature for an assembly. Use the code <Assembly: AssemblyKeyFile(“..\filenameKey.snk”)> at the top of the project source so that the assembly gets a strong name while it is built.







______________________________________________________

SetApp - 100 Apps for everything you ever wanted to do on Mac

Recommended Resource



| Managing .NET Assemblies | Understanding Assemblies in .NET| Reflection and Assemblies in .NET | Advantages of using ASP.NET Assemblies | Understanding Assemblies in VB.NET | Building VB.NET Assemblies |



_______________

FREE Subscription

Stay Current With the Latest Technology Developments Realted to .NET. Signup for Our Newsletter and Receive New Articles Through Email.

Name:

Email:

Note : We never rent, trade, or sell our email lists to anyone. We assure that your privacy is respected and protected.


 

“Amazon and the Amazon logo are trademarks of Amazon.com, Inc. or its affiliates.”

| Privacy Policy for www.dotnet-guide.com | Disclosure | Contact |

Copyright - © 2004 - 2019 - All Rights Reserved.