4 ms·
What? 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 ther
by manigandham 11y ago
What? 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.