Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
.NET Core support #133
This is an umbrella issue listing some things that need to be taken care of in order to get .NET Core support working.
Multiple branches, I'm currently working on getting NUnit 3.5 working, which is a prequisite on branch https://github.com/spring-projects/spring-net/tree/features/nunit35 , then I'll proceed with changing from Rhino.Mocks to FakeItEasy . These two then can go to master when working properly.
I guess initial project.json can go to master too if determined as functioning.
After that I can rebase branch https://github.com/spring-projects/spring-net/tree/features/netcore on top of master again. So easier changes first and building .NET in parallel. It's a big undertaking.
Starting a few hours, i have some data to share and i think that can help on migrating Spring.NET to .NET Standard 2.0.
Isolating only Spring.Core i have great results on basic tests.
But i have issues to work on.
Default application context load, based on ConfigurationManager infrastructure are broken overall, but XmlApplicationContext still working fine on linux. The challenge today is adapt configuration models to run ubiquitous on windows and on linux.
To make a basic funcionality i have to replace things, using fake implementations about:
Later, this week i'll share the project. It's not a fork, is a sugar to explain that is possible, and we are near to solve that. We are going to .NET Core! It's awesome!
Docker Instance and MachineName
AOP is now working too
referenced this issue
Oct 27, 2017
Following projects now compile under netstandard2.0:
Basically things not supported in netstandard/.NET Core have been left out of compilation (remoting, enterprise services etc).
Closing this as the main steps have been completed. There probably are more improvements that can be made as separate issues.