If it seems like we've been a bit quiet recently it's because we've been working hard on migrating Cofoundry to run on ASP.NET Core. We've been making good progress and I'm pleased to reveal that we have managed to get Cofoundry up and running on ASP.NET Core, complete with admin panel and visual editor support.
There's still a lot more to do, but with the bulk of the ugly migration work out of the way we're starting to track our progress in GitHub issues under the 0.2 milestone.
There are vast differences between MVC5 and ASP.NET Core, so it's not just about getting the code to work, but also investigating a best practice approach to follow to make Cofoundry intuitive to developers familiar with the new ASP.NET Core concepts. You can expect for us to take some time to work on getting this right as we'd like to avoid breaking changes in the future if we can.
.NET Core
The migration plan has always been a two stage approach, moving first to ASP.NET Core running on top of .Net 4.6.2 and then to .NET Core (or more likely .Net Standard). Last week we ran the .NET Portability Analyzer over the codebase and the results were good. We've been watching the progress on .NET Core for some time, so aside from some expected incompatibilities that we've planned to factor out into plugin packages, our path to .NET Standard seems fairly straight forward. This hopefully means we can move straight to .NET Standard in a reasonable time frame.
Our major blocker with .NET Standard is with Entity Framework Core. It still seems to be missing some features we're relying on so I've opened up an issue to discuss how we can work around this, if you want to contribute to the discussion you can find it here.
Next Steps
We're going to keep working through migration tasks and hopefully start producing pre-release NuGet packages and updated samples soon. If you're keen to see what we're up to you can follow our progress in the release/0.2.0 branch or chat to us on gitter.