npm security update: Attack campaign using stolen OAuth tokens 

This article is about creating ASP.NET Core applications, using Visual Studio Code and .NET Core. After this article, you will be able to create applications, using Visual Studio Code in .NET Core

This release contains some minor bug fixes and a couple of new features specifically targeted at enabling .NET Standard support for the ASP.NET Web API Client.  

Building and testing a ASP.Net Core 3.0 application using GitHub Actions 

• .NET Core 2.1
• Entity Framework Core
• MediatR
• Marten
• Eureka
• Ocelot
• JWT Tokens
• RestEase
• RawRabbit
• NHibernate
• Polly
• NEST (ElasticSearch client)
• Dapper
• DynamicExpresso
• SignalR 

Steve Smith shows us a starting point for building ASP.NET Core apps in Visual Studio using a clean architecture.  

One of the most exciting announcements during this year’s Connect(); event was the ability to embed .NET libraries into existing iOS (Objective-C/Swift) and Android (Java) applications with .NET Embedding. This is great because you can start to share code between your iOS and Android applications, and you can also share the user interface between your apps when you combine .NET Embedding with Xamarin.Forms Native Forms. This means that you can leverage your existing investments and apps without having to re-write them from scratch to start adding cross-platform logic and UI. In fact, during the Connect(); keynote I showed how I was able to extend the open source Swift-based Kickstarter iOS application with .NET Embedding and Xamarin.Forms Native Forms. You can check out the clip below. 

This article explains step-by-step the server-side manipulation of SVG using Microsoft ASP.NET and C#. The example server-side application demonstrates how simple and complex maps can easily be represented using SVGs.  

It is common when working on a web application, comprised of a server-side Web API, running on a framework like ASP.NET or NestJS, and a client-side Single Page Application (SPA), running on a framework like Angular, to refer to the server-side as "the back-end" and to the client-side as "the front-end". I've been a culprit of this until recently.