sfeldman.NET

When it comes to receiving messages with ASB, there are plenty of options:

Processing with Azure EventHubs can be significantly simplified if using EventProcessorHost. EventProcessorHost is using Azure Storage account to track last read locations (pointers) in event hub partitions.

Last week GitHub has introduced what seems like a small feature, but a huge comments de-clutter if you ask me: reactions. I've been using Slack for quite a while and among the feature that slack has had for a while was reactions for comments. From the UI perspective, reactions allow to provide the needed feedback w/o taking too much of the vertical space.

Azure Service Bus has a rich pub/sub mechanism supporting multiple options.

Tooling is an important part of the development experience. No matter how good a service you're using is, if there are no decent tools, you always have that disgruntled feeling about the entire experience. When developing against hosted services, tools are either coming from the service provider or a third party.

Null-Conditional Operator in C# 6 (?.), also known as "Elvis" operator, has allowed compacting code by removing boilerplate code for a null check to avoid NullReferenceException. But there's more to that than just a null check. I've run into a case where Elvis operator also removed need for an extra code to implement a Decorator pattern, which resulted in removing complexity. Here's the original code implemented using Decorator pattern:

Not so long ago Microsoft made a deliberate choice to play the OSS game, and it was quite a welcomed change. Rome wasn't built in a day. So it this initiative. It's a long and bumpy way. Along the way we all, maintainers and contributors, learn along.

When working with Azure Service Bus or Storage Queues, Fiddler help in troubleshooting errors that could happen while talking to the remote service. Particularly useful when there's a mismatch between .NET client library that wraps RESTful API and remote service. Using Fiddler, you can trace the traffic going back and forth. Communication happens over HTTPS and sometimes Fiddler can refuse to show the values. When that happens, you no longer troubleshoot your Azure Service usage, but Fiddler configuration. Luckily, the fix as easy as resetting certificates used by Fiddler.