What's Changed

• Fix issue #108 by adding the NuGet package path as a probe location for dependency resolution as well as adding other app and ref paths for Microsoft libraries.

This increases the time taken to sign assemblies because of potentially massive NuGet package directories but in terms of reliability there should never be another dependency resolution error unless you don't actually install the package (which would install int's dependencies as well).

NuGet: https://www.nuget.org/packages/Brutal.Dev.StrongNameSigner/3.6.3

Full Changelog: v3.6.2...v3.6.3