You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some hours ago Microsoft released version 2.3.0 of both Microsoft.AspNetCore.Mvc.Razor and Microsoft.AspNetCore.Mvc.TagHelpers with a dependency on version 8 of some helper libraries, like Microsoft.Extensions.Caching.Memory, instead of version 2.
This is causing problems compiling and running some of our older applications since it implicitly forces an upgrade on libraries like Microsoft.Extensions.Options or Microsoft.Extensions.Logging, which have some significant breaking changes from version 2 up to 8.
The fix is to change de project dependencies and ensure these libraries are fixed on version 2.2.0. instead of 2.x
What I'm finding odd is that these libraries aren't maintained anymore and this doesn't look like to be made on purpose, specially a release 7 years later.
Expected Behavior
Keep the dependencies of Microsoft.Extension.* libraries on version 2 instead of upgrading to version 8.
Steps To Reproduce
No response
Exceptions (if any)
No response
.NET Version
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
This is intentional, see #58598. 2.2 has been out of support since 2019, and the netcoreapp2.1 TFM since 2021. Apps should still work when targeting .NET Framework.
Is there an existing issue for this?
Describe the bug
Hello,
Some hours ago Microsoft released version 2.3.0 of both
Microsoft.AspNetCore.Mvc.Razor
andMicrosoft.AspNetCore.Mvc.TagHelpers
with a dependency on version 8 of some helper libraries, likeMicrosoft.Extensions.Caching.Memory
, instead of version 2.This is causing problems compiling and running some of our older applications since it implicitly forces an upgrade on libraries like
Microsoft.Extensions.Options
orMicrosoft.Extensions.Logging
, which have some significant breaking changes from version 2 up to 8.The fix is to change de project dependencies and ensure these libraries are fixed on version 2.2.0. instead of 2.x
What I'm finding odd is that these libraries aren't maintained anymore and this doesn't look like to be made on purpose, specially a release 7 years later.
Expected Behavior
Keep the dependencies of
Microsoft.Extension.*
libraries on version 2 instead of upgrading to version 8.Steps To Reproduce
No response
Exceptions (if any)
No response
.NET Version
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: