While Powershell is incredibly flexible, the openness lends itself to be non-specific in some cases, such as for finding out what is keeping a lock on a file.
Why is .GetAwaiter().GetResult(), or .Wait() or .Result bad? It ends up boiling down to deadlocks and threadpool starvation. This post gives a gentle, high up look at why this may happen.
Taking lessons from Part 1 and Part 2, I'll be taking a dive into creating solid foundations for future parts. We'll be looking at flexibility for generation, saving, and printing.
A list of symbol based C# operators, what they do and the links to documentation for times when searching question marks doesn't return what I want.
We all know pooling is useful for performance, so let's check out what .NET comes with out of the box and see how it's all used.
Implementing SqlAzureExecutionStrategy is easy, go ahead and lift it from here but this is also a deep dive into what makes it tick by looking at the EF6 source code for Execution Strategies.
Two and a half simple and practical examples with the Task Parallel Library (TPL) that can be swapped into your code to use up those cores.
The next step: making a stiff, jagged looking map into something a little smoother.