4 ms·

It is a completely different architecture from the ground up, completely re-written with modern development in mind. For one example it has native support for

It is a completely different architecture from the ground up, completely re-written with modern development in mind. For one example it has native support for dependency injection, and in general testability has massively improved since it was a core design goal. They've also de-coupled several layers, which is hugely powerful since you can write your own middleware. For example check out this article on "Handling Errors Globally with the Custom Middleware"[0]. If you want to see how different it is from .Net Framework look at this diagram: https://msdnshared.blob.core.windows.net/media/2017/06/062217_2209_ThenewNETAp12.png https://msdnshared.blob.core.windows.net/media/2017/06/06221... [0] https://code-maze.com/global-error-handling-aspnetcore/#builtinmiddleware https://code-maze.com/global-error-handling-aspnetcore/#buil...

sk5t 8y ago
The diagram (and your comment) appear to be about ASP.NET and don't tell anything about .NET Core compared to, say, .NET Framework 4.5.
- Someone1234 8y ago
  Frankly because nothing outside of the .Net Core's Web/Asp.net/MVC/WebAPI improvements actually matters. And the changes there are massive and significant. While you can technically create Forms, WPF, and UWP applications using .Net Core on Windows, that isn't really the direction or focus of the framework. Just a niche for legacy software or people who continue to need Windows specific desktop applications. https://trends.google.com/trends/explore?q=%2Fm%2F02_qnn,%2Fm%2F03f8ny,Windows%20Presentation%20Foundation,uwp,%2Fm%2F07sb4tb https://trends.google.com/trends/explore?q=%2Fm%2F02_qnn,%2F... Console applications might have a future for cross-platform headless sever loads. But outside of that it is a web framework that happens to support non-web projects on the side. It is competing primarily with e.g. Java, Ruby on Rails, Node.js, PHP, etc.

sk5t 8y ago

The diagram (and your comment) appear to be about ASP.NET and don't tell anything about .NET Core compared to, say, .NET Framework 4.5.

Someone1234 8y ago
Frankly because nothing outside of the .Net Core's Web/Asp.net/MVC/WebAPI improvements actually matters. And the changes there are massive and significant. While you can technically create Forms, WPF, and UWP applications using .Net Core on Windows, that isn't really the direction or focus of the framework. Just a niche for legacy software or people who continue to need Windows specific desktop applications. https://trends.google.com/trends/explore?q=%2Fm%2F02_qnn,%2Fm%2F03f8ny,Windows%20Presentation%20Foundation,uwp,%2Fm%2F07sb4tb https://trends.google.com/trends/explore?q=%2Fm%2F02_qnn,%2F... Console applications might have a future for cross-platform headless sever loads. But outside of that it is a web framework that happens to support non-web projects on the side. It is competing primarily with e.g. Java, Ruby on Rails, Node.js, PHP, etc.