Unable to Debug Business Central On-Prem to a different instance from VS Code

(0) Share

Report

Posted on by Olister Rumao

3,959

Hi All,

I have created a Server and WebServer Instance in BC16.
I'm able to connect VS Code to the respective instance, download symbols, and publish extensions.
But when I try to debug the same extension, the debugging starts to a different instance.
I need to know if there is a setting in VS Code to choose which WebserverInstance to debug.

Here is launch.json
{
"version": "0.2.0",
"configurations": [
{
"name": "Dev",
"request": "launch",
"type": "al",
"environmentType": "OnPrem",
"server": "http://localhost",
"serverInstance": "Dev",
"authentication": "UserPassword",
"startupObjectId": 22,
"startupObjectType": "Page",
"breakOnError": true,
"launchBrowser": true,
"enableLongRunningSqlStatements": true,
"schemaUpdateMode": "ForceSync",
"port": 5049
}
]
}

Debugging URL with debugging context

localhost:8080/.../SignIn

Please note that I have cleared the Credential Cache, Reinstalled AL Extension, and even created a new project and downloaded the symbols.

All responses (2)

Answers (0)

Suggested answer

Suresh Kulla 47,789 on at

Like (0)

Report

RE: Unable to Debug Business Central On-Prem to a different instance from VS Code

Specify the web client base URL and then set the Server on launch.json to that value. Make sure to restart the services and vs code.
Suggested answer

Marco Mels on at

Like (0)

Report

RE: Unable to Debug Business Central On-Prem to a different instance from VS Code

Hello,

Did you fill in PublicWebBaseUrl in customsettings.config file?

Thanks.