Amend Optional Attribute Names in XAML
Polishing some XAML

Published: April 12^th, 2020

I have to admit I am a stickler for detail. Ok, a lot of developers are born this way, but this post discloses a certain degree most of the developers I know miss. Here comes a procedure to enrich your XAML with optional attribute names, e.g. the word Path.

Formatting Messages Handling plurality adequately

Published: March 1^st, 2016, Updated: Some days ago

Once in a while I stumble upon code to format message texts in C#, either mine or from developers on Stack Overflow. It looks like this:

string messageTemplate;
if (_itemCount == _persistedItemCount)
    messageTemplate = Resources.ProtocolMessageAllItemsAreFiled;
else if (_persistedItemCount == 0)
    messageTemplate = Resources.ProtocolMessageNoItemsAreFiled;
else
    messageTemplate = Resources.ProtocolMessageSomeItemsAreFiled;
return String.Format(messageTemplate, _persistedItemCount, _itemCount);

Developers get quite — let's say — "creative" to format readable message texts for the user, especially when it comes to plurality. Source code like this is ok, but we can do better.

C# developers usually love the keyword var:

var isProcessed = false;
var numberOfElements = 10;
for (var i = 0; i < productList.Count; i++)
    // ...

How can this innocent keyword be bad?

When designing a button bar in WPF I discovered a strange behaviour of the UniformGrid. My buttons did not look very uniformly.

Some developers consider logging to be a thief of performance and a false hope when they need to locate a bug. I consider it to be helpful in debugging scenarios and only experienced performance issues because of logging when it was used unwise. One way to make logs to be more helpful is to include a session ID in server-side log entries. Here is how to do it.