If it helped you, it could help someone else too.Visual Studio 2019 is a massive step forward in the developer spectrum. It’s also useful to have a rough estimate of how much time you spent working on a given feature.ĭid you find this post useful? If so, please consider retweeting it.
#Good visual studio extensions code#
Ever wonder how much time you spend writing code per day, week, or month? Or which parts of a feature took longer to complete? WakaTime gives you the answers to those questions. The second bonus extension is on the productivity side of things.
Under Code Lens, uncheck Containers Scope.There’s a few settings you’ll want to tweak to make it behave similarly to Visual Studio: Once you’ve installed the extension, open the settings page by choosing GitLens: Open Settings from the Command Palette. The GitLens Explorer view provides much the same features as Team Explorer in VS2017, lowering the barrier to entry of the Git command line. GitLens gives you the flexibility to see who and when source code was changed in-line within a file, much like in Visual Studio. NET Core but it helps to bring VSCode’s editor closer to the VS2017 experience. NET DecompilerĮver wonder what a method is doing under the hood? Rather than load up a separate tool like ILSpy, DnSpy, or DotPeek to decompile the assembly, you can do it straight from Code by way of this extension. Luckily, this extension takes that burden away by providing an auto-complete for the name and version of any package you’re adding to the project. For long time Visual Studio users, this can be hard to get used to, especially when it comes to adding NuGet packages. There is a strong emphasis on using the editor and command line in Code. NET Core Project opens an integrated terminal window that runs the selected command, making it easier to build or launch an application. Sometimes though, it’s nice to have a visual hierarchy of the tests.NET Core Test Explorer does just that by adding a view that displays all the tests in the solution in a tree layout.Ĭlicking either Build. The dotnet test command is highly configurable. NET Core is built around a powerful CLI. Visual Studio Keymap brings you as close as possible to the mappings from Visual Studio, with the exception of functionality that isn’t supported in VSCode. #2: Visual Studio KeymapĪnyone who’s spent time learning keyboard shortcuts in Visual Studio will feel lost when starting out with VSCode. The only frequent problem I’ve had with it is randomly losing Intellisense, which requires a restart of the extension through the Command Palette via the Omnisharp: Restart Service command.
Code automatically recommends it when you open a C# project, so all you need to do is click Install. It brings with it many features that a Visual Studio developer will expect such as Intellisense, syntax highlighting, debugging, and more. The C# extension is the starting point if you want to write for. These extensions bridge the gap by addressing needs in the areas of debugging, keyboard shortcuts, testing, documentation, build options, and source countrol. This list is targetted at developers moving from Visual Studio 2019, who want to make the transition a bit smoother. It became apparent when I started using VSCode that there were a few features missing to make the IDE feel familiar for a Visual Studio 2019 developer. And while it’s gone through lots of changes, the core elements have pretty much stayed the same since 2010. I’ve been using Visual Studio for more than a decade now. That’s why I decided to put this list together. Most are focused on general productivity or front-end development, with very few specific recommendations for. There are tons of lists out there with the best Visual Studio Code extensions.