Net Framework applications can be found in post by Richard Banks: How to Remote Debug a. Hope this helps! Please post any helpful comments for others and any other links you might know of! ReferencesĪnother example of remote debugging. For example, if debugging a IIS web application: Once the container has been selected, then the running process can be selected. If there is more than one container detected, you can determine the specific IP address of the container by using the docker inspect command:ĭocker inspect -f "" mysite The screenshot below shows the detected containers:
In the Transport, Remote is used and the Find button is used to establish the remote connection: Within Visual Studio, select the Attach to Process action in the Debug window: The final step is to start the remote debugger on the container as shown below:ĭocker exec -it mysite "C:\Program Files\Microsoft Visual Studio 14.0\Common7\IDE\Remote Debugger\圆4\msvsmon.exe" /nostatus /silent /noauth /anyuser /nosecuritywarn For example, the following starts the container with the name "mysite" and exposes ports 40 and port 80 as port 8078.ĭocker run -d -p 4020:4020 -p 4021:4021 -p 8078:80 -name mysite core RUN & amp 'c:\rtools_setup_圆4.exe' /install /quietĪfter the image has been built, the next step is to make sure the ports for remote debugging (-p 4020:4020 -p 4021:4021) are also mapped when running the container. RUN Invoke-WebRequest -OutFile c:\rtools_setup_圆4.exe -Uri. The following is an example of enabling this on a dockerfile that uses Microsoft's Asp.Net image: Net Framework app is to install and run the remote debugger.
The first step to enabling the debug of a. Īttaching to a container is similar to those examples where the ability to remote debug needs to be enabled on the container to allow Visual Studio the ability to connect. This approach can be used to attach to a remote computer and even to Azure Web Apps and Azure Functions. Most devs are familiar with debugging solutions at design time using both the auto-attach (F5) and attaching the debugger to a running process on their local machine. In all three examples, the container needs to be prepared to allow for Visual Studio to access a running process on the container. Net Framework application running a windows container as well as provide references to posts about remote debugging for different platforms including the. Visual Studio has excellent built in support for working with Docker containers, and most of the examples on the web are written with those tools installed. But what about the situation where the container is already running? This post will provide an example of debugging a.
0 kommentar(er)
