Assemblies deployed in the global assembly cache must have a strong name
In ASP.NET, assemblies contain metadata called assembly manifest which includes info about the assembly version, author, security requirements needed to run the assembly. All this info can be accessed in ASP.NET from the System.Reflection namespace. Other than that, assemblies in ASP.NET are collections of one or more files that can be an exe or a dll, also there are private and shared assemblies in ASP.NET. Assemblies usually get placed in the bin directory, however shared assemblies go into the GAC folder
There are total 2 types of assemblies 1. Private Assembly Private assembly are created each time in the folder so it increases the file size and Not safe. 2. Shared / Public Assembly Shared assembly can reside in common area called GAC which is .net assembly repository. Not created everytime u have to just register it with the GAC and add reference and use that
Each computer on which the common language runtime is installed has a machine-wide code cache called the global assembly cache (GAC). Assemblies deployed in the global assembly cache must have a strong name. A developer tool named "Global Assembly Cache tool" (Gacutil.exe), provided by the .NET Framework SDK can be used to deploy assemblies to GAC. The global assembly cache stores assemblies specifically designated to be shared by several applications on the computer. It provides us the way to overcome "DLL Hell" problem also.
The official answer is %windir%\assembly But that is just the registered assemblies. Don't do anything in the folder manually, use the API or the gacutil tool. If you are looking for the big list of files it is probably at the subdirectories of %windir%\assembly\GAC_MSIL
Dunloy GAC was created in 1908.
Castlewellan GAC was created in 1905.
Kilrea GAC was created in 1956.
GAC Toyota was created in 2004.
The population of GAC Toyota is 5,600.
Greenlough GAC was created in 1939.
Longstone GAC was created in 1945.
Portaferry GAC was created in 1912.