如何在“生产”环境中Web部署ASP.NET Core应用程序？

Question

I created a test ASP.NET Core web app and published it to azure via Web Deploy...

When I try to access a page controller via the site URL, I have the following:

I have mainly non-modified by default also a lauchSettings.json file with

{
    "iisSettings": {
        "windowsAuthentication": false,
        "anonymousAuthentication": true,
        "iisExpress": {
            "applicationUrl": "http://localhost:23403/",
            "sslPort": 0
        }
    },
    "profiles": {
        "IIS Express": {
            "commandName": "IISExpress",
            "launchBrowser": true,
            "environmentVariables": {
                "ASPNETCORE_ENVIRONMENT": "Development"
            }
        },
        "IIS Express (Staging)": {
            "commandName": "IISExpress",
            "launchBrowser": true,
            "environmentVariables": {
                "ASPNETCORE_ENVIRONMENT": "Staging"
            }
        },
        "IIS Express (Production)": {
            "commandName": "IISExpress",
            "launchBrowser": true,
            "environmentVariables": {
                "ASPNETCORE_ENVIRONMENT": "Production"
            }
        },
        "MyApplication": {
            "commandName": "Project",
            "launchBrowser": true,
            "environmentVariables": {
                "ASPNETCORE_ENVIRONMENT": "Development"
            },
            "applicationUrl": "http://localhost:23404"
        }
    }
}

What should I do in order to modify the ASPNETCORE_ENVIRONMENT variable when publishing it via

PS.

I updated the App Settings in Azure portal, like this then republished the application...

But nothing changed, I have the same Error ...

Answer 1

launchsettings.json only affects local development I think. It won't affect it in Azure. I think you should be able to define an app setting with key ASPNETCORE_ENVIRONMENT set to eg Development.

Answer 2

I thinks you are mixing 2 questions here.

1. Deployment to production
2. Monitoring bugs

As about deployment, it looks like you did everything correctly - your site is hosted using not Development environment. This is exactly what error page tells you.

As about bugs, you definitely would not like anyone to see your connection strings or anything else an error message may contain. So you need to add some logging to see what really fails.