Want to receive every Tuesday the best .NET links?
Once subscribed you can login, submit a link and receive the weekly newsletter.
by bill-s, 2018-03-10T00:49:40.600Z
Today, we are announcing .NET Core 2.1 Preview 1. It is the first public release of .NET Core 2.1. We have great improvements that we want to share and that we would love to get your feedback on, either in the comments or at dotnet/core #1297.by bill-s, 2018-03-13T06:26:53.256Z
In a past life, I was a web developer. In this post, I’d like to take an outsiders perspective on a couple of developments that I think will be hugely disruptive in the coming years. The first of these is .NET Core making it possible to run .NET websites on cheap hosting. The second is Blazor, which promises to let us use .NET for front-end web scripting – replacing Javascript. This post is a bit more soapbox-y than usual, so bear with me!by bill-s, 2018-03-10T00:49:40.600Z
In this tutorial we’ll build a IoC container from scratch which supports transient and singleton registries. The code we write is fully unit tested with NUnit and I think you’ll learn some valuable tips.by bill-s, 2018-03-10T02:44:33.871Z
In this blog series, I'm going to create a small chat application using React and ASP.NET Core, to learn more about React and to learn how React behaves in an ASP.NET Core project during development and deployment.by tushar, 2018-03-12T00:24:20.256Z
Based on the scope of the impact made by a smell, we may perceive smells in three categories – implementation smells, design smells, and architecture smells. Implementation smells have limited scope, typically confined to a class or file, have a limited local impact, and require relatively the least effort to refactor. Long method, magic number, and empty catch block are the examples of implementation smells. Design smells impact a set of classes and thus refactoring a design smell may introduce a change in a few classes. Examples of design smells are insufficient modularization (god class), multifaceted abstraction (divergent change), and broken hierarchy (refused bequest). Further, architecture smells span multiple components and have a system level impact. Let us understand various architecture smells that may arise in a software system.by atsvetkov, 2018-03-12T00:28:08.575Z
In recently released .NET Core 2.1 Preview 1, tools packages can be installed globally on the machine. This article explains how it works and shows how to create a small development web server utility, which exposes current directory contents via HTTP with a simple "dotnet serve" command.by tpeczek, 2018-03-12T08:32:54.941Z
ASP.NET Core comes with out-of-the-box support for server side in-memory response caching. This post shows how to replace in-memory approach with Redis and address durability and load balancing.by dnwuBkFzB5iuz, 2018-03-12T00:59:08.479Z
This is yet another post in a <a href='https://www.carlrippon.com/scalable-and-performant-asp-net-core-web-apis-introduction/' target='blank'>series</a> on creating performant and scalable web APIs using ASP.NET Core. In this post, we'll start to focus on caching. Often the slowest bit of a web API is fetching the data, so, if the data hasn't changed it makes sense to save it in a place that can be retrieved a lot quicker than a database or another API call. We will focus on leveraging standard HTTP caching and in this post we'll focus on client side caching. There are 2 HTTP caching approaches: - <strong>expiration</strong> and <strong>validation</strong>by dnwuBkFzB5iuz, 2018-03-13T02:54:25.918Z
Carrying on from the last post in this series on creating performant and scalable web APIs using ASP.NET Core, we're going to continue to focus on caching. In this post we'll implement a shared cache on the server and clean the code up so that it can be easily reused.by bill-s, 2018-03-10T14:40:19.172Z
SOLID is one of the most popular sets of design principles in object-oriented software development. It’s a mnemonic acronym for the following five design principles: - Single Responsibility Principle - Open/Closed Principle - Liskov Substitution Principle - Interface Segregation Principle - Dependency Inversionby bill-s, 2018-03-10T14:40:19.172Z
Many development teams have spent the last few years organizing and empowering cross-functional teams, building independently managed microservices, and implementing DevOps pipelines to go faster than ever! These industry shifts, critical for organizations to plan less and react more, solved old problems while creating new ones. As we focused on designing domain-aligned microservices, we also engineered JSON-hungry responsive UIs, Single Page Apps, and portals to consume them. A ton of client-side code has been thrown into our frontend layers creating monoliths, which are often maintained by a different team. Front ends have become increasingly more complex, interdependent and highly coupled to whatever Angular-React-Ember-Vue framework was cool when it was built.by bill-s, 2018-03-10T14:40:19.172Z
In my previous post I detailed how to setup JWT authentication with ASP.NET Core 2, Angular 5, and Facebook OAuth. It received some great feedback and also a few requests to make a Vue.js version - so here it is! The final product is the same, simple demo we saw in the previous post with a flow to support email registration/login as well as facebook login. Both paths lead to a super-duper secure area of the app only authenticated users can access.by bill-s, 2018-03-10T00:49:40.600Z
A quick introduction to getting started collaborating using VS Live Share.