> The project.json is a terrible format The latest asp.net core templates(shipping with VS 2017 RC) use .csproj files, so you can test them out already. > On

> The project.json is a terrible format The latest asp.net core templates(shipping with VS 2017 RC) use .csproj files, so you can test them out already. > On the other hand for .net core many libraries simply do not exist (yet). This is partly due to MS making such a huge mess out of the ecosystem, going through dnx to dotnet and switching around targets to settle on netstandard. Hopefully things have settled by now and library authors can catch up. There's still one more compatibility snafu to get through with the transition from netstandard 1.6 -> 2.0 and .NET framework versions 4.6.1/4.6.2. If you suffer from "javascript fatigue", it's best to stay away from .NET Core right now - it is going through the same churn of rapid reinvention. We're using it for some smaller projects and are really happy with where it's going, but it's not been an easy ride.