[Feature Request] Add .NET 6 framework support for Microsoft.Identity.Client package
See original GitHub issueIs your feature request related to a problem? Please describe.
This is related to Issue #41837. Microsoft.Identity.Client 4.44.0
package referenced in Microsoft.Data.SqlClient 4.1.0
which is reference in Microsoft.EntityFrameworkCore.SqlServer
. We have migrated our .netcore 3.1 web api to .NET6 and it is running on an on-premise IIS server which does not have .NETCoreApp 2.1 framework. Our application is not loading since there is no .NETCoreApp 2.1 framework in the server. Please refer the issue #41837 and .NETCore team confirmed this package should add the support for .NET6 framework as well since .NET5.0 also out of support.
Since .NETCore 2.1 and 5.0 frameworks are out of support , as per our organization security policy we can’t use the outdated .net framework in the production servers and it flags a security vulnerability. So we are force to uninstall the .NETCoreApp 2.1 and .NET 5.0 frameworks from server and making our application down. Please let me know if there any timeline for this feature to be added.
Describe the solution you’d like
Add .NET6.0 framework support for Microsoft.Identity.Client 4.44.0
package.
Describe alternatives you’ve considered Currently we got an exception to keep the .NETCoreApp for few months to get some resolution from Microsoft on this issue.
Additional context Please refer the screenshot of the framework dependency.
Issue Analytics
- State:
- Created a year ago
- Comments:9 (5 by maintainers)
Top GitHub Comments
Thanks for the update @ponkumarpandian. We will most likely add net6 soon, to benefit from new System.Text.Json improvements. But we will track that separately.
@bgavrilMS It was IIS configuration issues. When I had .net core 2.1 installed on the server and without having below mentioned IIS configuration my application was working fine. Once I have uninstalled .NETCore 2.1 and have only .NET Core runtime installed application started breaking. After installed below IIS components , and reinstall the .NET 6 run time it started working.
We can close this issues and there is no changes required on this repo.