Previous Topic: Common Language RuntimeNext Topic: Local and Global Assembly Cache


Strong Naming

Microsoft has introduced strong naming to improve security and prevent DLL conflicts. When a DLL is strongly named, it contains several attributes that uniquely identify it such as version number and an encryption key. The caller of a strongly named DLL must also be strongly named thus extending the security throughout the application. This ensures that the caller of a method within a DLL (assembly) will execute the one it was assembled against.