Hello, I'm currently facing a problem as a result of netstandard1.1 being included as a TargetFramework for the AppMetrics.Concurrency project. The problem is that when we reference AppMetrics in our core libraries, it tends to transitively bring down the version number of many .NET packages to versions that have security vulnerabilities due to the "Lowest applicable version" rule for dependency resolution. I may be wrong, but since all other AppMetrics projects target netstandard2.0 and up, I don't think it would be an issue to remove support for netstandard1.1 for this specific library.
Hello, I'm currently facing a problem as a result of
netstandard1.1being included as aTargetFrameworkfor the AppMetrics.Concurrency project. The problem is that when we reference AppMetrics in our core libraries, it tends to transitively bring down the version number of many .NET packages to versions that have security vulnerabilities due to the "Lowest applicable version" rule for dependency resolution. I may be wrong, but since all other AppMetrics projects targetnetstandard2.0and up, I don't think it would be an issue to remove support fornetstandard1.1for this specific library.