.Net/C# - Pros and cons using the GAC [duplicate]

This question already has answers here: Closed 12 years ago.

Possible Duplicate:

What are 开发者_JAVA百科the advantages and disadvantages of using the GAC?

I would like to hear your opinion regarding the benefits of disadvantages of using the GAC in .Net applications. To me, it looks more professional to sign & register the application dlls in the GAC. It's more secure, helps with backward compatibility, side by side installations and easy to reference for end-users. But I want to hear the other side as well.

---

It's a great idea to use the GAC for your shared assemblies but be sure to understand some of the potential drawbacks. It can also introduce extra complexity to development and deployment.

Take a look at this previous question for potential drawbacks: Why should I NOT use the GAC?

---

You'd already listed advantages, the main disadvantage to using the GAC in my view is that it gets slightly more complicated to install, you can't just copy the files in and run, and same when you want to uninstall you can't just delete one directory.

I'm assuming that it's for an assembly that will just be used by your own apps, so you don't have to worry about other peoples apps linking to it.