Visual Studio Code 1.12 debugger fails to run with Omnisharp and Dotnet projects

[mdmoura]

Environment data

dotnet --info output:

.NET Command Line Tools (1.0.1)
Product Information:
Version: 1.0.1
Commit SHA-1 hash: 005db40cd1
Runtime Environment:
OS Name: Windows
OS Version: 10.0.14393
OS Platform: Windows
RID: win10-x64

VS Code version: 1.12

C# Extension version:
1.10.0-beta2

Steps to reproduce

I upgraded Visual Studio Code from 1.11 to 1.12 and got the following error when debugging a dotnet project:

Error processing 'configurationDone' request. Unknown Error: 0x89720010

Everything was working fine before upgrading to Visual Studio Code 1.12.

And I was using Omnisharp extension1.10.0-beta1. I then upgraded to 1.10.0-beta2.

However I keep getting the same error. What might be wrong?

[egamma]

@gregg-miskelly can please help us to track down whether this is 1.12 releated?

[jasonsturges]

Same issue - every ASP.NET Core web application or DotNet Core command line application that previously functioned before the v.1.12.0 update now exhibits this error.

[mjosephsmith]

Same issue - all ASP.NET Core web apps would build and run just minutes prior to the update.

[miguelcaravantes]

same issue v1.12

[bernardbr]

Same issue here!
Error processing 'configurationDone' request. Unknown Error: 0x89720010

[miguelcaravantes]

in VS code "Insiders" 1.12 works fine

[isidorn]

Yes, as a workaround you can use VSCode insiders https://code.visualstudio.com/insiders
While we are investigating the issue...

[bernardbr]

In a meanwhile I'll downgrade https://code.visualstudio.com/updates/v1_11

[ingcrengifo]

@bernardbr Great idea, I'll do the same.

[mjosephsmith]

I took the downgrade path, as the Insiders version immediately through an error stating that "coreclr" was not a valid configuration type... 👎

[winterlimelight]

If you can get away without debug in the short term you can run the following from PowerShell to have things run as normal:

path-to-folder-with-proj-file> $Env:ASPNETCORE_ENVIRONMENT = "Development"
path-to-folder-with-proj-file> dotnet run

[emersonsoares]

As @isidorn recommended, vs code insiders is working fine here.

[RichardD012]

@mjosephsmith if you open the console you can install a .NET debugger.

[zeroskyx]

Same issue here -- related to https://github.com/OmniSharp/omnisharp-vscode/issues/1323?
VSCode 1.12.0
C# 1.9.0
Windows 10 Pro x64

[gregg-miskelly]

No. This is a bug in VS Code. The VS Code team is working on fixing it. Either install insiders or roll back in the mean time.

[gregg-miskelly]

We will not close this yet since this is a hot issue, but microsoft/vscode#25918 tracks fixing this.

[gregg-miskelly]

VS Code 1.12.1 is now out, and contains the fix. So closing this.

[omerlh]

I am having the same issue, using vscode 1.15. It happens to me when trying to attach to docker process, as described in #1369. Regular start of dotnet core app works, so I guess this is something related to this configuration. I have 2 errors when running the configuration, the original error and:

unknown request 'attach'

The launch configuration:

        {
            "name": "Debug Api",
            "type": "coreclr",
            "request": "attach",
            "processName": "dotnet",
            "pipeTransport": {
                "debuggerPath": "/vsdbg/vsdbg",
                "pipeProgram": "docker-compose",
                "pipeCwd": "${workspaceRoot}",
                "pipeArgs": [
                    "exec", "app"
                ],
                "quoteArgs": false
            }
        },

Update: I used docker instead of docker-compose and now it works. Weird...

[gregg-miskelly]

@omerlh you are seeing Unknown Error: 0x89720010, and you are only seeing it for docker??? If not, please open a new issue.

[omerlh]

Yes, I saw it only for docker-compose. When switched to docker instead it worked...