Signing an assembly with a strong name is called assembly strong signature! In visualizing Studio.NET and. NET Framework SDK, you can assign strong names to assemblies! Assemblies with the same strong name are generally the same! Signing the program collection through strong signature can ensure the global uniqueness of the name! Because strong names rely on unique key pairs to ensure the uniqueness of names, others will not generate the same assembly name as you (different private keys generate different names). Strong names protect version inheritance of assemblies, because the uniqueness of strong names can ensure that others cannot generate subsequent versions of assemblies. Strong names provide a reliable integrity check when passing. NET framework security check can ensure that the assembly content has not been changed after generation! It should be noted that assemblies with strong names refer to other assemblies. If this assembly does not have a strong name, the benefits of an assembly with a strong name will still cause DLL conflicts! Therefore, assemblies with strong names can only refer to other assemblies with strong names.