1
votes

I have an MVC core website written in C# which is deployed to an AWS EC2 Instance with Windows Server 2012 R2 and IIS8 deployed on it.

I am trying to remote debug the application as I am getting errors thrown which I don't when running locally (details for another post maybe).

On AWS Console, I have a security group with the following Rules as guided by here: Inbound rules Outbound Rules

and when I click on Debug->Attach to process, and browse to my AWS instance, I can see the correct dnx.exe process, however, when I attach to that process,

enter image description here

I get the The breakpoint will not currently be hit. No symbols have been loaded for this document

I've tried going to Tools->Options->Debugging->Symbols and clicking Load all symbols as it is my understanding that since VS2012 the symbols do not need to be deployed, but rather just on the local machine doing the debugging, taken from here.

In versions of Visual Studio before VS 2012, debugging managed code on a remote device required that the symbol files were also located on the remote machine. This is no longer the case. All symbol files must be located on the local machine or in a location specified in the Debugging / Symbols page of the Visual Studio Options dialog box. See .NET Remote Symbol Loading Changes in Visual Studio 2012 and 2013 on the Microsoft Application Lifecycle blog.

I can see the connections being initiated in the MSVSMON process on the EC2 instance.

I feel like I'm close but I'm just missing one simple thing.

1

1 Answers

0
votes

You need to check on which port the Remote Debugger is running and allow inbound traffic on that port by opening Inbound Port [4024 in my case] with a Custom TCP Rule for Remote Debugging.

You can check the port used by Remote Debugger at Tools > Options in the Remote Debugger Menu.