For an application, logging is very important to keep track of that application and keep it error-free. In .NET Core, we don't need any third party logging; instead, we can use built-in logging whenever we want. This is very efficient in terms of code and performance.

Let’s start. Create a new .NET Core application and name it. 

C# is usually thought of as a backend, server-side language. But with the Blazor-Web Assembly combo, developers can use it for client-side as well. 

Writing clean code that follows industry standards is always a good idea. But it's usually easier said then done. Read on for overview of writing clean code. 

System.IO.Pipelines is a new library that is designed to make it easier to do high performance IO in .NET. It’s a library targeting .NET Standard that works on all .NET implementations. 

Use the DocumentDB Nuget package to quickly build a simple but complete ASP.NET MVC core application based on Azure Cosmos DB.  

We can now run ASP.NET Core applications as Windows services with minimal effort. This blog post introduces how this process is done.

During the last Build conference, Microsoft has announced the next version of Visual Studio with C# 7.3 support. This is yet another minor language update with some quite interesting features. The main change was related to generics, starting from C# 7.3 there 3 more constraints: unmanaged, System.Enum and System.Delegate. 

In this post, we are going to write about what we consider to be the best practices while developing the .NET Core Web API project. How we can make it better and how to make it more maintainable.

We are going to go through the following sections:

• Startup Class and the Service Configuration
• Project Organization
• Environment Based Settings
• Data Access Layer
• Controllers
• Actions
• Microsoft.AspNetCore.All Meta-Package
• Routing
• Logging
• CryptoHelper
• Content Negotiation
• Using JWT
• Conclusion  

Some months ago a feature landed in Xamarin.Forms that seemed to truly polarize the Xamarin.Forms community: support for styling applications using CSS. Some argued that it was an unnecessary introduction to "Web" technology to the native development experience, and others that it simply isn't the right solution to the problem.  While I sympathize with the latter opinion and think there's plenty of room for some good debate on the right path forward, I count myself as part of a third camp: I think that CSS is a powerful (and frequently maligned) solution to the problem of styling native mobile applications.