I am bringing up command line and running my app using dotnet run
command. This starts Kestrel and brings up my application.
How should I go with identify to which process to attach debugger so I can debug the website that Kestrel now hosts?
I specifically need to be able to do it this way - meaning I can't use standard F5.
You can attach the Visual Studio debugger to a running process on a local or remote computer. After the process is running, select Debug > Attach to Process or press Ctrl+Alt+p in Visual Studio, and use the Attach to Process dialog to attach the debugger to the process.
That means to attach a debugger (i.e visual studio's integrated debugger) to the process so you can pause it and inspect variables at runtime. This happens when you hit F5 automatically, or can be done manually using the debug menu.
Open Visual Studio in Administrator Mode, then Debug -> attach to process -> tick the check box "Show processes from all user", select w3wp.exe.
Unfortunately, there is no way to tell right now using the tools provided by Visual Studio or .NET Core. Notice, though, that the community has already requested for this feature here, so you can voice your opinion there.
Currently, the best option is to follow the steps to find out the id of the process given the application's port:
netstat -abon | findStr "127.0.0.1:{PORTNUMBER}"
dotnet.exe
If you feel adventurous, you may want to use something like this PowerShell, which will return directly the port number:
$string = netstat -abon | findStr "127.0.0.1:{PORTNUMBER}"; $results = $string.split(' '); $results[$results.length - 1]
You can print the pid to the console and use that to select from Ctrl-Alt-P
Console.WriteLine($"Running at pid {System.Diagnostics.Process.GetCurrentProcess().Id}");
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With