When deploying an ASP.Net core application into our hosting you need to make sure to include a proper Web.Config file.
Asp.Net core differs from Classic ASP.Net Web Form in that its dynamic files (like .aspx, .php, ... for other frameworks) are compiled into a single .exe or .dll file.
Without Web.Config the system will not know how to start the website and will return a 500 error.
The Web.Config file should be automatically created inside your project.
Here is how default Web.Config file looks like:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<system.webServer>
<handlers>
<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified"/>
</handlers>
<aspNetCore processPath="%LAUNCHER_PATH%" stdoutLogEnabled="false" hostingModel="InProcess"/>
</system.webServer>
</configuration>
Where %LAUNCHER_PATH% should point to the App's primary .dll or .exe file.