Tools
Visual Studio & VS Code
Configuration, debugging, Git, extensions, productivity and teamwork.
- 018 minVisual Studio vs VS Code — when to choose whichintro
When to reach for the full Visual Studio IDE, and when a lightweight VS Code editor is enough.
- 0210 minConfiguration and essential extensionscore
How to configure Visual Studio and VS Code, and which extensions are the team standard.
- 0311 minDebugging (breakpoints, watch, call stack)core
Practical debugging in Visual Studio and VS Code: breakpoints, inspecting variables and the call stack.
- 0410 minGit in the IDE (commit, branch, merge, PR)core
Day-to-day work with Git directly from Visual Studio and VS Code, all the way to the Pull Request.
- 059 minProductivity: shortcuts, snippets, refactoringcore
Keyboard shortcuts, snippets and safe refactorings that genuinely speed up coding.
- 068 minTeamwork: Live Share, settings syncadvanced
Real-time collaborative coding with Live Share and synchronizing settings across machines.
Check your knowledge — quiz
5 questions · pass mark 80%. Score saved locally.
1.Which tool will you choose at ProfessNet for working on the ZEUS backend built on a .NET solution (.sln)?
2.Why do we keep a .vscode/extensions.json file with a "recommendations" section in the repository?
3.What does a conditional breakpoint with the condition userId == 4071 do when set in a loop over thousands of records?
4.At ProfessNet, how does every change reach the main branch?
5.How does Settings Sync differ from configuration kept in the repository (.editorconfig, .vscode/settings.json)?