If the target executable of a "normal" VS 2k22 debug session also contains a debug adapter in the process, then a connection to the debug adapter (via DebugAdapterHost.Launch) using the same IDE instance will deadlock. Works ok from another IDE instance. Probably need to talk to someone to explain the situation.
If the target executable of a "normal" VS 2k22 debug session also contains a debug adapter in the process, then a connection to the debug adapter (via DebugAdapterHost.Launch) using the same IDE instance will deadlock. Works ok from another IDE instance. Probably need to talk to someone to explain the situation.