A .NetStandard 2.0 port of Spring.Net
This port extends Spring.NET 2.0 adding support to .NET Standard
I'm Luiz Carlos Faria, Spring.NET user. I love this project. I couldn't just and watch the project die, Spring.NET solves many questions and adress many ways to do IoC and Dependency Injection in the right way. It's a pleasure to contribute with this discussion.
A main goal with this port is solve questions about adapt and overcome migration from .NET Framework to .NET Standard. Only core projects of Spring.NET will stay here.
Understanding what's necessary to develop a framework in 2018, change all kind of decisions taken in the past. Spring.NET is largest project that i know, with more and more responsabilities in only one repository, distributed on some assemblies.
This choice does not sounds good for 2018. Squeeze the Spring.NET responsabilities may improve community adoption, just causing needs that community will respond with new framework extensions. Challenges about best extension for .NET Core configuration model, MVC, and others skill must be done.
In order of that, this port/fork contains only two projects:
- A full featured Inversion of Control container
- Expression Language for lightweight scripting
- An Aspect Oriented Programming framework
I really considering moving Spring.AOP to Spring.Core, aggregating both in only one project/assembly/nuget package. The segregation of both projects does not sounds good for me.
This project was created to present for Spring.NET developers that is possible to migrate. It's sounds like:
"Hey there, why nobody starts a port? We can do that! It's not simple, but you don't to spend many time, come on, don't give up!"
For example look that:
- Summer.Core.Fakes/System.Runtime.Remoting.cs
- These file address not resolved dependencies.
- The default configuration model, based on ConfigurationManager is not working.
