You can change to a debug build by specifying the DOTNET_CONFIGURATION build environment variable, as shown below: NET Core s2i image, the build is a release build by default. Here is a summary.Ī debug build works fine for remotely debugging. The procedure for setting up the ASP.NET Core pod is almost same as what I wrote before for Visual Studio Code. The MIEngine debugger enables you to use any command for SSH connection.Īll the steps below have been confirmed using a combination of Visual Studio 2017 (versions 15.7.2 and 15.8 preview2) on Windows 10 and OpenShift 3.9. However, you need to use the oc command instead of an SSH client such as putty since Red Hat OpenShift pods don't allow direct connections via SSH. If a remote host accepts an SSH connection, Visual Studio can do remote debugging using Visual Studio's default feature.
Visual Studio and Visual Studio Code now support SSH as a transport protocol for remote debugging. Remotely debugging a pod enables you to investigate such an issue. Sometimes you encounter an issue that happens only in the production environment.
#Visual studio remote debugging windows 10 how to
Today I introduce how to remotely debug a pod using Visual Studio from your Windows computer. Last year, I wrote a blog post how to remotely debug your ASP.NET Core container on OpenShift with Visual Studio Code.