Open monty241 opened 6 years ago
Yeah, this is expected - my assemblies are not strongly signed. I won't sign my assemblies without a good reason - why do you need strongly signed versions of my assemblies?
We always use them for documented reasons. It makes it harder to get started with the package. I have created an alternative myself; was easier than making it work.
Yes, self-signing is generally the recommended solution. What do you mean documentation reasons?
Sorry, typo, "documented" or known reasons. Work and costs can be painful. But note that error is on strong-naming, not on signing.
After deploying either 0.2.0.1 or 0.3.01-pre, unit tests raise:
Better would have the NuGet made such that it does not occur.