GACUTIL.EXE is no longer supplied/installed along with Visual Studio, instead, it has been moved into the Windows SDK v7.1. So to install a DLL into the GAC for .NET 4.0 (or anything after v1.1 I believe) you must first download and install the SDK. Once you have done this you must locate the relevant version of GACUTIL from the four possible locations:
- Program FilesMicrosoft SDKsWindowsv7.1Bin
- Program FilesMicrosoft SDKsWindowsv7.1Binx64
- Program FilesMicrosoft SDKsWindowsv7.1BinNETFX 4.0 Tools
- Program FilesMicrosoft SDKsWindowsv7.1BinNETFX 4.0 Toolsx64
The first two are for registering DLLs to be used in .NET 3.5 or earlier, with the first being for x86 and the second for x64 versions.
The second two are for registering DLLs to be used in .NET 4.0, again with the first being for x86 and the second for x64 versions.
With the release of .NET 4.0 the framework now has two GACs, this stackoverflow post explains why.
As part of his fantastic ‘What is .NET standard‘ presentation at DDD12, Adam Ralph provided an amazing amount of detail in such a short amount of time. One of the most valuable points, which is completely obvious when you think about it, is how you should work with .NET standard when creating libraries. NET standard now comes in a multitude of flavours: currently 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6 and 2.0. When starting out . . .
If you’re trying to access a class library (.NET Standard) from a traditional console application (in VS2017 those can be found under ‘Windows Classic Desktop’) you will run into problems; which can feel a little strange for something that was pretty simple in VS2015 and earlier. You can add a reference to the class library project (Resharper will even volunteer to add the dependency / namespace reference if you don’t already have it). But the . . .