Skip to main content


.NET Core MVC Application File Upload To Physical Location With Buffered Technique

Buffering Technique In File Upload: The server will use its Memory(RAM) or Disk Storage to save the files on receiving a file upload request from the client.  Usage of Memory(RAM) or Disk depends on the number of file requests and the size of the file.  Any single buffered file exceeding 64KB is moved from Memory to a temp file on disk.  If an application receives heavy traffic of uploading files there might be a chance of out of Disk or RAM memory which leads to crash application. So this Buffer technique used for small files uploading. In the following article, we create a sample for the file uploading using .NET Core MVC application. Create The .NET Core MVC Project: Let's create a .NET Core MVC project, here for this sample I'm using Visual Studio Code as below.   Check the link to use the Visual Studio Code for .NET Core Application . IFormFile: Microsoft.AspNetCore.Http.IFormFile used for file upload with buffered technique. On uploading files f

Steps To Create, Run And Debug Dotnet Core Application In Visual Studio Code

Introduction: Microsoft Visual Studio Code is a lightweight editor that supports most of the programming languages. Dotnet Core can be run and debug using Visual Studio Code as we do in Visual Studio editor which is the recommended and famous editor for Dotnet Applications. Before starting anything, install the latest version of Dotnet Core SDK from the Microsoft DotnetCore website and also download the Visual Studio Code editor which is the free editor. C# for Visual Studio Code Extensions: In Visual Studio Code, we can get a lot of extensions plugins which makes development more easy and fast. Similarly to work with C# we need to install the VS Code extension of "C# for Visual Studio Code". Few features of this extension like: .NET Core lightweight development tool. Good C# editing support. Syntax Highlighting. Good Code Intellisense. Nice debugging support. Create A Dotnet Core Solution: In Visual Studio solution file automatically get cr

Ionic Angular Page Life Cycle Methods

Page Life Cycle Methods: Page life cycle methods are like default method gets executed on navigate to the page. Major life cycle methods in the Ionic application are: ionViewWillEnter ionViewDidEnter ionViewWillLeave ionViewDidLeave Route Effects On Ionic Page State: In angular <router-outlet> prebuild component where any page will be displayed inside of it dynamically based on route configuration components. Ionic with angular we have route template like <ion-router-outlet> which is extended from <router-outlet>. On using <ion-router-outlet> ionic navigation work like :- In an ionic application when the user navigates to a new page, ionic will save or store the old page(old page exists within the DOM in the hidden state) and display the new page. Now if the user clicks on the old page link from the current page, ionic loads the old page from the storage(this means components will not be initialized freshly). It is like a cache for pe

How Response Caching Works In Asp.Net Core

What Is Response Caching?: Response Caching means storing of response output and using stored response until it's under it's the expiration time. Response Caching approach cuts down some requests to the server and also reduces some workload on the server. Response Caching Headers: Response Caching carried out by the few Http based headers information between client and server. Main Response Caching Headers are like below Cache-Control Pragma Vary Cache-Control Header: Cache-Control header is the main header type for the response caching. Cache-Control will be decorated with the following directives. public - this directive indicates any cache may store the response. private - this directive allows to store response with respect to a single user and can't be stored with shared cache stores. max-age - this directive represents a time to hold a response in the cache. no-cache - this directive represents no storing of response and always fetch the fr

Endpoint Routing In Asp.Net Core

How Routing Works In  Core 2.1 And Below Versions?: In Asp.Net Core routing is configured using app.UseRouter() or app.UseMvc() middleware. app.UseMvc(routes => { routes.MapRoute( name: "default", template: "{controller=Home}/{action=Index}/{id?}"); }); Here in Dotnet Core version 2.1 or below versions on the execution of route middleware request will be navigated appropriate controller matched to the route. An operation or functionality which is dependent on route URL or route values and that need to be implemented before the execution of route middleware can be done by accessing the route path from the current request context as below app.Use(async (context, next) => { if(context.Request.Path.Value.IndexOf("oldvehicle") != -1) { context.Response.Redirect("vehicle"); } else { await next(); } }); app.UseMvc(routes => { routes.MapRoute( name: "vehicleRoute", template: "vehicle", defaul