Don't worry. Not everyone knows it...

Background When you are in between of writing your logic and by mistake you pressed F5, what will happen? Boom… you will lend up with below dialog due to compilation errors: Now think about it. If we are writing a code it means we need that to be executed whenever we are running the application. Isn’t it? It’s very-very rare case when someone still would like to execute previous logic. At least for me, I never ever want this to happen. Solution So, how to get rid of this rarely used prompt. There are two ways: First, Simply check the checkbox ‘ Do not show this dialog again’ . But for me, on one of my machines this checkbox has not even appeared. Hence, I opted for second option. Second, go to Tools >> Options… >> Projects and Solutions >> Build and Run. On right side panel, just change the value in dropdown displayed under ‘ On Run, when build or deployment errors occur: ’ to  ‘ Do not Launch ’  and we are done. ...

Let’s have a look at one of the coolest feature of Visual studio 2017. If you will see below snapshot, there are many new icons here.  These icons are part of cool new feature called Live unit testing in Visual Studio 2017 Enterprise. Live Unit Testing continuously runs and displays unit test result and code coverage inside editor itself. It automatically finds and runs impacted tests for every line of code. In above diagram, Red cross indicates failed test case, Green tick indicates passed test case and Blue minus indicates the code that have no test coverage at all. Let’s start by looking at failing test case. You can quickly navigate to failing test case by clicking on tooltip as shown below:  And below is my test case: At this point, I’m not really sure why this is failing. So, I’ll go ahead and debug this test We can see here that above particular code has thrown a nul...