Visualstudio-docs: Which Exe to Attach to?

[spottedmahn]

When I've been remote debugging ASP.NET Core apps I've been attaching to my exe i.e. MyASPApp.exe in this example but the demo attaches to dotnet.exe.

Is there pros/cons to either approach? Same difference?

Attaching to my exe feels safer compared to attaching to dotnet.exe. Seems like I could effect other apps, no?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: c4215ecb-721f-9b0b-66ae-042ffd7c9842
• Version Independent ID: 0d58ec46-8b09-f184-24f3-ac53ac0d1b50
• Content: Remote Debug ASP.NET Core on a Remote IIS Computer - Visual Studio
• Content Source: docs/debugger/remote-debugging-aspnet-on-a-remote-iis-computer.md
• Product: visual-studio-windows
• Technology: vs-ide-debug
• GitHub Login: @Mikejo5000
• Microsoft Alias: mikejo

[Mikejo5000]

@spottedmahn That's very interesting. I don't think that it was possible to connect to MyASP.exe in previous versions of the remote debugger and/or VS. If attaching to MyASP.exe gets you the debugger features you expect, yes, that sounds safer. I will need to test this before changing the doc, as that may not work in VS 2017. What version of VS are you running?

[spottedmahn]

Works in VS 2017 on a .NET Core 2.0 web app for me.

[Mikejo5000]

@spottedmahn I'm updating the doc, mentioning the method you described. I can't get a repro on a local IIS, so I will also leave in the dotnet.exe info for the time being until I have better info.

[spottedmahn]

Hi @Mikejo5000 - I think I figured it out today why I'm seeing the differences: full framework vs core framework...

When targeting the full framework the exe is the app name. In core, I guess only a dll is produced and that DLL runs under dotnet.exe

Reference: Attaching the debugger