search

microsoft / vscode-dotnettools

This is a feedback repository to capture issues logged for the C# Dev Kit and related extensions from Visual Studio Code
Other
231 stars 13 forks source link

[BUG] Can't debug ERROR brokeredServicePipeName #1432

Closed kdcllc closed 1 month ago

kdcllc commented 2 months ago

Describe the Issue

Unable to debug with C# Dev Kit v1.10.12 (pre-release)

The following error is thrown:

Start debugging failed. Provided launch or attach configuration is missing required property 'brokeredServicePipeName'.

if the extension is disable debugging works!

Steps To Reproduce

No response

Expected Behavior

The expected behavior to be able to debug .NET Core applications

Environment Information

Version: 1.93.0-insider Commit: 336db9ece67f682159078ea1b54212de7636d88a Date: 2024-08-30T18:47:32.318Z Electron: 30.4.0 ElectronBuildId: 10073054 Chromium: 124.0.6367.243 Node.js: 20.15.1 V8: 12.4.254.20-electron.0 OS: Linux x64 6.8.0-40-generic

WardenGnaw commented 2 months ago

What version of the C# extension do you have installed? If you update it to the latest, do you see the same error?

kdcllc commented 2 months ago

@WardenGnaw I am using the latest C# Dev Kit v1.10.12 (pre-release) if I down grade to stable version I have a different issue, where language service stops working

WardenGnaw commented 2 months ago

Sorry, I should have clarified. Which version of the ms.dotnettools-csharp are you using.

Latest prerelease was v2.45.17 and latest release was v2.39.29

kdcllc commented 2 months ago

@WardenGnaw I am using v2.45.17 (pre-release)

I had to switch to pre-release versions due to other issues with release versions of the extensions.

WardenGnaw commented 2 months ago

Got it. Sorry couple more questions to help me figure out what's going wrong.

How are you starting your debug session?

Are you right clicking on solution explorer, using the debug button in the file on the top right, using a dynamic configuration from C: <projectname>or are you using a launch.json

kdcllc commented 2 months ago

@WardenGnaw this is great question.

I am using launch.json file

        {
            "name": ".NET Core Launch (console)",
            "type": "coreclr",
            "request": "launch",
            "preLaunchTask": "build",
            "program": "${workspaceFolder}/src/Host/bin/Debug/net8.0/Host.dll",
            "args": [],
            "cwd": "${workspaceFolder}/src/Host",
            "console": "internalConsole",
            "stopAtEntry": false
        },
WardenGnaw commented 2 months ago

Interesting... I'm unable to reproduce this issue o Ubuntu 22.04 with C# Dev Kit v1.10.12 (pre-release) and C# Extension v2.45.17 (pre-release).

However, I have some suggestions to try to work around this issue is to use the C# Dev Kit debug launch path since the configuration you have is only utilize C# Extension.

Note: I'm guessing the projectPath here.

{
   "name": "C#: Host Debug",
   "type": "dotnet",
   "request": "launch",
   "projectPath": "${workspaceFolder}/src/Host.csproj"
},

or does right clicking in the solution explorer and debug image

kdcllc commented 2 months ago

@WardenGnaw I am using this template to create Console DI app https://github.com/kdcllc/Bet.Extensions.Templating. Please try using that for your testing. Thanks

kdcllc commented 2 months ago

@WardenGnaw

The debugging is working once again here is the latest bits that are installed on my machine:

Version: 1.94.0-insider
Commit: a162831c17ad0d675f1f0d5c3f374fd1514f04b5
Date: 2024-09-06T12:53:19.832Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Linux x64 6.8.0-40-generic
pennisiandrea commented 2 months ago

Same problem here but I don't think it is linked to this extension. I've tried to downgrade C# Dev Kit to v1.9.55 without success. What helped me was downgrading C# extension to v2.39.29 (I had v.2.45.20). Now my debugger is working well with this configuration: C# Dev Kit v1.10.16 C# v2.39.29

andrenatal commented 2 months ago

Same problem here but I don't think it is linked to this extension. I've tried to downgrade C# Dev Kit to v1.9.55 without success. What helped me was downgrading C# extension to v2.39.29 (I had v.2.45.20). Now my debugger is working well with this configuration: C# Dev Kit v1.10.16 C# v2.39.29

This combination also worked for me.

trg601 commented 2 months ago

I switched to the latest pre release version and it fixed it for me.

WardenGnaw commented 1 month ago

This should be fixed in versions of the C# Extension past v2.48.31