How a shared dll (GAC) is loaded into memory and used compared to a private dll

Question

I would like to point out that I know how to add / remove assemblies to / from the GAC. I ask if anyone can explain to me how this works from a technical point of view. What is the point of placing the dll there - in terms of saving resources.

Regards rk

Answer 1

The point of placing things in the GAC is that multiple applications (even from different vendors) can access the same assembly. There is one place where it can be updated, and all applications that can correctly access this version can use it. You also know that all assemblies in the GAC are digitally signed, so you know where the code came from (for example, MS).

As for loading into memory. Each application will have to download it independently.

Answer 2

This question provides a good argument for using the GAC, where you can avoid it.

And this question gives a couple of links to GAC demystification articles that can help you with the solution.