There are a bunch of contradictory statements about web.config and .NET Core.
Read a few web.config
examples from Google and you should notice that,
).
).So migrating to ASP.NET Core only make the first obsolete, and you should only say goodbye to that piece of knowledge.
If you host your web app on IIS, then web.config
is still needed, as you need initial settings there to configure ASP.NET Core module for IIS/IIS Express (dotnet publish
generates such a file if you don't have your own).