-
Notifications
You must be signed in to change notification settings - Fork 456
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop support for .NET 3.5/4.0 and Silverlight #185
Comments
Drop support, it's the right thing to do. |
Silverlight down (#173, #180 and #184), .NET 3.5 next? How should we approach this? CMD/MSBuild/CsProj 1 PR and then an experimental PR perhaps starting with one of the test fixtures so we can establish conventions for how we treat things like: DOTNET35 |
We have killed off support in the build process for the following:
Now for the arduous task of build flag redux. |
Let's start with NET35 @ #195. Will wait till you merge so I can continue without conflicts ... |
We OK to close this issue @jonorossi ? |
Let's wait until those are merged, I'd like to do a quick check to see if there is anything left after that. |
@jonorossi - what still needs to be done here? Can you think of anything I missed? |
|
You right @jonorossi! There was some guff there ... #206. Will keep hunting and submit more PR's for what I find. |
GrepWin for |
GrepWin for |
GrepWin for Here we have an interesting conundrum to do with the tooling for MsBuild. In This needs to change but we might need to update the build server before I can submit a PR. What do you think @jonorossi? Can you help? |
GrepWin for |
.NET 4.5 and 4.6 were all in-place upgrades of .NET 4.0 (we just compile against different reference assemblies), so the framework directory is the same. |
Looks like we are done here. Many thanks @fir3pho3nixx for getting that all sorted. |
@jonorossi - No worries 👍 |
We've already made the decision to drop all Silverlight support in Windsor v4 following dropping support for Silverlight in Castle Core v4.
I (and others) think it is time we drop support for .NET Framework 3.5 and 4.0 for the next major Windsor version (v4), it is time because they are so old and mostly because it has now become effort to maintain and a lot of work for add .NET Core support while still keeping them working. Most .NET containers have removed support a while ago and today support:
Feel free to jump in either way, however be prepared to put forward a good argument if you believe we shouldn't remove support for .NET 3.5/4.0, Windsor 3.x will always be there for you if you really aren't already on .NET 4.5/4.6.
The text was updated successfully, but these errors were encountered: