I came across this error message when I was setting up a new Visual Studio Team Services build and found it quite funny. A valid ASP .Net Core project does not need a web.config file when it's not hosted in IIS, and it definitely doesn't need a wwwroot folder if it's an API that does not serve static files.
It made me reflect on my past choices when designing software solutions. We sometimes take shortcuts, whether due to time constraints or insufficient business analysis. It usually makes us look stupid, sooner or later. No profound lessons in this post. It's just something to remind me that I should look where I can put in that extra 5%.