-
-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Visual Studio Code support #273
Comments
I volunteer to add these files if desired. |
I don't see why not :D My only concern is with these files becoming out of date as neither myself nor Kai use VSCode. |
I personally would prefer using launchSettings.json, I believe this is supported by all IDEs. |
Yeah. They can become out of date, but they are really helpful for new devs who don't want/have VS or are on Linux. I have example files here: However there are a few things that you may not want to add to your files. Mainly, I apply custom syntax highlighting in my settings folder that you guys may not want. The main things that will become out are file paths. If you move file paths or change the build target (.NET Core 2.0 -> 3.1 for example) the file path in the launch/task will need to be updated. |
We don't check in Rider or VS files, why VSC? I'd be on board with launchSettings as they, like |
Did not know this. |
In regards to Hacktoberfest, to clarify, we would appreciate contribution of |
Fixes: #273 Adding tasks and launch configurations to allow running and debugging tutorial projects directly from Visual Studio Code. Newly added tasks also allow publishing tutorial projects and running them under under the wather. Verification: - Ran each added launch configuration from VS Code - Published a couple projects and made sure artificats were written to the expected location - Ran a couple projects under the watcher
Nice :) Sorry I didn't have time to add these when I opened the issue. Glad someone else did. |
Feature Request
Add
.vscode
folder with extensions, tasks, launches, and (optionally) settings.json
files so people can run the examples from Visual Studio Code rather than Visual Studio without additional setup.The text was updated successfully, but these errors were encountered: