[Legacy support] The strong named assembly should be done for NETFramework compatibility.
Opened this issue · 0 comments
kirexp commented
The strong name is required for assembly.
Hi. I was wondering if you could sign assembly before building nugget package from it?
I am using your package in the legacy project and when I build my own package that has a reference on NLog.RabbitMQ I get an exception.
System.IO.FileLoadException: Could not load file or assembly 'Nlog.RabbitMQ.Target, Version=2.7.7.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044)
File name: 'Nlog.RabbitMQ.Target, Version=2.7.7.0, Culture=neutral, PublicKeyToken=null'
it only appears when I am signing my packages. Unfortunately my company is obligating us to sign our packages.
Can you sign assembly using *.snk ?