OTOH, VS Code supports grid layouts, something i do find myself using. While VS supports "popping out" tabs, it's something i've rarely done over the years. csx scripting is stuff i can do in VS Code without extra steps.
csx) files, VS Code "just works." Working with individual. Similarly, if i want to work with C# Script (.
VS Code handles this just fine, whereas VS's "folder view" is more limited. Also note the improved syntax highlighting and Class/Outline view in VS Code: this is because the project loaded - an MS sample project - isn't a full. Next time you install on another machine or reinstall, set up sync, and you're good to go. Note the VS install is much less customized as i find it to be annoying to do so, whereas in VS Code making and maintaining configurations to be more simple and rewarding. VS Code gives me what i actually use most often in Visual Studio and cuts out the noise: I'm just more productive with keybindings/ Ctrl+Q/Command Palette than the default long/deep menus and toolbars with buttons i'll rarely use. Yes, the menus and toolbars are customizable - but that's another step to take. When i use Visual Studio, i find myself using Ctrl+Q (equivalent of VS Code's Command Pallete) a lot because it's easier than navigating toolbars and menus, IMO. It's got lots of toolbars, menus/submenus, tabsets/tabs, icons out the wazoo. Comparatively speaking: It's opinionated. Having used MS "Visual" tools since VB4, i'm as familiar & comfortable with "full" Visual Studio as i'll ever be. VS has a longer feature list than VS Code, but what percent of the time are you taking advantage of those extra features ? (Performance profile tools being my #1 example here.) This varies from person to person & project to project, so feature count isn't a very useful comparison.
0 kommentar(er)
