Aug 12, 2009 · The Global Assembly Cache (GAC) is a folder in Windows directory to store the .NET assemblies that are specifically designated to be shared by all applications executed on a system. Assemblies can be shared among multiple applications on the machine by registering them in global Assembly cache(GAC).

Jun 6, 2011 · In other words, you want to register your DLL in the GAC if multiple applications (on the same machine, of course) will share the DLL. From your comments, however, I want to mention a few more things: You may have registered the DLL incorrectly; once your DLL is in the GAC, you should be able to add it from the same list where all the GACed ...

So the solution described shows the advantage of putting third-party assemblies into GAC during the development. It doesn't related to production. As you may find, installation into GAC is mainly intended to solve the problem of location of required assemblies (dependencies).

I think the GAC is most useful if you have to have multiple versions of your application running at one time, each of which needs to load a different version of the same shared library. Even then, if the two application versions are in different directories then as long as you keep their binaries separate you still don't need the GAC.

GAC is really a repository for Microsoft common .NET libraries. Yes, they let developers use it too, but as a rule of thumb, if you don't need GAC, don't use it. keep things simple and local if it doesn't hurt. I would consider GAC only for performance reasons, for example if you have some huge assemblies, try to place them into GAC and NGEN ...

Nov 5, 2014 · I have installers and I can place the assemblies into GAC easy enough. I control my installers and my installers just have to write a registration file to a specific location to register with the parent program, the rest of my program can be placed wherever I want. The question is if I SHOULD place my assemblies in GAC (or some of them at least)...

May 18, 2010 · 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.

I have a component that I need to add to the GAC. I'm running Windows 7 64-bit, and in an effort to troubleshoot an issue (SSIS 2005 isn't recognizing the DLL), I'm trying to make sure I have the DLL (.NET 4.0) registered in the proper GAC. So here are my questions: Where are the physical locations in Windows 7 for both 64bit and 32bit GACs?

Apr 17, 2010 · For example, if both .NET 1.1 and .NET 2.0 shared the same GAC, then a .NET 1.1 application, loading an assembly from this shared GAC, could get .NET 2.0 assemblies, thereby breaking the .NET 1.1 application. The CLR version used for both .NET Framework 2.0 and .NET Framework 3.5 is CLR 2.0.

Jun 23, 2015 · Beginning with ODP.NET 10.1.0.3, the Oracle installer will register the following publisher policy DLLs in the Global Assembly Cache (GAC) that redirect 9.2, 10.1 and 10.2 ODP.NET applications to use the last installed version of ODP.NET: Policy.9.2.Oracle.DataAccess.dll and Policy.10.1.Oracle.DataAccess.dll