Want to receive every Tuesday the best .NET links?
Once subscribed you can login, submit a link and receive the weekly newsletter.
by cezarypiatek, 2019-08-19T15:18:39.785Z
I’ve decided to create a series of blog posts where I will present what I’ve recently learned about the traps related to the multithreading in C#. I will also show you my proposition of Roslyn analyzers that can possibly help to avoid those issues right at the stage of writing the code. This part is about choosing a suitable object for locking.by bill-s, 2019-08-19T23:26:54.912Z
In this post, I show how you could implement a plugin system that can unload the plugins dynamically. I also provide some background information behind the techniques and classes involved. Unlike the AppDomain, the AssemblyLoadContext lets you unload the plugin types and the owned assemblies - sounds promising, right?by bill-s, 2019-08-19T23:29:07.044Z
Recently got chances to work on Azure DevOps for Desktop (UWP/WPF/Desktop Bridge/MSIX) , and often need to CI/CD .Net Core and .Net Standard. Most of them are related to SDK setup, NuGet version update, TargetPlatform settings, or Code Sign Certificate trust. This article is to give quick references on how to solve common CI issues for this scenario.by bill-s, 2019-08-19T23:29:44.027Z
Regular visitors of my blog will know that I’ve written a lot of posts about the HttpClientFactory feature, available in the Microsoft.Extensions.Http package which simplifies the consumption and proper lifetime usage of HttpClient instances. Recently, I’ve begun digging into gRPC and I’m pleased to see a similar pattern is available for gRPC-based communication. In this post, I want to show a quick example of how to get started with the gRPC Client Factory. I’m going to focus on adding this to an ASP.NET Core 3.0 web project, which will act as a client of an external gRPC service. This post assumes a little knowledge about gRPC. You can read my earlier blog post (slightly outdated now) which covers some extra ground.by bill-s, 2019-08-19T23:26:08.063Z
In Part 1, we explored why front-end performance is an essential ingredient for any website serious about achieving its goals. We then learned about the common metrics which are used to measure major performance as well as some for the best tools to collect this data for you. Now that we know how to measure and understand a website’s current performance, in Part 2, we’re going to talk about some of the recommended front-end performance optimization techniques you can use to improve it. All of these can be built into your web development workflow starting today.by bill-s, 2019-08-19T23:30:46.721Z
Table of contents Section 0: The Golden Rule Single advice that inspires all the others (1 special bullet) Section 1: The Test Anatomy The foundation - structuring clean tests (12 bullets) Section 2: Backend Writing backend and Microservices tests efficiently (8 bullets) Section 3: Frontend, UI, E2E Writing tests for web UI including component and E2E tests (11 bullets) Section 4: Measuring Tests Effectiveness Watching the watchman - measuring test quality (4 bullets) Section 5: Continous Integration Guidelines for CI in the JS world (9 bullets)by bill-s, 2019-08-19T23:23:52.404Z
Logging is a big part of software development for many years now. One can argue that a logging mechanism is a must-have part of any application or library. I would agree with that statement. Logging has a crucial part to play in a scenario where you can’t use interactive debugging (that is, attaching a debugger like Visual Studio). It allows us to investigate errors after the problem already happened. In some cases, like Production Debugging, logs might be the only information you have.