Include "remote" in name of .net core remote launch configuration.
- Dominant language
- TypeScript
- Stars
- 3.1k
- Forks
- 737
- Avg merge
- 17h 56m
- Merged PRs (30d)
- 21
Description
"Add configuraiton..." for ".NET: Launch a remote .NET Core Console App" has the same name as the default console launch configuration, causing confusion in the configuration drop down.
Initial launch configuration generated by the extension:
```json
{
"name": ".NET Core Launch (console)",
"type": "coreclr",
"request": "launch",
"preLaunchTask": "build",
// If you have changed target frameworks, make sure to update the program path.
"program": "${workspaceRoot}/bin/Debug/netcoreapp2.0/scratch.dll",
"args": [],
"cwd": "${workspaceRoot}",
// For more information about the 'console' field, see https://github.com/OmniSharp/omnisharp-vscode/blob/master/debugger-launchjson.md#console-terminal-window
"console": "internalConsole",
"stopAtEntry": false,
"internalConsoleOptions": "openOnSessionStart"
},
```
Default configuration added for ".NET: Launch a remote .NET Core Console App":
```json
{
"name": ".NET Core Launch (console)",
"type": "coreclr",
"request": "launch",
"preLaunchTask": "build",
"program": "${workspaceRoot}/bin/Debug//",
"args": [],
"cwd": "${workspaceRoot}",
"stopAtEntry": false,
"console": "internalConsole",
"pipeTransport": {
"pipeCwd": "${workspaceRoot}",
"pipeProgram": "enter the fully qualified path for the pipe program name, for example '/usr/bin/ssh'",
"pipeArgs": [],
"debuggerPath": "enter the path for the debugger on the target machine, for example ~/vsdbg/vsdbg"
}
}
```
The new configuration should probably have 'remote' in the name or something.
Contributor guide
Assessment
This issue has not been assessed yet.