Open akoeplinger opened 2 months ago
@akoeplinger do you plan to handle this and what timeline are you looking to tackle this in?
I don't plan to handle this as I'm not familiar with the aspnetcore codebase, I just had to disable the warning to unblock codeflow.
@adityamandaleeka most of the code where the obsolete constructor is used is under your team's ownership. Leaving it up to you to prioritize and address.
In https://github.com/dotnet/aspnetcore/pull/56655 I had to disable the new SYSLIB0057 warning for the obsolete X509Certificate2 constructors (see https://github.com/dotnet/docs/issues/41662 for details) to unblock the dependency flow.
These suppressions should be reverted and the obsolete usages replaced.