-
Notifications
You must be signed in to change notification settings - Fork 844
Added default dotnet-tools + additional tasks to launch them #16409
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
Conversation
psfinaki
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks useful - how about we mention some of those tasks in the DEVGUIDE?
Probably not worth it? These are standard tools/tasks, you either use them or don't. I feel like all of them are self explanatory? We don't mention how to launch with VS diagnostic tools or dotTrace/dotMemory/windbg there. |
Mmm e.g. we have that note about updating XLFs and it says "This can be done automatically by running this command" and I just thought we could add smth like "... or by executing this task in VSCode". So that people have a notion of those. I personally don't use VSCode tasks so I don't know - but now looking at the PR I am thinking it is easy enough to give them a try and change my dev routines. Up to you ofc. |
I wouldn't update them just for now. Since our VSCode support is not great at the moment. I'd update it and fully add once we do more LSP testing, I think. |
Added tools I use the most. Now I need to manually install them in dev container every time, this will allow installing them in one command.
Also, added a task to launch fsi/fsc under trace, so it can be opened with speedscope later.