The framework will receive updates that cover security issues and breaking browser bugs until December 31st 2021.
Starting January 1st 2022 XLTS.dev team will maintain a fork of the latest version of AngularJS and provide software updates
 

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 

Here are the lists of new APIs obtained:

• 28 New Namespaces
• 359 New Types
• 359 New Types and their 3.845 Members
• 1.044 New Methods in Types that were already there in .NET Core 2.2
• 166 New Fields (mostly Enumeration Values) in Types that were already there in .NET Core 2.2  

Domain-Driven Refactoring - Jimmy Bogard - NDC London 2022

Books, workshops, storming and more, all build up an idealized domain model. All describe great techniques for domain-driven greenfield applications. But what about the code we have? How can we take what's already built, and move it towards a better, more cohesive design?
In this session, we'll look at anemic, procedural, boring code and examine code smells that can point us in the right direction. We'll also look at standard design patterns for more complex behaviors and models, and how to recognize when (and when not) to apply them. Finally, we'll cover how to safely apply refactoring techniques to achieve our domain-driven model nirvana. 

Microsoft Web Template Studio (WebTS) is a Visual Studio Code Extension that accelerates the creation of new web applications using a wizard-based experience. 

we’re about half-way through the release now. Most of the features are now included, but there are still many changes that we expect in the next few previews to complete experiences and round off rough edges that still exist. Take care. 

Domain Driven Design: The Good Parts

The greenfield project started out so promising. Instead of devolving into big ball of mud, the team decided to apply domain-driven design principles. Ubiquitous language, proper boundaries, encapsulation, it all made sense.
But along the way, something went completely and utterly wrong. It started with arguments on the proper way of implementing aggregates and entities. Arguments began over project and folder structure. Someone read a blog post that repositories are evil, and ORMs the devil incarnate. Another read that relational databases are last century, we need to store everything as a stream of events. Then came the actor model and frameworks that sounded like someone clearing their throat. Instead of a nice, clean architecture, the team chased the next new approach without ever actually shipping anything.
Beyond the endless technical arguments it causes, domain-driven design can actually produce great software. We have to look past the hype into the true value of DDD, what it can bring to our organizations and how it can enable us to build quality systems. With the advent of microservices, DDD is more important than ever - but only if we can get to the good parts. 

Why could there not be another tool that allowed a development team to harness their existing source control systems, but make database changes a part of the workflow? Enter SQL Source Control by Redgate. 

CodeRabbit is an app that fully integrates into your GitHub repos, reviews your code, and then suggests changes that should be made.

What are some examples of websites that use .NET Core?