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

ASP.NET Core 2.1: A Boon to Modern Web Application Development

Customized enterprise application development with unique features and the latest programming languages was a tale of another world a decade ago. It required a significant amount of time and money to offer the optimum user experience. However, today, digitization has made a 360-degree revolution in the software industry.
When it comes to developing a customized enterprise web application, you choose from a vast set of technologies. The most prominent among them all is ASP.NET. It has the perfect combination of web development models offering all the services required for building robust enterprise web applications.

Link: https://dzone.com/articles/aspnet-core-21-a-boon-to-modern-web-application-de

ASP.NET Core with Entity Framework Core: Returning Multiple Result Sets

One of the things I like most about Entity Framework is the various ways you can retrieve data to hydrate your entities.
You can retrieve data using LINQ (command or fluent with methods), ExecuteQuery (and all of it’s various flavors), or even ADO.NET with straight SQL.

Link: https://dzone.com/articles/aspnet-core-with-entity-framework-core-returning-m?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

Customizing ASP.NET Core Part 10: TagHelpers

This was initially planned as the last post of this series because this also was the last part of the talk about customizing ASP.NET Core I did in the past. See the initial post about this series. Now I have three additional customizing topics to talk about. 
In this tenth part of this series, I’m going to write about TagHelpers. The built-in TagHelpers are pretty useful and make pages prettier and more readable. Creating custom TagHelpers will make your life much easier.

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

Creating a Basic Web Site From an ASP.NET Core Empty Project

I recently wanted to do a very quick proof of concept, regarding the use of setInterval versus setTimeout after reading that setTimeout was referable if you were calling the same function very rapidly. I thought I’d note down my journey from File -> New Project to having the POC running so that, next time, I don’t have to re-lookup the various parts.
File -> New Project
If you create a brand new ASP.NET Core 2.1 project, select the empty project, and then run the generated code, you’ll see this:

Link: https://dzone.com/articles/creating-a-basic-web-site-from-an-aspnet-core-empt?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

ASP.NET Core: Replacement for Server.MapPath

ASP.NET Core offers two different locations for files:

Content root – this is where application binaries and other private files are held.
Web root – this is where public files are held (wwwroot folder in web project).

By default, web root is located under content root. But there are also deployments where web root is located somewhere else. I have previously seen such deployments on Azure Web Apps. It’s possible that some ISPs also use different directories in trees for application files and web root.

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