Little Git Tricks: Mark Files as Moved
When you use the File Explorer (or Windows Explorer) to move files around in your repository, Git knows nothing about that action and treats your files as deleted and newly created:

When you use the File Explorer (or Windows Explorer) to move files around in your repository, Git knows nothing about that action and treats your files as deleted and newly created:

As I was updating my code sample for ReportUnit, I discovered that this little helper is not being developed any longer. I wrote about ReportUnit in 2017 and used it since then to generate an overview for my test suites. Let us see if there is an alternative worth migrating to.
IntelliJ is the Java IDE from JetBrains. I used it a few times over the last months for online workshops like "Make Your Code More Testable" or the 99 minutes series of Ministry of Testing.
The Object Explorer window in SQL Server Management Studio (SSMS) is the place in which you find the databases, the tables, and all other objects inside a SQL Server. While I worked with this view for ages, I only recently found the Object Explorer Details view.
On one device I run constantly into problems with Visual Studio because my user does not have all the rights necessary to perform the tasks I have to do. The simple work around for this problem is to run Visual Studio as an administrator. While I can start Visual Studio explicit as administrator every time I open a project, but that extra step gets annoying quickly.
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 Code Analysis (FxCopCmd.exe) has been deprecated in favor of FxCop analyzers, which run during build. Refer to https://aka.ms/fxcopanalyzers to migrate to FxCop analyzers.
Remote workshops come with their own set of challenges. An often overlooked one is how to get everyone back at a certain time. If you focus on the exercise you easily miss the agreed time to come back. That is even before we start with time zones and specialities like half-hour deviations from standard time (as they occur in parts of Australia).
A nice solution to this problem is mobti.me. This free service is a remote timer for mob (or ensemble) programming. Without any modification we can reuse this service for anything that needs a timer.
After deleting the developer certificate in IIS Express I could recreate a new one as described in this post. This approach worked, even when I needed to run the IisExpressAdminCmd for every port I use. At least, that was how I could fix all problems with SSL and IIS Express on my machine until a few weeks ago. I finally gave up as I got this error:
Error code: SSL_ERROR_RX_RECORD_TOO_LONG
I am glad 2020 is over. It was the year that put an end to any hope of self-responsibility to tackle a global crisis. It did not work for COVID-19, it will not work for climate change. We need something else and I hope we find it in time.
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 changed my mind, and I am happy I did.