Shulou(Shulou.com)06/02 Report--

This article introduces you how to achieve remote debugging in ASP.NET Core, the content is very detailed, interested friends can refer to, hope to be helpful to you.

Experience Web Deploy

This publishing method can package the code directly to the specified site of the specified server, which is very convenient.

Considerations for remote debugging

To use remote debugging features, you need to meet the following highlights at the same time:

The code must be published to the server as Debug

The files in the local project folder must be the same as those on the server (mainly dll files under bin)

Personal feelings

The picture above is the schematic diagram of remote debugging. If the VS fails to respond for a long time, the server will report a 502 error.

Remote debugging requires the code to be released in Debug, which is not in line with the actual situation, which makes the function of remote debugging a little more obvious.

Compared with debugging local code, when remote debugging hits a breakpoint in the code, VS will stutter or even time out, probably because you need to establish a network connection to transmit debugging information (network speed should be guaranteed in our business)

Microsoft documentation for the use of remote debugging network requirements: do not use proxies to ensure good bandwidth and network speed

On how to achieve remote debugging in ASP.NET Core to share here, I hope that the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.