Could not load file or assembly ‘x’ or one of its dependencies. Strong name validation failed.

In some of the work I’m doing right now, I’m manipulating an assembly after compile time – having it disassembled into IL, tweaked, then re-compiled back into an assembly.

The assembly is signed and what is being done to the assembly is breaking the strong name. This is quite comforting to know; the strong name wouldn’t be . . . → Read More: Could not load file or assembly ‘x’ or one of its dependencies. Strong name validation failed.

Configuring NLog for your application when NLog is in the Global Assembly Cache (GAC)

If you have several applications that are using NLog, it can be a good idea to install NLog into the GAC and reference that.

A gotcha you must watch out for is caused by this piece of configuration from the NLog site:

<configuration>
<configSections>
<section name=”nlog” type=”NLog.Config.ConfigSectionHandler, NLog”/>
</configSections>
<nlog>
</nlog>
</configuration>

Because you are not using the strong name for the Assembly-qualified name of . . . → Read More: Configuring NLog for your application when NLog is in the Global Assembly Cache (GAC)