Visual Studio 2013 New Features of the IDE

(Note: This blog post was originally published under my old domain(codesmiles.com), here. Web Archive link. Update: I posted this article on Aug 10, 2013 on CodeProject and in this blog around the release of Visual Studio 2013 preview version(all the below mentioned features are still present in the final release). Even though I wrote this post for documenting and sharing the visual studio 2013 new features that I identified when I started exploring Visual Studio 2013, I recently noted many people, even Microsoft folks have talked about the new features in various Microsoft sites, I recommend everyone to check them out too (posting all those links will just make people lazy :-)). Visual Studio 2013 Preview has been launched recently. Like I did with Visual Studio 2010 and Visual Studio 2012, I am writing this with several purposes in mind; I thought of documenting these cool new features of Visual Studio 2013 that I found, so that it will serve as an index for me and I could easily refer to this in talks I may give, or, when sharing these with friends. (Note that one of the ultimate purposes of blogging/posting articles for me is that I can easily

Visual Studio 2012 New Features of the IDE – better late than never :)

(Note: This blog post was originally published under my old domain(codesmiles.com), here. Web Archive link. I am making this post thinking “Better late than never”, as I was supposed to make this post a long time ago, actually in the beta period of Visual Studio 2012, like I did with Visual Studio 2010, unfortunately I was held up with other stuff, personal and work related. This post remained as partially completed in my blog’s drafts for a long time which I took and finished. Note: This post talks about the Visual Studio 2012’s IDE new features. All non-IDE features, new language features, .net framework 4.5 features, new type of app development support like Windows 8 metro app development and specific code editor enhancements will be discussed in future posts. So with that in mind, here are the new features of Visual Studio 2012’s IDE.. Dark Color Theme for code editor and IDE windows Visual Studio 2012 provides out of the box option to have a White on Black color scheme, Dark AKA White on Black color schemes have become choice of many developers as many have realized that they are easy on the eyes. Dark Theme (click to enlarge)  

Want the dark font color scheme in Visual Studio 2010/2008?

(Note: This blog post was originally published under my old domain(codesmiles.com), here. Web Archive link. If you like the dark color scheme available in Visual Studio 2012 and would be happy to have the same in your Visual Studio 2010/2008, you can have it for at least the code editor font colors by downloading the themes from studiostyl.es. (Note that white-on-black (dark color scheme) is easy on your eyes than usual black-on-white) I was wondering if anyone could have made a theme based on Visual Studio 2012 and went to studiostyl.es and searched then got couple of dark themes based on Visual Studio 2012 code editor font colors. One seems to be made using Visual Studio 11(2012) beta, you can get it here. I think this one looks more accurate. ..and the other one made using Visual Studio 2012 you can get it here.

Code Snippets in Visual Studio

This post gives introduces code snippets in Visual Studio, how you can use them and helps you find out the list of built-in code snippets for each language easily. Code snippets in Visual Studio are useful in reducing typing effort required to input code. Code Snippets help in several ways to simplify your work if you can remember to use them instead of typing the actual code. Code Snippets are present in Visual Studio from ver 2005.

What can you do with ‘IntelliTrace’ in Visual Studio 2010

(Note: This blog post was originally published under my old domain(codesmiles.com), here. Web Archive link. (This post is part of my Visual Studio 2010 series) As I wrote in my earlier article, Visual Studio 2010 has many new features in debugging. IntelliTrace is one of the major features of Visual Studio 2010 and as of now it is available only in Visual Studio 2010 Ultimate edition. In my opinion, IntelliTrace is the best reason to convince your boss to get Ultimate edition for you :). Note, IntelliTrace only supports managed code, for example, it doesn’t support vc++ native code. [more] This article introduces IntelliTrace and tells how it helps in simplifying debugging and tells some more things that can be done with it (based on Visual Studio 2010 ultimate edition-release candidate). (I am taking the intro from previous post..) Introducing Visual Studio 2010’s IntelliTrace.. IntelliTrace is a feature previously known as Historical debugging, which is a major enhancement made to the Visual Studio 2010 debugger. When an exception occurs, you usually start debugging with breakpoints set in suspected areas and check variable/object values for correctness. But if an exception occurs when IntelliTrace is enabled, it allows you to just go

Visual Studio 2010 New Features in Debugging – Exciting & Innovative

(Note: This blog post was originally published under my old domain(codesmiles.com), here. Web Archive link. (This post is part of my Visual Studio 2010 series) This article talks about Visual Studio 2010’s new features related to debugging, applicable from beginner to expert(based on Visual Studio 2010 beta 2). Visual Studio 2010 comes with powerful debugging features. Debugging is an area where an improvement brings great relief to developers, and increases developer happiness. Visual Studio 2010 seems to highly enhance debugging support, and can change some basic ways we used to debug applications, let us have a look.[more] Export/Import Breakpoints By using Export/Import breakpoints in Visual Studio 2010, you can debug a portion of the application and export the current set of breakpoints and import it back whenever you want to debug the same portion of application, no matter what breakpoints you have currently placed in your code. This feature will enable you to have different set of breakpoints for each scenario or portion of application that you may need to debug. This is one of the features that I highly wished to have. An example scenario… consider your web page/windows form has basic CRUD(Create/Read/Update/Del) options, you are currently working on