-
Notifications
You must be signed in to change notification settings - Fork 485
.NET Target Frameworks for Castle Core v5.0 #597
Copy link
Copy link
Closed
Milestone
Description
We've made changes to our target frameworks for our next major version but none of this has been released yet. With so much time passed and the .NET Core landscape changing I think we need to re-evaluate our target frameworks before releasing.
.NET Core notes:
- ".NET Core 2.1 reached end of life on August 21, 2021".
- According to the .NET Support Policy only .NET Core 3.1 and .NET 5 are currently supported.
.NET Framework notes:
Our set up:
<!-- v4.4.1 -->
<TargetFrameworks>net35;net40;net45;netstandard1.3;netstandard1.5</TargetFrameworks>
<!-- master -->
<TargetFrameworks>net45;netstandard2.0;netstandard2.1</TargetFrameworks>What do we support for v5.0? I don't think we should be supporting any .NET Core versions that are now end of life, there is no reason for people to expect we support new versions of Castle Core on end of life runtimes. Do we continue with any .NET Standard TFMs? Even though DynamicProxy might not work on some .NET Standard-based runtimes, Windsor depends on Castle Core and so we shouldn't restrict Windsor unnecessarily.
/cc @stakx
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels