by bill-s, 2019-06-13T12:41:30.423Z
Today, we are announcing .NET Core 3.0 Preview 6. It includes updates for compiling assemblies for improved startup, optimizing applications for size with linker and EventPipe improvements. We’ve also released new Docker images for Alpine on ARM64.
by bill-s, 2019-06-13T12:51:28.360Z
When I was early in my career I would read a blog or watch a video about a relatively basic concept and then the author would suggest an advanced idea and "leave it to the reader" to investigate and implement.
I was watching another great beginner video from Scott Allen "ASP.NET Core Fundamentals" (highly recommend) the other day and something similar came up again.
During the section "Building the User Interface" Scott goes on to create a View Component which can be added into individual pages or onto the layout page so that all pages get the display. The View Component gets the count of restaurants from the data store and displays it in the UI. During the development of this Scott says "If you're in a performance sensitive scenario you might want to cache this value" and this got me thinking.
by bill-s, 2019-06-13T12:49:41.360Z
by shehryarkn2, 2019-06-11T22:22:47.829Z
In this article, I’m not convincing developers that they should always use a Book & stop learning from tutorials, as Tutorials provide a complete solution of a programming problem whereas books can only give you basic concept & you have to implement your required solution.
by bill-s, 2019-06-10T22:49:21.662Z
gRPC is a modern open source RPC framework created by Google. It is based on Google’s modern Protocol Buffer serialization engine but is not tied to it. C# developers who have used WCF in the past, or anyone building C# backend services should take a look at this. gRPC has most of the functionality that WCF has, but you can build on .NET Core. This article will introduce gRPC, explain why WCF developers should pay attention, and talk about why it could be used for any service. According to Scott Hunter at Microsoft:
If you are a remoting or WCF Server developer and want to build a new application on .NET Core, we would recommend either ASP.NET Core Web APIs or gRPC
by bill-s, 2019-06-10T22:48:52.358Z
The long road to C# 9 has already begun and this is the first article in the world about the C# 9 Candidate features. Once you have completed reading this article, you will hopefully be better prepared for the new C# challenges you will meet in the future.
by bill-s, 2019-06-13T12:40:39.557Z
Blazor is one of fantastic technologies I think.
It will be shipped a part of .NET Core 3.0.
There are two different models:
This runs on server-side through SignalR.
This runs on browser using WebAssembly.
However, you can create apps on same programming model.
Of course, it is .NET Core, so you can create Blazor apps on Linux too.
by bill-s, 2019-06-13T12:48:46.493Z
Using React by itself will not result in a highly performant application. If you’re not careful, the application can pick up bloat easily. It’s good practice to conduct audits periodically.
Code splitting is easy to setup with Webpack 4 and you should definitely use it to optimize your application.
Identify where long lists of content are rendered and optimize them with react-window.
Understand how React works internally. This will help you identify wasted renders and fix them. Use the “Highlight Updates” option in React DevTools to help you with this step.
There are several other methods to improve performance in React applications — prefetching, service workers, bundle analysis, etc. to reduce bundle sizes.
by bill-s, 2019-06-13T12:41:04.315Z
I recently embarked on a mission with my colleague Kendall Roden to uncover the feature parity between Visual Studio 2017/2019 and Visual Studio Code when it comes to developing a dockerized Asp.Net Core application. We started by identifying the artifacts that get scaffolded by Visual Studio 2017/2019 which would need to be manually generated with Visual Studio Code. Here is the list that we came up with:
by bill-s, 2019-06-13T12:44:34.284Z
Enabling developers to build resilient microservices is an important goal for .NET Core 3.0
In this episode, Shayne Boyer is joined by Glenn Condron and Ryan Nowak from the ASP.NET team who discuss some of the exciting work that's happening in the microservice space for .NET Core 3.0.
by bill-s, 2019-06-10T22:48:33.629Z
This is my personal collection of notes, scripts and techniques developed to help debug live .NET Core applications. All of these techniques were performed from a sidecar in Kubernetes. If you are interested in profiling .NET Core applications running on Linux without Kubernetes then these guides still will contain a lot of useful information.
by bill-s, 2019-06-13T12:51:51.448Z
This is the twenty-second of a series of posts on ASP .NET Core in 2019. In this series, we’ll cover 26 topics over a span of 26 weeks from January through June 2019, titled A-Z of ASP .NET Core!
by bill-s, 2019-06-13T12:52:37.980Z
Let’s chat about ordering. It’s one of my favorite topics, and something I’ve blogged about extensively before. Previously ordered processing in Azure Functions was only possible with event streams like Azure Event Hubs, but today I want to show how you can preserve order for Service Bus queues and topics as well.
On the surface it seems pretty straight-forward: I want to be able to process messages from a queue in the exact order that I received them. For a simple service running on a machine, it’s pretty easy to achieve. However, how do I preserve the ordering of queue messages when I want to process at scale? With something like Azure Functions I may be processing messages across dozens of active instances, how can I preserve ordering?