Support for .NET Core 2.0
Description
Environment
Attachments
depends on
Activity
Scellow Dev July 31, 2017 at 12:54 PMEdited
not right place to ask - sorry for that mistake, i'll post in the right repo!
Nathan Brown May 29, 2017 at 12:07 AM
I think we are close with pull request #633. It's currently passing 5,073 of 5,385 tests on Linux. If it could be reviewed and any commits/contributions made to help close the gap, we should be able to have something solid by the time .NET Core 2.0 is released.
Alex Zaytsev May 3, 2017 at 6:16 AM
The version which "compiles": https://github.com/hazzik/nhibernate-core/tree/NH-3807
To build from within VS2017 RTM (15.1): https://github.com/aspnet/Announcements/issues/235
Nathan Brown May 3, 2017 at 4:15 AM
Hmmm. It's not like BuildTools is a tiny download either. AppVeyor doesn't seem to have a problem having the full Visual Studio installed on their build agents.
For Antr3 in the .NET Core 1,0 version, I had my own custom build, but if the upstream project is supporting it now, hopefully they can get the tooling fixed up.
I'm pretty sure this has already been discussed internally, but I can't find it anywhere on JIRA.
I think it would make a lot of sense if NHibernate were to support .NET Core as target platform in the foreseeable future to enable cross-platform development. I understand that this might be a huge task involving even more aggressive cleanup of legacy code and possibly (probably) some breaking changes, but would go a long way to keep NH relevant. EF 7 will support it (duh), which will definitely give it an edge over NH...
I for one am certainly considering making the switch over to EF 7 for new projects just for that reason, even though NH is still much more powerful and flexible (and I have experience with it).