Consider strong-naming with published SNK

[TetsujinOni]

To allow organizations which require strong-named assemblies so they can use code-signing for their internal projects to consume Pri.LongPath, consider strong-naming the package.

[SchreinerK]

@TetsujinOni IMHO organizations should build binaries with own key if this is requiered.
But I am with you, there could be also an alternate NuGet package with a strong name.

• see also what Microsoft says about strong names
• maybe a option: StrongNameSigner

[TetsujinOni]

https://docs.microsoft.com/en-us/dotnet/framework/app-domains/strong-named-assemblies was the source of my suggested path of using a published SNK for signing the open source library, to enable the local build reference compatibility with the nuget package.

Which is, of course, why StrongNameSigner and local signing are less desirable solutions than opening an upstream project issue.