In a standard .net 4.0 installation, Gacutil is missing. They also moved the GAC from% Windir% \ assembly to% Windir% \ Microsoft.NET \ Assembly.
They did not even bother to add a "special view" for the folder in Windows Explorer, as well as for the .net 1.0 / 2.0 GAC.
Gacutil is part of the Windows SDK, so if you want to use it on your development machine, just install the Windows SDK for your current platform. Then you will find it somewhere like that (depending on the SDK version):
C: \ Program Files \ Microsoft SDKs \ Windows \ v7.0A \ bin \ NETFX 4.0 Tools
The new GAC is discussed here: .NET 4.0 introduced a new GAC, why?
If you want to install something in the GAC on a production machine, you need to do it in the "right" way (gacutil was never intended to be installed on production servers only as a development tool), Windows Installer, or with other tools. You can, for example, do this using PowerShell and the dll System.EnterpriseServices.
In the general case, based on several years of experience, I personally strongly recommended against using the GAC. Your application will always work if you decompose the DLL with each application in the bin folder. Yes, you will get several copies of the DLL on your server if you have, for example, several web applications on the same server, but it is definitely worth it to be able to update one application without violating the others (by introducing an incompatible version of the common DLL in the GAC).
Erik A. Brandstadmoen Aug 03 2018-11-11T00: 00Z
source share