We are looking at trying to run the front end site under .Net Core on a seperate server to the editing and admin site that still has the dependency on .Net Framework and would like to know if this is possible. From what we can see it seems as though it should be possible with a bit of work but it would be easier if we had the promised package form EPiServer that would help with this.
Is there any time frame for official support from EPiServer for this? I notice that at the recent partner event there was still no timeframe given and it sounds more like marketing fluff than an actual commitment to support .Net Core. .Net Core has significant advantages for us over the .Net Framework and it is very concerning that there is no commitment to a process of migration.
Is it possible to split EPiServer into the front end site and the editing and admin site and run just the front end under .Net Core. This would allow us to get most of the benefits in resource usage and performance that comes with .Net Core.
You are correct that there are no exact timeframe. The difference now is that Episerver has promised us that it will come out during 2019, but not if it is Mars or December.
It would be nice if we could get an official confirmation of that or can you give me a reference to where that is confirmed.
Any news? .Net core support is a dealbreaker for us. No support for core in 2019 it is at least strange...
just out of curiosity - in what sense it's a deal breaker?
"Is it possible to split EPiServer into the front end site and the editing and admin site and run just the front end under .Net Core. This would allow us to get most of the benefits in resource usage and performance that comes with .Net Core."
Yes, it is possible to run just the front end site (aka not the CMS/admin interface) using whatever tech stack you want. See examples on Episerver github such as hosting a PWA FE using Vue.js or similar.
We have been investigating if it is possible to run EPiServer under .Net Core and it looks like most of the rendering pipline hasn't been made .Net Core compatible yet as .Net Core changed this significantly from what .Net Framework does and it is likely going to be a decent amount of work for them to fix. It's likely possible to hack something together but it's definetly not production ready to run under .Net Core.
We are working on ASP.NET Core support at the moment. Check-out https://world.episerver.com/blogs/martin-ottosen/dates/2019/12/asp-net-core-beta-program/ for more information.