Dll registration in GAC.

The main reason to load your assemblies into the GAC is versioning. GAC centralizes versioning at the machine level where it can be controlled by the system administrator.

If the GAC is not used, then each application has to deal with its own versioning issues including updates.

Using the GAC can also improve start-up times for large applications because the CLR only needs to verify the signatures of assemblies once on installation, rather than each time the assembly loads.

However, I think it's fair to say that GAC registration is only advantageous in a minority of cases and, as there are a number of complications, most installations don't bother with it nowadays.

2 Replies

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

Vulpes14y ago
Accepted answer
The main reason to load your assemblies into the GAC is versioning. GAC centralizes versioning at the machine level where it can be controlled by the system administrator.

If the GAC is not used, then each application has to deal with its own versioning issues including updates.

Using the GAC can also improve start-up times for large applications because the CLR only needs to verify the signatures of assemblies once on installation, rather than each time the assembly loads.

However, I think it's fair to say that GAC registration is only advantageous in a minority of cases and, as there are a number of complications, most installations don't bother with it nowadays.
Sreekanth Reddy13y ago
If we register it comes under Shared Assembly type.
If we dint register it comes under Private assembly.