ASP.NET Core 2.2 preview – Updated routing handling

We’re making a big investment in routing starting in 2.2 to make it interoperate more seamlessly with middleware. For 2.2 this will start with us making a few changes to the routing model, and adding some minor features. In 3.0 the plan is to introduce a model where routing and middleware operate together naturally. This post will focus on the 2.2 improvements, we’ll discuss 3.0 a bit further in the future.

Source: ASP.NET Core 2.2.0-preview1: Endpoint Routing | ASP.NET Blog

Custom error pages in ASP.NET MVC

Excellent blog post by Ben Foster:
Custom error pages in ASP.NET MVC. Easy, right? – Ben Foster

My extra take on it was to create content in the static .html pages and use an iframe inside the aspx based pages (to reuse the content easily).

E.g: (my 500 error page is named Error500.aspx)

<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Error500.aspx.cs" Inherits="Error500" %>
<% Response.StatusCode = 500; %>

<!DOCTYPE html>

<html xmlns="">
<head runat="server">
    <title>An error has occurred - 500</title>
    <style>iframe, html, body { height: 100%; width: 100%; margin: 0; border: 0; padding: 0; }</style>
    <iframe src="Error500.html"></iframe>


Architect modern web applications with ASP.NET Core and Azure | Microsoft Docs

.NET Core and ASP.NET Core offer several advantages over traditional .NET development. You should use .NET Core for your server applications if some or all of the following are important to your application’s success:

  • Cross-platform support

  • Use of microservices
  • Use of Docker containers
  • High performance and scalability requirements
  • Side-by-side versioning of .NET versions by application on the same server


Online: Architect modern web applications with ASP.NET Core and Azure | Microsoft Docs

How to increase upload size of a document in an application. | The ASP.NET Forums

Re: how to increase upload size of a documnet upto 20 MB….in an application. Aug 04, 2013 08:25 AM|LINK You likely will need to update your maxRequestLength within your web.config to handle files and uploads that are large (as the default limit is often 4MB). This can be handled within the section of your web.config or the section if you want to handle it at the IIS level (both are probably a good idea). It’s important to know that maxAllowedContentLength is measured in bytes and maximumRequestLength is measured in kilobytes when settings these values so you’ll need to adjust them accordingly if you plan on handling much larger files :  If you wanted to use 20MB as a limit, you would need to change the values to the following respectively :  If you don’t see these sections within your existing web.config file, you’ll simply need to copy them in. Updating the maxRequestLength property is likely going to be the easiest method of handling this, however there are alternatives such as libraries like NeatUpload, which are designed to handle large files and can handle uploading files as streams to your preferred method of storage.

Source: how to increase upload size of a documnet upto 20 MB….in an application. | The ASP.NET Forums

Stackify Prefix – ASP.NET Profiler

Prefix will help troubleshoot what your code is doing by inspecting key methods, database queries, web service calls, and logging statements.

Prefix is designed for developers to use everyday as they write & test their own code. Prefix answers the question of “What just happened” in my code.

Free to use with a few limitation (shows 1000 latest requests etc.)
Source: What is Stackify Prefix?

Getting started videos: