3 ms·
From a side view, .NET Core is not any different. But when you start to dig into the details, you are going to find out that there is no Web.config anymore. Go
by garganzol 10y ago
From a side view, .NET Core is not any different.
But when you start to dig into the details, you are going to find out that there is no Web.config anymore. Gonsky. There is that middleware thing which is configured from the code. Filters? Not anymore.
- manigandham 10y agoWhat? Have you even read the documentation or actually used .NET Core? Filters are still there and even better now. There's no need for web.config because there's project.json which does everything you need. Code based configuration is great, especially for a statically typed language. You can still load things dynamically if you want, like you always could in .NET code. You just listed changes in the framework as if they were bad without actually giving any reasons - or even being accurate.