Every other process I was able to attach however and I was puzzled. The note I had from VS 2012 was looking like this : The problem was, that I wasn’t for some time creating any.
Dec 14, 2021 · You can use the Windows debuggers (WinDbg, CDB, and NTSD) to debug target applications that contain managed code. To debug managed code, you must load the SOS debugging extension (sos.dll) and a data access component (mscordacwks.dll). The Windows debuggers are separate from the Visual Studio debugger..
Collect Debug Output Strings for DLP: SUPOPS-447: DLP: Windows: Unable to identify Enforce version when installed to a custom directory: SUPOPS-459: SED: Windows: SED 10.5 MP3 released: SUPOPS-479: SEE: Windows: Update SEE version: SUPOPS-458: SEP: Windows: Could not find a part of the path after saving the SBDZ: SUPOPS-464: SEP: Windows.
"gdbserver" now supports seamless debugging of processes from containers Prior to this update, when *GDB* was executing inside a Super-Privileged Container (SPC) and attached to a process that was running in another container on Red Hat Enterprise Linux Atomic Host, *GDB* did not locate the binary images of the main executable or any shared libraries loaded by the process to be debugged.
I've set use managed compatibility from debugging options. I've enabled native code debugging option. I've tried targeting .NET framework 4.5.2 and 4.6.1 . In the end I've tried to attach another process(i.e calc.exe) and it was fine. Its just Revit.exe refusing to be attached to the VS debugging.