Support Nito.Asyncex. StrongNamed

[tangdf]

[StephenCleary]

Short answer: this is a known issue. I have no plans to add strong-naming to AsyncEx now, for reasons described here. See also #2. If Microsoft would provide better tooling and guidance for strong naming libraries without causing massive maintenance headaches, then I would be willing to reconsider.

A Short History of Strong Naming in AsyncEx:

• AsyncEx v2 was strong named. Endless problems ensued and only grew as the library's popularity grew. The strong naming was removed in v3.
• AsyncEx v4 had a separate library that was strong named. More problems ensued to the point it became a maintenance burden. This strong named option was also removed.
• AsyncEx v5 (prerelease) was public signed for a release or two. I had high hopes that public signing would work around the problems with strong naming, but it did not fix a worthwhile amount of the problems with strong naming, so the public signing was also removed.

I still think the .NET ecosystem would be better served by a service that auto-signs packages following a semantic versioning approach. So far, I have not had time to write this service. In the meantime, the Strong Naming Toolkit and StrongNameSigner are still available.