VSCode should self-configure debug settings when added to ASP.NET Core projects

[weinand]

From @bitcrazed on July 10, 2016 17:44

• VSCode Version: 1.3.0
• OS Version: Windows 10

Steps to Reproduce:

1. Create ASP.NET Core project using either Visual Studio 2013 or via Yeoman ("yo aspnet") at the command-line
2. At the command-line, navigate to the root of the project (wherever project.json resides)
3. Run dotnet restore: Dependencies should be downloaded
4. Run dotnet run: Project should build & run
5. Run code .: VS Code should load and open the project folder
6. Open debug tab and hit "play button": VS Code displays an error that "launch.json must be configured"
   

I asked about this on Twitter and received help from @jchannon, @shanselman and @DamianEdwards (thanks guys): Turns out that I had to manually determine the target-framework and project-name fields. I also had to set the "debugType": "portable" in project.json. (see request to set this by default)

I would have expected that since VS Code injected launch.json into the project, and that it had access to project.json etc. that it'd be able to determine the target-framework automatically.

Copied from original issue: microsoft/vscode#9033

[weinand]

VS Code by itself does not know anything about .NET projects and project.json.
So it can only be the .NET extension that creates a launch.json that corresponds to the project.json.

[shanselman]

This is still a nasty bug.

[DustinCampbell]

@rajkumar42, is this related to #577.

[rajkumar42]

No this is a different issue.