Hi, my name’s Aaron Powell and I’m a Cloud Advocate at Microsoft. My area of specialty is front-end web dev and .NET (especially F#), but I enjoy doing silly things with technology.
Thanks for the feedback Camilo, I'll answer in reverse order (and they are easier to answer that way!).
3. Currently no, the only "auto-select" for a profile is when you go into Live Share. That said, it's something I was thinking about last week and may add if there's demand (would just need to work out how best to do it).
2. Alas there's no way for me to disable extensions, it's uninstall or nothing, see this comment: dev.to/aaronpowell/comment/dd3a
1. I made a deliberate decision to not use the .vscode/settings.json file as the place I update for a few reasons. The main reason is that I don't want to do anything that runs the risk of corrupting the current git repo. If the extension updated a file tracked in git then it's a (potential) commit you have to make and a diff that needs to be explained. I'd prefer to not do anything that run the risk of modifying a file that everyone on the team relies on.
Another reason is that I originally wrote this extension for when I give talks. I have to remember to switch my settings to make it optimised for viewing on a projector, and I want those settings across all instances I have open (I may use several demos in a talk). So yes, it was partially built around a workflow I needed.
Lastly, you can already do workspace-specific settings by just using the .vscode/settings.json to what you need (I use to do that for repos explicitly used for presenting), so I didn't want to replicate functionality that already exists.
Hope that explains my thought process/reasoning behind some decisions. 😊
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for the feedback Camilo, I'll answer in reverse order (and they are easier to answer that way!).
3.Currently no, the only "auto-select" for a profile is when you go into Live Share. That said, it's something I was thinking about last week and may add if there's demand (would just need to work out how best to do it).2.Alas there's no way for me to disable extensions, it's uninstall or nothing, see this comment: dev.to/aaronpowell/comment/dd3a1.I made a deliberate decision to not use the.vscode/settings.jsonfile as the place I update for a few reasons. The main reason is that I don't want to do anything that runs the risk of corrupting the current git repo. If the extension updated a file tracked in git then it's a (potential) commit you have to make and a diff that needs to be explained. I'd prefer to not do anything that run the risk of modifying a file that everyone on the team relies on.Another reason is that I originally wrote this extension for when I give talks. I have to remember to switch my settings to make it optimised for viewing on a projector, and I want those settings across all instances I have open (I may use several demos in a talk). So yes, it was partially built around a workflow I needed.
Lastly, you can already do workspace-specific settings by just using the
.vscode/settings.jsonto what you need (I use to do that for repos explicitly used for presenting), so I didn't want to replicate functionality that already exists.Hope that explains my thought process/reasoning behind some decisions. 😊