对于那些在调试Azure网站的web应用程序时遇到此问题的人，还有一个额外的答案:

例如，当从GitHub部署时，代码在默认优化的Azure服务器中编译。

通过将SCM_BUILD_ARGS设置为/p:Configuration=Debug，我告诉服务器以可调试的方式进行编译

但还有更多的选择。看到这个: http://azure.microsoft.com/blog/2014/05/08/introduction-to-remote-debugging-on-azure-web-sites-part-3-multi-instance-environment-and-git/

我只是碰到这个问题，我在发布构建配置下运行，而不是调试构建配置下运行。一旦我切换回调试我的变量显示在手表再次。

I found that I had the same problem when I was running a project and debugging by attaching to an IIS process. I also was running in Debug mode with optimizations turned off. While I thought the code compiled fine, when I detached and tried to compile, one of the references was not found. This was due to another developer here that made modifications and changed the location of the reference. The reference did not show up with the alert symbol, so I thought everything was fine until I did the compilation. Once fixing the reference and running again it worked.

我也有同样的问题。尝试以上所有方法，发现我还必须删除{PROJECT_ROOT}\bin\Release\netcoreapp2.2和{PROJECT_ROOT}\obj\Release\netcoreapp2.2内的所有内容。它肯定与发布有关，因为虽然我在我的Azure Web应用程序上使用部署工具/ bitbucket，但我确实尝试了Build >> Publish >> Publish to Azure，因为我想检查哪些文件实际部署了。

对于那些在调试Azure网站的web应用程序时遇到此问题的人，还有一个额外的答案:

例如，当从GitHub部署时，代码在默认优化的Azure服务器中编译。

通过将SCM_BUILD_ARGS设置为/p:Configuration=Debug，我告诉服务器以可调试的方式进行编译

但还有更多的选择。看到这个: http://azure.microsoft.com/blog/2014/05/08/introduction-to-remote-debugging-on-azure-web-sites-part-3-multi-instance-environment-and-git/

我也遇到过同样的问题，我的解决方案是将解决方案配置从发布更改为调试。希望能有所帮助