What is Blazor and what is Razor Components?

#252 – March 31, 2019

sponsor

Find A Job Through Vettery

Vettery specializes in tech roles and is completely free for job seekers. How does it work? You apply to join the platform, and once accepted, you’ll start receiving interview requests directly from top companies growing their tech teams. You decide which interviews you want to take, all from the comfort of your inbox!

this week's favorite

What is Blazor and what is Razor Components?

Blazor is a single-page app framework for building interactive client-side Web apps with .NET. Blazor uses open web standards without plugins or code transpilation. Blazor works in all modern web browsers, including mobile browsers.

Azure Service Bus Message Deferral Implementation

I was recently tasked to create an API that needs to be resilient and decoupled from other systems. So, we used Azure’s Service Bus for this. This API is used in a way where it receives instructions in an order, and that order matters. This part is key.

Memory and Span usage guidelines

NET Core includes a number of types that represent an arbitrary contiguous region of memory. .NET Core 2.0 introduced Span and ReadOnlySpan, which are lightweight memory buffers that can be backed by managed or unmanaged memory. Because these types can be stored on the stack, they are unsuitable for a number of scenarios, including asynchronous method calls. .NET Core 2.1 adds a number of additional types, including Memory, ReadOnlyMemory, IMemoryOwner, and MemoryPool. Like Span, Memory and its related types can be backed by both managed and unmanaged memory. Unlike Span, Memory can only be stored on the managed heap.

Profiling .NET Code with PerfView and visualizing it with speedscope.app

According to the official web page, speedscope.app is “a fast, interactive web-based viewer for performance profiles”. But I believe it’s more than that! In my opinion, it’s one of the best visualization tools for performance profiles ever!

Storing UTC is not a silver bullet

When I read Stack Overflow questions involving time zones, there’s almost always someone giving the advice to only ever store UTC. Convert to UTC as soon as you can, and convert back to a target time zone as late as you can, for display purposes, and you’ll never have a time zone issue again, they say.

newsletters