Just wanted you ask what your view on ASP.NET 5 is? Is it on your roadmap to migrate to it? ASP.NET 5 is planned to be released Q1 2016. Will we see an ASP.NET 5 based EPiServer version in 2016?
There's already a thread about that here http://world.episerver.com/Modules/Forum/Pages/Thread.aspx?id=123618.
It won't happen anytime soon. But I guess there will be ASP.NET 4.6 support soon.
I just tried and 4.6 are already works, at least for a Alloy project.
I have one that are runnit it
<package id="EPiServer.CMS" version="9.1.0" targetFramework="net46" /> <package id="EPiServer.CMS.Core" version="9.1.0" targetFramework="net46" /> <package id="EPiServer.CMS.UI" version="9.2.0" targetFramework="net46" /> <package id="EPiServer.CMS.UI.Core" version="9.2.0" targetFramework="net46" /> <package id="EPiServer.Framework" version="9.1.0" targetFramework="net46" /> <package id="EPiServer.Logging.Log4Net" version="2.0.0" targetFramework="net46" /> <package id="EPiServer.Packaging" version="3.2.3" targetFramework="net46" /> <package id="EPiServer.Packaging.UI" version="3.2.3" targetFramework="net46" /> <package id="EPiServer.Search" version="8.0.0" targetFramework="net46" />
It's good to hear that ASP.NET 4.6 works, but it's ASP.NET 5 that I'm interested in. ASP.NET 5 contains a bunch fantastic (although breaking) changes like configuration in json files instead of the current Web.config + configSource mess. It also contains quite drastic performance improvements.
@Johan: You say that "It won't happen anytime soon". Does that mean that ASP.NET 5 support is not something that is currently being worked on? Is it even on the radar for future development?
EDIT: Sorry! I missed the link to the thread discussing it.
When you say that a lot of stuff is missing from the new framework, do you mean that .NET Core is missing stuff or that ASP.NET 5 is missing stuff? It would be incredible if EPiServer was only dependant on .NET Core and not the full .NET Framework (enabling Mac and Linux development/deployment) but I realize that would be an even bigger undertaking than just moving to ASP.NET 5 + Full .NET framework.
I'm referring to .NET Core. Sure, MVC 6 would be nice to have... maybe that's one way to transition to CoreCLR.
Ah, that makes sense. I'm not expecting EPiServer to ever be compatible with just .NET Core (even if I would cry of joy if it were). But there's a huge amount of nice things in ASP.NET 5 (and MVC 6), and I'm really hoping that this is something the EPiServer folks are working on/looking at.
As an insider what I can say is that we have been working to make our products ASP.NET 5-compatible. But it won't be released any time soon.
That's fantastic to hear! Could you elaborate on what "ASP.NET 5-compatible" or is that not something you want to share just yet?
I can't say much, but the first step will be making our products run on ASP.NET 5. This will involve some legacy parts such as Admin mode in CMS and Commerce Manager in Commerce, as well as some internal works (project formats, tests etc). Then we will try to embrace new features of ASP.NET 5.
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.