Loading
What is the difference between a private assembly and a shared assembly?
9 Answers
A Private assembly is an assembly which is available only for a specific application where they are kept.Shared application is a public application which is shared by multiple application.In order to share an assembly it must be built for the purpose by giving a cryptographically strong name while on the other end name of the private assembly must be unique.
Sonakshi SinghPosted Dec 12, 2011, 2:27 AM
Private assembly is used in a single application and no need to register in GAC
while shared assembly can be shared by multiple applications and need to register in GAC
with strong name
while shared assembly can be shared by multiple applications and need to register in GAC
with strong name
Pankaj RanaPosted Dec 8, 2011, 8:51 AM
private assembly means one assembly may use for multiplle applications.
shared assembly means more than one assembly used for one application.
murali krishnaPosted Dec 1, 2011, 8:27 AM
http://www.c-sharpcorner.com/uploadfile/72d20e/concept-of-shared-assembly-in-net/
Deepak DwijPosted Nov 28, 2011, 6:22 PM
A private assembly is normally used by a single application, and is stored in the application's directory.
A shared assembly is normally stored in the global assembly cache.
Private assembly resides under folder structure and can be accessible within the application. Shared assembly resides in GAC and shared among multi files.
Private assembly doesn't required strong name whereas Shared assembly requires strong name and registed to GAC.
Private assembly doesnot contain publicKeyToken into its CLI code whereas Shared assembly contains publicKeyToken in CLI code
A shared assembly is normally stored in the global assembly cache.
Private assembly resides under folder structure and can be accessible within the application. Shared assembly resides in GAC and shared among multi files.
Private assembly doesn't required strong name whereas Shared assembly requires strong name and registed to GAC.
Private assembly doesnot contain publicKeyToken into its CLI code whereas Shared assembly contains publicKeyToken in CLI code
Vineet Kumar SainiPosted Nov 19, 2011, 7:13 AM
Private assembly is use in single project and in shared assembly we keep the dll in GAC where multiple project can access dll.
Puneet SharmaPosted Nov 10, 2011, 1:16 AM
the main difference is dll is pleased in same project folder in private assembly but in shared assembly dll placed in GAC (global assembly catche ) so faster accessing private assembly and also memory occupied is more , so single application better to use private .shared assembly slower compare to private ,but memory occupied is low.
balakrishna pulaparthiPosted Nov 7, 2011, 3:16 AM
Location and visibility: A private assembly is normally used by a single application, and is stored in the application's directory, or a subdirectory 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 which many applications will find useful, e.g. the .NET framework classes.
Versioning: The runtime enforces versioning constraints only on shared assemblies, not on private assemblies.
Prabhu RajaPosted Nov 5, 2011, 6:15 AM