How to Get Rid of Error "Process with an Id of XXXX is not running" in Visual Studio
As I tried to make some changes in an older project, I ended up with this error message whenever I tried to start the web application:

As I tried to make some changes in an older project, I ended up with this error message whenever I tried to start the web application:

The default behaviour for views in ASP.Net MVC up to version 5 is that they are compiled when the first user requests them in IIS. When the view isn't that complicated, the user only experiences a minimal delay before the web page is displayed in the browser. That is true as long as the view compiles. If not, your users will get a page like this one:

This dialog is familiar to all developers who use Visual Studio:

When you work in multiple teams, you quickly end up with different ideas on how the code you write should be formatted. “Tabs or spaces?” is something developer can argue for hours, have strong opinions about and are unwilling to change them. With only one setting in Visual Studio you are constantly changing it, or you end up reformatting the code. Both is annoying and not really a working solution.
Visual Studio 2017 has a new feature called EditorConfig, who addresses exactly this problem. Even better, this is not a Microsoft only approach, but an initiative by multiple vendors and projects (like JetBrains, GitHub, and many more.). You can find more details on EditorConfig.org, including examples and links to various projects using it.
This year I did not just attend NDC Oslo, I got the chance to contribute as a speaker to this great conference. That shift of perspective made me much more appreciative of the hard work that goes into a talk and how much it takes to stand in front of such a great and welcoming audience.
The five talks I selected for this post had an impact on me that went far beyond of being entertained for an hour. I spend a lot of time thinking about what I heard and I guess so will you. Those presentations may look as if they are at the wrong place for a tech conference, but trust me, they are as important as any technical talk. I am glad the organizers put them in. They challenge how we think, not only about the systems we use and build, but also about how we work with others and make our world a better place.
Did you ever need a little bit of randomness in a list? Not cryptographically strong randomness, just a bit of unpredictability so that not every run of your tool is the same? If so, this post offers you a simple way to shuffle your lists.
Updating Visual Studio is for most cases a non-event. However, one instance started to show JavaScript errors all over the place. Since we do not write JavaScript with this instance, we do not need to know about JavaScript errors.
Suddenly, NUnit stopped working. We were in the middle of our refactoring, moved code around and ended up with all our tests being ignored. We rebuild the solution – no errors detected. We run our application – no problems at all. We even rebooted the machine. Everything worked except our tests:

Exploratory testing is a great way to find bugs of any sorts. However, after an hour of testing all possible edge cases you don’t know what you tried and what not. Rapid Reporter is a great helper to keep track of your activities.
Tools do not have to be big to be a great help. One of those little helpers I use often when working with XML and JSON is Indent XML. It is a plugin for Sublime Text (a sophisticated text editor) and helps you to turn this