With Visual Studio Keymap, Code uses the same shortcuts for all overlapping features. One of the most common issues of changing an IDE, is to learn an entirely new set of shortcuts (still have nightmares from switching from Eclipse to Visual Studio years back).
The experience isn't as great as in LINQPad, but it's at your fingertips.Īnother extension from Microsoft, brings your Visual Studio keyboard shortcuts into Code. Rather than starting LINQPad for C# or Chrome dev tools for JavaScript, Code Runner can execute one or more highlighted lines of code inside Code. I often find myself needing to try out a few lines of C# or JavaScript code. Jun Han developed another useful extension called Code Runner.
This is most likely the first extension you will ever install as a. Wait a minute! You need an extension to develop C# in Code? Since Code supports multiple programming languages, C# support is like any other language an extension. We still use Visual Studio to maintain Functions, because the tooling is better, but I can see where Microsoft is going with the support for Code.
I won't go into detail about Functions here, except to tell you how awesome they are (and we already wrote a series about developing and logging in Azure Functions). It's amazing how tiny improvements like these can make a world of difference.Ī lot of the elmah.io internals are written as Azure Functions. Auto Close Tag automatically adds a closing tag, which saves you quite a lot of keystrokes over time, while Auto Rename Tag renames closed tags automatically. However, using these two extensions from Jun Han, will give you much of the same experience in Code. I don't usually write HTML in VSCode, since the HTML editor in Visual Studio 2017 is pretty awesome. This blog post is part of our Learn about. This post is a summary of all the different extensions we've found to make Code even better. We use Code for quickly previewing files, writing markdown, non C# programming, quick prototyping, and much more. We haven't replaced Visual Studio, but it's great for some aspects of our development process. Previously, we used a lot of different development tools (alongside Visual Studio), but that changed when Microsoft launched Visual Studio Code. Note that you can now kiss your Visual Studio 2010 settings and preferences goodbye (your projects will be safe and sound).ĭELETE (or rename) all other folders that are not the “11.0” folder, assuming you used to have Visual Studio 2008 or whatever.Extending your IDE is the new black and we also use a lot of extensions every day in our daily work. Here you’ll see a folder titled “11.0” (the VS 2012 folder) and probably also “10.0” (the VS 2010 folder).ĭELETE (or rename) the “10.0” folder. If you weren’t, go to the “Roaming” folder.
Open the start menu and type “%AppData%” and press enter to get to your Application Data Folder.Įither you were automatically placed in the “Roaming” folder or you weren’t. If your Intellisense is anything but intelligent, and has stopped working, do the following: Maybe a hotfix will come out eventually to fix this issue. You don’t have to uninstall either of them, but if you open a solution in them it seems you’ll re-break Visual Studio 2012. Note that for this fix to work, you have to abandon Visual Studio 2010 or 11 PERMANENTLY. So, after a ton of screwing around and guess-and-check, here’s how I solved it. Strangely, I did not find the “correct” aka permanent solution to this problem. I thought to myself “what the hell Visual Studio? 2010 didn’t have these problems?!” and then, after a swig of beer, proceeded to exercise my Google-Fu to solve this issue. The very first thing I noticed was that after about 10 minutes of programming my Intellisense quit working and never came back.
I recently upgraded my home PC from Visual Studio 2010 and 11 Beta to Visual Studio 2012. So, this post is about our beloved IDE instead of actual code.