mikoskinen/attachtodotnet

Extension for Visual Studio 2017/2019 which makes it easier to attach to the correct dotnet.exe process

Attach to dotnet.exe

Extension for Visual Studio 2017/2019 which makes it easier to attach to the correct dotnet.exe process.

Features

This extensions adds two commands to Visual Studio:

• Attach to dotnet.exe. The dialog provides a clear view of different running .NET Core applications.
• Reattach to the previous dotnet.exe process. Useful for scenarios where dotnet watch is used as the process id is changed everytime the code is compiled.

Screenshots

With the extension

Without the extensions

attachtodotnet's Issues

dotnet script support

Mikael,

In the absence of any built-in debugging for C# scripting (.csx) in Visual Studio 2019, this extension "as is" was almost just right for me to be able to, at least, debug and step through code. Your extension could "see" the external dotnet.exe parent process and even "attach" to it, but no breakpoints worked. However, tweaking your source code slightly to include child dotnet-script.exe process (and building a modified .vsix and adding to Visual Studio, of course) does make your extension work!

I'm surprised Microsoft hasn't added the ability to do this themselves in Visual Studio yet, since dotnet script debugging is already available in VSCode.

Anyway, (1) using a custom configured tool for "dotnet.exe script" to launch an active C# script file and then (2) attaching to the process using your slightly modified extension (as well as (3) putting something at the top of the script to "force it to wait" so it doesn't just run straight through the script and exit before even have a chance to attach to the external process) seems work well!

Perhaps you would consider tweaking your extension to work for dotnet.exe script since it is very useful!

Cheers,
Tom