CircuitBreaker.Net is an implementation of the Circuit Breaker pattern for .NET. This pattern can improve the stability and resiliency of your application, especially in SOAP, microservices and distributed environments.  

quicktype generates types and helper code for reading JSON in C#, Swift, TypeScript, Go, Objective-C, C++ and more. Customize online with advanced options, or download a command-line tool.  VSCode Plugin

Report Designer can be redistributed at no extra cost, Designer can be launched with .NET without a single line of code

we extract language rankings from GitHub and Stack Overflow, and combine them for a ranking that attempts to reflect both code (GitHub) and discussion (Stack Overflow) traction. The idea is not to offer a statistically valid representation of current usage, but rather to correlate language discussion and usage in an effort to extract insights into potential future adoption trends.

Get Started Building Microservices with ASP.NET Core and Docker in Visual Studio Code 

Clean code is C# code that is easy to read and understand, both for the original author and any future developers who may need to work on the codebase. It is a code that follows best coding practices and is organized in a logical way. 

A modular, service based web application model

Code generator to produce initial services / user interface code for an SQL table

T4 based code generation on server to reference script widgets with intellisense / compile time validation

T4 based code generation to provide compile time type safety and intellisense while calling AJAX services from script side.

An attribute based form definition system (prepare UI in server side with a simple C# class)

Automatic seamless data-binding through form definitions (form <-> entity <-> service).

Caching Helpers (Local / Distributed)

Automatic cache validation

Configuration System (storage medium independent. store settings in database, file, whatever...)

Simple Logging

Reporting (reports just provide data, has no dependency on rendering, similar to MVC)

Script bundling, minification (making use of Node / UglifyJS / CleanCSS) and content versioning (no more F5 / clear browser cache)

Fluent SQL Builder (SELECT/INSERT/UPDATE/DELETE)

Micro ORM (also Dapper is integrated)

Customizable handlers for REST like services that work by reusing information in entity classes and do automatic validation.

Attribute based navigation menu

UI Localization (store localized texts in json files, embedded resource, database, in memory class, anywhere)

Data Localization (using an extension table mechanism helps to localize even data entered by users, like lookup tables)

Script widget system (inspired by jQueryUI but more suitable for C# code)

Client side and server side validation (based on jQuery validate plugin, but abstracts dependency)

Audit logging (where CDC is not available)

System for data based integration tests

Dynamic scripts

Script side templates 

IKVM is an implementation of Java for the Microsoft .NET platform. It can be used to quickly and easily:

• Execute compiled Java code (bytecode) on .NET Framework or .NET Core
• Convert bytecode to a .NET assembly to directly access its API in a .NET project 

Vertical Slice Architecture, not Layers! 

Why Vertical Slice Architecture? Nobody wants to deal with a system that is hard to change and easy to introduce bugs because it's a spaghetti code mess of various technical concerns. Clean Architecture is popular because it separates concerns into many different layers. But why are we organizing code by layers? Does adding a new feature require you to modify files across multiple projects in your UI, business, and data access layers? Vertical Slice Architecture is about how you organize code and focus on features instead of technical layers will make your system easier to change. 

Earlier this year, Microsoft announced their support for Blazor, and now Frank A. Krueger has developed the Ooui library which allows C# or F# to be used to write applications that run in the browser.  Ooui can target WASM, enabling Xamarin.Forms app to be deployed in web assembly and the result runs entirely in-browser without the need for an application server.