StrongNaming for nuget package about fsharp.control.asyncseq HOT 2 CLOSED

While having a strong named version is needed in some scenario, it make noise for normal .NET users who doesnt need it and after strong naming need to add assembly binding redirects.

As you said, to have it signed is possibile to use strongnamer in the consumer app/lib and it can be set it as development dependency too (PrivateAssets="All in fsproj or developmentDependency=true in nuspec) so is not added to dependency list of the consumer app/lib.

As a note, if strong naming need to be done, it require:

• a bump to a major version (v3), because strong naming is a breaking change
• set the assembly version to a fixed version, so doesnt break each new package.

@edud69 there was a previous version of FSharp.Control.AsyncSeq who was already strongly signed? i am checking but didnt yet found one.

from fsharp.control.asyncseq.

I don't think there was any version that was previously strongly signed also.

from fsharp.control.asyncseq.