In my earlier post Getting Started: Xamarin Forms with .NET Standard I covered how to create a new Xamarin Forms project which uses a .NET Standard 1.4 library to share the views between iOS, Android and UWP. 

With your dependency graph enabled, we’ll now notify you when we detect a vulnerability in one of your dependencies and suggest known fixes from the GitHub community. 

We are going to talk about:

What you get out of the box with ASP.NET Core 2.0
How to use Postman to test your API
Changing the default configuration of our project
Testing the content negotiation
Restricting media types
More about formatters
Implementing a custom formatter
Consuming API programmatically 

Try Bazel’s opt-in preview in Angular CLI

In Google we build all our software with a tool called Bazel. We’ve been using it for the past over 12 years to build projects with any size — from small internal apps, to large applications such as Gmail, Google Drive, and Google Cloud Console. 

Why Serilog? It is easy to set up, has a clean API, and is portable between recent .NET platforms. The big difference between Serilog and the other frameworks is that it is designed to do structured logging out of the box. Another thing I really like about Serilog is that it can be configured via the appsetting.json file alongside configuring through code. Changing logging configuration without touching the codebase is really helpful, especially in the production environment. 

Anatomy of the .NET dictionary

The internals of the .NET Dictionary class is a very common interview topic, so the information in this post might come in handy one day. Alternatively, use this new-found knowledge to impress friends and colleagues at every opportunity!

• .NET Core 3.1.7 and .NET Core SDK ( Download | Release Notes )
• .NET Core 2.1.21 and .NET Core SDK ( Download | Release Notes ) 

• .NET Core 2.2.7 and .NET Core SDK ( Download | Release Notes )
• .NET Core 2.1.13 and .NET Core SDK ( Download | Release Notes ) 

• .NET Core 2.2.6 and .NET Core SDK ( Download | Release Notes )
• .NET Core 2.1.12 and .NET Core SDK ( Download | Release Notes ) 

Developed by Microsoft’s Research in Software Engineering, Code Contracts provide a way to convey code assumptions in your .NET applications. They can take the form of preconditions, postconditions, and state invariants. In C# Code Contracts Succinctly, author Dirk Strauss demonstrates how to use Code Contracts to validate logical correctness in code, how they can be integrated with abstract classes and interfaces, and even how they can be used to make writing documentation less painful.