what difference between Private and Shared assemblies?

A private assembly is normally used by a single application, and is stored in the application's directory, or a sub-directory beneath. A shared assembly is normally stored in the global assembly cache, which is a repository of assemblies maintained by the .NET runtime. Shared assemblies are usually libraries of code 1.In private assembly all the referred DLL's will be copied into global project debug folder but in shared assembly will not. 2.Private assemblies are faster in accessing,when compare with shared assemblies 3.Memory wise shared assembly are recommended. 4.The private assembly is used when only one project need to be developed for a client but shared assembly is used when more then one project Need to be developed

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Pankaj Pandey13y ago
hello

i want to add some more line in Nayak's answer

private assembly do not need a SN key but shared assembly needs.
0
Satyapriya Nayak13y ago
A private assembly is normally used by a single application, and is stored in the application's directory, or a sub-directory beneath. A shared assembly is normally stored in the global assembly cache, which is a repository of assemblies maintained by the .NET runtime. Shared assemblies are usually libraries of code 1.In private assembly all the referred DLL's will be copied into global project debug folder but in shared assembly will not. 2.Private assemblies are faster in accessing,when compare with shared assemblies 3.Memory wise shared assembly are recommended. 4.The private assembly is used when only one project need to be developed for a client but shared assembly is used when more then one project Need to be developed
+1