Conversation
…codespace with prebuilt
|
Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer Issue DetailsGenerate .runsettings file for VSCode as part of libs.pretest. Unfortunately we can't use the .runsettings file that we generate for Visual Studio as the paths that we use are specific for every test project containing configuration settings and for VSCode we need to point OmniSharp to the .runsettings file via a global setting that applies to all projects. However I'm not concerned about this as much as in VS we have more complex settings that are specific to each test project. After adding this, people can open a test file and just click on "Debug Test" on intellicode and then debug it by just setting a breakpoint when in a codespace.
In order to support this locally we need a few more tweaks, I will put up a separate PR for that.
|
|
Is there anything we can do to keep this working? Will PR validation / CI cover this? |
At the moment it will only validate that the target works, but it won't validate the .runsettings file is well formed (same for the VS generated .runsettings file), I guess we could cover this as part of the plans of protecting VS/innerloop experience? #36139 |
ghost
locked as resolved and limited conversation to collaborators
3 participants
Generate .runsettings file for VSCode as part of libs.pretest. Unfortunately we can't use the .runsettings file that we generate for Visual Studio as the paths that we use are specific for every test project containing configuration settings and for VSCode we need to point OmniSharp to the .runsettings file via a global setting that applies to all projects. However I'm not concerned about this as much as in VS we have more complex settings that are specific to each test project.
After adding this, people can open a test file and just click on "Debug Test" on intellicode and then debug it by just setting a breakpoint when in a codespace.
In order to support this locally we need a few more tweaks, I will put up a separate PR for that.