The Microsoft.Azure.Kusto.Language package is not strong signed. Though of limited value in modern .NET, strong-named binaries using .NET Framework can only other other strong-named binaries. As a result, the lack of strong-naming limits adoption for .NET Framework consumers.
Best practices state that if targeting .NET Framework or .NET Standard, the assembly should have a strong-name: https://learn.microsoft.com/en-us/dotnet/standard/library-guidance/strong-naming. If the name is used only for identity and not security (which would be the case in this instance). The public or public/private key can be checked in and is not secret.
This request is the result of creating an OpenTelemetry instrumentor (see open-telemetry/opentelemetry-dotnet-contrib#3591). OpenTelemetry instrumentors target .NET Framework, and are strong-named for maximum ecosystem compatibility.
The Microsoft.Azure.Kusto.Language package is not strong signed. Though of limited value in modern .NET, strong-named binaries using .NET Framework can only other other strong-named binaries. As a result, the lack of strong-naming limits adoption for .NET Framework consumers.
Best practices state that if targeting .NET Framework or .NET Standard, the assembly should have a strong-name: https://learn.microsoft.com/en-us/dotnet/standard/library-guidance/strong-naming. If the name is used only for identity and not security (which would be the case in this instance). The public or public/private key can be checked in and is not secret.
This request is the result of creating an OpenTelemetry instrumentor (see open-telemetry/opentelemetry-dotnet-contrib#3591). OpenTelemetry instrumentors target .NET Framework, and are strong-named for maximum ecosystem compatibility.