从VS 2019预览版将.Net Core Web App部署到Azure App Service后出现错误

本文介绍了从VS 2019预览版将.Net Core Web App部署到Azure App Service后出现错误的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

大家好，

我尝试将Visual Studio 2019预览版中新创建的.Net Core(2.2.1版)Web App发布到Azure App Service中.

我在Visual Studio 2019中创建了Azure App服务(项目右键单击->发布-> Azure App Service配置文件).

可悲的是，我收到以下错误消息:

该页面无法显示，因为发生了内部服务器错误."

不过，当我在调试模式下本地运行该项目时，该项目运行正常.

我还尝试将部署模式"设置为自包含"，可惜这没有帮助.

配置文件设置为:

• 配置:发行版
• 目标框架:netcoreapp2.2
• 部署模式:独立/依赖框架(都尝试过)
• 目标运行时:win -x86

有人知道这个解决方案吗?

谢谢.

巴里斯

解决方案

按照以下步骤检查这是部署还是运行时问题: github/projectkudu/kudu /wiki/Deployment-vs-runtime-issues

要获取有关此问题的更多详细信息， 您可以尝试该文档中概述的建议， 对Azure App Service上的ASP.NET Core进行故障排除 启用日志并对其进行分析以缩小问题范围.

The ASP.NET Core Module stdout日志通常会记录在应用程序事件日志中找不到的有用错误消息. 您还可以启用和查看上面文档中突出显示的标准日志，并让我们知道如何进行进一步调查.

Hello everybody,

I try to publish a fresh created .Net Core (Version 2.2.1) Web App from Visual Studio 2019 preview into an Azure App Service.

I Created the Azure App service within Visual Studio 2019 (Project right click -> Publish -> Azure App Service Profile).

Sadly i get following Error:

"The page cannot be displayed because an internal server error has occurred."

The Project however runs fine when I am running it in Debug Mode locally.

I also tried to set the Deployment Mode to Self-Contained it sadly didn't help.

The Profile Settings are:

• Configuration: Release
• Target Framework: netcoreapp2.2
• Deployment Mode: Self-Contained / Framework dependent (tried both)
• Target runtime: win-x86

Does anyone know a Solution for this ?

Thanks in advance.

Baris

解决方案

Check if this is a Deployment or Runtime issue by following these steps: github/projectkudu/kudu/wiki/Deployment-vs-runtime-issues

To fetch more details on this issue, you may try the suggestions outlined in the document, Troubleshoot ASP.NET Core on Azure App Service to enable logs and analyze them to narrow down the issue.

The ASP.NET Core Module stdout log often records useful error messages not found in the Application Event Log. You may also enable and view stdout logs as highlighted in the document above and let us know how that goes for further investigation.