Problem with private assembly

An application requires one or more assemblies, which may be developed by any other developer. To use that assembly, you give the reference to that assembly in your code. If the assembly is private and not present in your application directory then first it requires to copy in application directory then your application can use it.

         This solution has to major shortcomings:

1. Unnecessary storing copies of a single assembly in multiple directories, which are part of same application.
2. The copy of original assembly may not be consistent.

To remove this shortcoming .net framework provides shared assembly.