.NET 5 Is the Future of .NET: What Every .Net Developer Must Know

Microsoft announced the new .NET 5 (future of .NET) at the Build 2019 conference. .NET 5 will be the single unified platform for building applications that runs on all platforms(Windows, Linux) and devices (IoT, Mobile).
If you are .NET developer currently supporting enterprise applications developed in .NET framework, you need to know how the .NET 5 is going to affect your current enterprise application in the long run. .Net 5 is based on .Net Standard which means not every .Net framework features will be available in .Net 5. Also, there are some technology stacks like web forms, WCF and WWF is not porting into .Net 5. We will look into the details of what is not covered in .Net 5 and what are the alternatives.

Link: https://dzone.com/articles/net-5-is-the-future-of-net-what-every-net-develope?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

.NET Blogs to Follow: The Ultimate List

Back in the day, books were the only way to gain knowledge. I remember spending hundreds of hours in book stores and in the local library, digging up old books about programming. Fast forward to 2019 and my focus has almost entirely shifted to blogs. Here’s my personal list of my recommendations for .NET blogs to follow.

Scott Hanselman: He really doesn’t need any introduction. Scott’s blog is one of the best resources for .NET developers. Besides blogging about .NET, Scott also writes a lot of interesting posts about productivity.

Link: https://dzone.com/articles/net-blogs-to-follow-the-ultimate-list-1?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

Worker Service Template in .NET Core 3.0

With ASP.NET Core 3.0 Preview 3, we get a template for background processes like Windows services and Linux daemons. The new project template is called Worker Service and this post shows how it works and how to use it.
Creating a Worker Service Application
After downloading .NET Core 3.0 Preview 3, open Visual Studio 2019, create new ASP.NET Core web application, and select Worker service as the project type.

Link: https://dzone.com/articles/worker-service-template-in-net-core-30?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

Serving Pre-Compressed Static Files in ASP.NET Core

Optimizing web applications is important because more economic web applications consume fewer CPU cycles and need less bandwidth — resources we have to pay for. It’s easy to turn on response compression on ASP.NET Core, but serving pre-compressed files needs more work. This blog post shows how to do it.
Why Pre-compressed Files?
Although it’s possible to compress files dynamically, when files are requested from a server it means additional work for the web server. Files to be compressed are changed only when a new deployment of the application is made. And the better compression we want the more work has CPU to do.

Link: https://dzone.com/articles/serving-pre-compressed-static-files-in-aspnet-core?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

How to Exclude Code From Code Coverage

Recently I blogged about how to generate nice code coverage reports for ASP.NET Core and .NET Core applications. This blog post focuses on how to leave out all code that will not be covered with unit tests from code coverage and get numbers shown on code coverage reports correct.
What to Exclude From Code Coverage?
I think almost all applications have some classes we don’t want to test. The usual candidates are primitive models and Data Transfer Objects (DTO). One example is given below: 

Link: https://dzone.com/articles/how-to-exclude-code-from-code-coverage?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

How to Implement Pagination in an ASP.NET Core App

When you have to show hundreds or thousands of records on your web page then you should apply pagination. This is because your users must not see all the records on the same page (which looks bad), instead, they move from one page to another page, and only see the records of the selected page.
Pagination brings cleanliness in your web page. It is an important technique which you should never miss to use. In this tutorial, I will teach you how to create pagination in Records in ASP.NET Core.

Link: https://dzone.com/articles/create-pagination-in-records-in-aspnet-core?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

Event Aggregator for ASP.NET Core 3 Razor Components/Blazor

Blazor.EventAggregator is a lightweight Event Aggregator for Razor Components. Razor Components (and formerly known as Blazor) is an upcoming technology included in ASP.NET Core 3.0 (currently in Preview 2).
Event aggregators are used for indirect component to component communication. In event aggregator patterns, you have message/event publishers and subscribers. In the case of Razor Components, the component can publish its events and other component(s) can react to those events.

Link: https://dzone.com/articles/event-aggregator-for-aspnet-core-3-razor-component?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

ASP.NET Core Response Compression

ASP.NET Core supports response compression. From popular algorithms, gzip and Brotli are supported. Those who like can also implement their own response compression providers. This blog post shows how response compression works in ASP.NET Core.
With ASP.NET Core we have three options for compression:

Link: https://dzone.com/articles/aspnet-core-response-compression?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

Telerik UI for Blazor 0.2.0 Free Preview Available

Telerik UI for Blazor 0.2.0 is available for download today. This release makes Telerik UI for Blazor compatible with Visual Studio 2019 preview 2, and ASP.NET Core 3.0 preview 2.
A few weeks ago we released an early preview of Telerik UI for Blazor. The early preview is intended to give developers a peek into the development process while giving everyone a chance to share their feedback on the product. We are working closely to align our goals with those of Microsoft’s ASP.NET Core team, which is why we’re happy to announce Telerik UI for Blazor 0.2.0. This new version aligns our UI components with the ASP.NET Core 3.0 preview 2 and Blazor 0.8.0 release.

Link: https://dzone.com/articles/telerik-ui-for-blazor-020-free-preview-available?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev