YetaWF with ASP.NET Core
YetaWF 2.5.x uses ASP.NET Core MVC 2.0 which hasn't been released yet (expected Q3 2017 - https://github.com/aspnet/Home/wiki/Roadmap). Unfortunately, we could not use 1.0 or even 1.1 as there were serious shortcomings (for example, https://github.com/aspnet/Mvc/issues/5397 and https://github.com/aspnet/Mvc/pull/5676/commits) and we don't believe even 1.1 is ready for a production site. VS 2017, which was released initially released in February 2017, is not quite as usable as VS 2015 for web development as the tooling for MVC web sites is a bit rough.
ASP.NET Core MVC Preview
ASP.NET Core MVC 2.0 has not yet been released but is available as a Preview. It requires a preview version of Visual Studio 2017 and of the ASP.NET Core .NET Command Line Tools.
Installing Visual Studio Preview
At least Visual Studio 2017 Preview (3) 4.0 is required to build YetaWF with ASP.NET Core MVC - You can download Visual Studio 2017 Preview from https://www.visualstudio.com/vs/preview/. Without this preview version of Visual Studio 2017, YetaWF CANNOT BE BUILT.
ASP.NET Core .NET Command Line Tools
In order to build ASP.NET Core applications with Visual Studio 2017, you need to install a preview version of the ASP.NET Core .NET Command Line Tools. This can be downloaded from https://github.com/dotnet/cli#installers-and-binaries. At least Preview 2.1.0-preview1 is required and without this, YetaWF CANNOT BE BUILT.
When you open your Visual Studio solution for the very first time, please wait a moment until all projects references are downloaded and resolved (this appears to be a bug in VS 2017). If you start a build too early, the build will fail. If this happens, simply rebuild all again.
For first time startup of the site, make sure to build a Debug build.
By default, a new YetaWF site uses port 80 which means you have to stop IIS in order to run your new YetaWF site with IIS Express or Kestrel. You can change this in the settings (see launchSettings.json) if desired. You also have to run Visual Studio 2017 as Administrator to be able to start/debug the website from Visual Studio.