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
197 stars 6 forks source link

[BUG] LaunchBrowser related features does-not work when working on a Codespace #1107

Open dibarbet opened 3 weeks ago

dibarbet commented 3 weeks ago

Describe the Issue

Copied from https://github.com/dotnet/vscode-csharp/issues/7086, originally filed by @OTonGitHub

in .NET development, there is a launchSettings.json file, which has some properties for launchBrowser and launchUrl, this defines if the browser be launched when the App is run and what would be the launch URL. That file is illustrated below:

When I am using a remote Codespace connected to my VSCode, the ports defined in launchSettings.json are forwarded, however the prompt that comes up when app does not take into consideration the specifications of launch properties, it only seems to detect the port in which the App is launched in and forwards it.

As such, I suggest that, for .NET development having this feature to detect launchUrl from the remote server and doing so locally will save time and make developer experience better for devs using codespace or remote development, this may not be .NET specific, but I am reporting as how I encountered it.

Thank you.

Steps To Reproduce

No response

Expected Behavior

No response

Environment Information

No response

dibarbet commented 3 weeks ago

Sending over to the project system as I've been told that is who plumbs the information over to the debugger.