With your StyleCop installation in place we can now look at how we can customise our StyleCop configuration. This is part two of my small series of StyleCop for .Net 5 Projects: Part 1: StyleCop for .Net 5 Projects: Installation Part 2: StyleCop for .Net 5 Projects: Custom Configuration Part 3: StyleCop for .Net 5 …
When you work in a team it is of great importance that you all follow the same rules. Otherwise your turn a code base in a mess in no time. We settled for StyleCop because it allowed us to delegate the nitpicking of code formatting and code style to a tool that does it automatically …
Cleaning up warnings in your project sometimes brings you to strange places. One of the more notable one was the depreciation warning for FxCop. We use StyleCopAnalyzers in our projects and there was no reference whatsoever to FxCop. Yet the build agent had a different opinion and showed this warning: Warning – CA0507 – Post-build …
Last week I attended the “Make Your Code More Testable” workshop by Ted M. Young (@jitterted). I was not sure if I wanted to attend yet another workshop this year as I saw the first tweet about this workshop. After I saw the recommendations by Gitte Klitgaard, Esther Derby, Kent Beck and GeePaw Hill I …
The world keeps turning and when you do not actively spend time to update the dependencies of your projects, you will fall behind. First one minor version, then another and before you know, there are a few new major versions released and your project is full of security risks. We all know that his happens …
We can use many attributes to describe a good application: changeable, future-proof, well designed, or flexible are just a few of them. What does this mean? Is this just a challenge for the most uncommon word pair? Or is there something behind those words that we can measure? My work gave me a good example …
StyleCop can be a great help to ensure that every developer in a project formats code the same way. However, what is great for production code may not be what you want for your little throw away experiments. Let’s look on our options to disable StyleCop when we don’t need it. Change the default …
Let’s talk about some of the more annoying habits many programmers have: the inability to delete code. Code is kept around as if their life depends on it, even when its purpose is long gone. They do all possible things so they don’t have to delete anything. They comment code out, put unreachable conditions around …
One of the main purposes of continuous integration is to know when your build fails. As soon as a problem is detected you want to be alarmed. But in certain situations you can accept a failed build. Today I will show you how to use a build matrix in Travis CI to allow failures for …
As experience shows the quality of code degrades slowly and before you know it will be an unmaintainable mess. To prevent this many practices where developed and have proven their usefulness over and over again: test automation, continuous integration and code analysis are just a few of them. Unfortunately those practices still require work and …