Weak-named vs Strong-named .NET components

Difference between Weak-named .NET components and Strong-named .NET components

S.No	Weak-named .NET components	Strong-named .NET components
1	Weak names are not guaranteed to be unique and thus cannot be shared without potentially causing conflicts.	Strong names are digitally signed and provide a public key that ensures there are no conflicts.
2	Weak-named .NET components must be individually copied to the /bin directories of the Web applications where they are used.	Strong-named .NET components can be copied into the server’s GAC
3	.NET components with weak names can call unmanaged code (such as COM components) and thus causes potential conflicts with dependencies.	Furthermore, .NET components with strong names cannot call unmanaged code (such as COM components) and thus avoid potential conflicts with dependencies.