Skip to content
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

Moved Castle.Core compatibility layer down to Castle.Windsor #183

Closed
wants to merge 1 commit into from
Closed

Moved Castle.Core compatibility layer down to Castle.Windsor #183

wants to merge 1 commit into from

Conversation

ghost
Copy link

@ghost ghost commented Feb 21, 2017

Moved all compatibility classes from Castle.Core down to Windsor for anticipation of migration to dotnet core.

{
using System.Collections.Generic;

// This allows us to use the new reflection API while still supporting .NET 3.5 and 4.0.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it is about time we discussed the plans for Windsor v4, we are dropping all Silverlight and I think we should drop .NET Framework 3.5 and 4.0 including any client profile ugliness... see #185.

That being that case, much of this isn't needed because .NET 4.5 added GetTypeInfo and some friends. You can even see that the .NET 4.5 build of Castle Core doesn't define FEATURE_LEGACY_REFLECTION_API (https://github.com/castleproject/Core#conditional-compilation-symbols).

@ghost ghost closed this Feb 23, 2017
@ghost ghost deleted the castle-core-shims-compatibility branch March 17, 2017 21:17
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant