ASP.NET

     Microsoft ASP.NET is a web development framework that’s used to build dynamic web pages, interactive web services, and robust data-driven web applications. It is a part of Microsoft .NET framework.

ASP.NET stands for Active Server Pages Network Enabled Technologies. In 2002, Microsoft released the first version of the ASP.NET framework. It was based on the CLR (Common Language Runtime), which enables developers to build ASP.NET applications in different .NET supported languages including C#, F#, and VB.NET.

The ASP.NET framework is based these key components:

·         CLR

·         Variety of languages

·         Standard class library

With the help of such components, it provides support for various programming models including ASP.NET Web Forms, ASP.NET MVC, ASP.NET Web API, and SignalR.

Some common characteristics of ASP.NET framework are:

·         Code-behind mode

·         State management

·         Caching

Some key advantages of using ASP.NET framework are:

·         Minimized length of the code

·         Language-independent

·         Provides high level of performance

·         Widely used for enterprise-level web applications

In this article, we will introduce you to some of the common online resources that will help you to learn the ASP.NET framework. These resources are ideal for all skill levels including novice, intermediate, and advanced programmers.

Projects and Solutions

  A typical ASP.NET application consists of many items: the web content files (.aspx), source files (.cs files), assemblies (.dll and .exe files), data source files (.mdb files), references, icons, user controls and miscellaneous other files and folders. All these files that make up the website are contained in a Solution. When a new website is created, VB2008 automatically creates the solution and displays it in the solution explorer. Solutions may contain one or more projects. A project contains content files, source files, and other files like data sources and image files. Generally, the contents of a project are compiled into an assembly as an executable file (.exe) or a dynamic link library (.dll) file. Typically a project contains the following content files:

 · Page file (.aspx)

· User control (.ascx)

· Web service (.asmx)

· Master page (.master)

· Site map (.sitemap)

· Website configuration file (.config)

Building and Running a Project

You can execute an application by:

· Selecting Start

· Selecting Start Without Debugging from the Debug menu,

 · pressing F5

· Ctrl-F5

The program is built meaning, the .exe or the .dll files are generated by selecting a command from the Build menu.

ASP.NET life cycle specifies how:

· ASP.NET processes pages to produce dynamic output

 · The application and its pages are instantiated and processed

 · ASP.NET compiles the pages dynamically ASP.NET life cycle could be divided into two groups:

 · Application Life Cycle

· Page Life Cycle

Getting started with Visual Web Developer

 

ASP.NET Application Life Cycle

 The application life cycle has the following stages:

 1. User makes a request for accessing application resource, a page. Browser sends this request to the web server.

  2. A unified pipeline receives the first request and the following events take place:

·   An object of the class Application Manager is created.

· An object of the class Hosting Environment is created to provide information regarding the resources.

·  Top level items in the application are compiled.

 3. Response objects are created. The application objects such as HttpContext, HttpRequest and HttpResponse are created and initialized.

 4. An instance of the HttpApplication object is created and assigned to the request.

 5. The request is processed by the HttpApplication class. Different events are raised by this class for processing the request.

ASP.NET Page Life Cycle

   When a page is requested, it is loaded into the server memory, processed, and sent to the browser. Then it is unloaded from the memory. At each of these steps, methods and events are available, which could be overridden according to the need of the application. In other words, you can write your own code to override the default code.

The Page class creates a hierarchical tree of all the controls on the page. All the components on the page, except the directives, are part of this control tree. You can see the control tree by adding trace= "true" to the page directive. We will cover page directives and tracing under 'directives' and 'event handling'.

The page life cycle phases are:

• Initialization
• Instantiation of the controls on the page
• Restoration and maintenance of the state
• Execution of the event handler codes
• Page rendering

Understanding the page cycle helps in writing codes for making some specific thing happen at any stage of the page life cycle. It also helps in writing custom controls and initializing them at right time, populate their properties with view-state data and run control behavior code.

Following are the different stages of an ASP.NET page:

· Page request - When ASP.NET gets a page request, it decides whether to parse and compile the page, or there would be a cached version of the page; accordingly the response is sent.

· Starting of page life cycle - At this stage, the Request and Response objects are set. If the request is an old request or post back, the IsPostBack property of the page is set to true. The UICulture property of the page is also set.

· Page initialization - At this stage, the controls on the page are assigned unique ID by setting the UniqueID property and the themes are applied. For a new request, postback data is loaded and the control properties are restored to the view-state values.

· Page load - At this stage, control properties are set using the view state and control state values.

· Validation - Validate method of the validation control is called and on its successful execution, the IsValid property of the page is set to true.

·  Postback event handling - If the request is a postback (old request), the related event handler is invoked.

·  Page rendering - At this stage, view state for the page and all controls are saved. The page calls the Render method for each control and the output of rendering is written to the OutputStream class of the Response property of page.

· Unload - The rendered page is sent to the client and page properties, such as Response and Request, are unloaded and all cleanup done.

ASP.NET

v  What is asp.net

v  Get vs Post

v  Asp.net web forms vs MVC

v  Asp.net Compilation

v  Asp.net request processing

v  Asp.net life cycle

v  Types of controls in Asp.net Web Forms

v  Explore some basic controls like button,Textbox Drop Down, GridView and Listview

v  Working with Validations

v  Working with CSS and Bootstraps

v  StateManagement  - View State,Hidden Fields, Cookies

v  StateManagement  - Session and Application

v  Caching

v  Creating Custom and User Control using asp.net

v  Working with Master Pages

v  What is Ajax

v  Working with Update Panel

v  What is script Manager

v  Hosting in IIS

v  Working with 3 Tier applications

v  Live Projects

ASP.NET Core Development

 ASP.NET Core is the latest release of Microsoft’s cross-platform version of its ASP.NET Web development framework. This ASP.NET Core Development training introduces attendees to ASP.NET Core development and teaches the skills necessary to design and build well-architected web and service-oriented applications that follow the MVC design pattern. This course does introduce new frameworks like gRPC and Blazor but does not include in-depth coverage of those topics.

Key Learning Areas

v  Understand the goals and benefits of the .NET Core platform

v  Learn to make good decisions about application architecture and the choice of data access technology

v  Use ASP.NET Core's routing system to achieve a REST-style architecture

v  Learn how to build a compelling and maintainable HTML user interface using the Razor view engine and client-side JavaScript

v  Gain experience building a service that make data available via a modern Web API

v  Get an introduction to Blazor, Razor Pages, and gRPC

v  Understand the different cross-platform deployment options available including via Docker containers

ASP.NET CORE

v  Introduction

v  .NET Core SDK

v  ASP.NET Core Application Architecture

v  Application Configuration

v  Request Routing

v  Models

v  Controllers

v  Views

v  HTML Forms

v  Data Validation

v  Application State

v  Error Handling

v  Logging

v  Testing

v  Authentication

v  Web APIs

v  Remote Procedure Calls (gRPC)

v  Blazor

v  Deployment

Objectives

v  Understand the benefits of MVC design over traditional ASP.NET Web Forms.

v  Acquiring sufficient knowledge on role of Model, View and Controller in integrating them to develop complete web application.

v  Understand how Routing API maps requests to action methods in controller.

v  Learn how to reuse code rendering HTML using custom HTML Helper methods and Tag Helpers.

v  Building Custom Model Binders for typical conditions in which built-in default binders are not usable.

v  Understanding and applying validation framework for both client and server validations.

v  Access databases and performing CRUD operations using LINQ and Entity Framework.

v  Implement security in ASP.Net Core applications.

v  Use Ajax and partial page updates and rendering and executing JavaScript code from ASP.NET Core.

v  Modularize using Areas.

v  Compress the output using bundling and minification features.

v  Develop Service Oriented RESTful services using Web API feature of ASP.NET Core.

v  Build and deploy ASP.NET Core application to the production server.

Prerequisites

v  Prior knowledge of HTML and C# is mandatory.

v  Basic knowledge of ASP.NET Web Forms and ASP.NET MVC recommended.

v  LINQ, Entity Framework and SQL Server for database related operations.

v  Some familiarity with HTML, CSS, and JavaScript.    

Blazor

 Blazor has been gaining in popularity lately, especially after the release of .NET Core 3.0, which enriched it with many interesting features. There is great interest around it and Microsoft is betting a lot on its future. But what is Blazor exactly?

 Blazor is a programming framework to build client-side Web applications with .NET. It allows .NET developers to use their C# and Razor knowledge to build interactive UIs running in the browser. Developing client-side applications with Blazor brings a few benefits to .NET developers:

v  They use C# and Razor instead of JavaScript and HTML

v  They can leverage the whole .NET functionalities

v  They can share code across server and client

v  They can use the .NET development tools they are used to

 

  

In a nutshell, Blazor promises .NET developers to let them build client Web applications with the development platform they are comfortable with.

Hosting Models

 Blazor provides you with two ways to run your Web client application: Blazor Server and Blazor WebAssembly. These are called hosting models.

 Blazor Server hosting model runs your application on the server, within an ASP.NET Core application. The UI is sent to the browser, but UI updates and event handling are performed on the server side. This is similar to traditional Web applications, but the communication between the client side and the server side happens over a SignalR connection. The following picture gives you an idea of the overall architecture of the Blazor Server hosting model.

  Blazor Server hosting model provides a few benefits, such as a smaller download size of the client app and the compatibility with not recent browsers. However, it has some drawbacks, like a higher latency due to the roundtrip between the client and the server for most user interactions and the challenging scalability in high traffic scenarios.

  Blazor WebAssembly hosting model lets your application run entirely on the user's browser. The full code of the application, including its dependencies and the .NET runtime, is compiled into WebAssembly, downloaded by the user's browser and locally executed. The following picture describes the hosting model of Blazor WebAssembly.

 The benefits provided by the Blazor WebAssembly hosting model are similar to those provided by Single Page Applications. After the download, the application is independent of the server, apart from the needed interactions. Also, you don't need an ASP.NET Core Web server to host your application. You can use any Web server, since the result of the WebAssembly compilation is just a set of static files.

Blazor (ASP.NET Core 3.1)

v  What are Blazor; Razor Components and Web Assembly?

v  Web Assembly vs Server

v  Configuring Core 3.1

v  Discuss the rapid development and evolution of ASP.NET

v  Comparison of features for web technologies

v  Creating Progress Web Application

v  Support for Dependency Injection

v  Creating your first Blazor Web Application

v  Configuration Options

v  New Core 3.1 Features

Blazor Application

v  Overview of Blazor

v  Blazor and Razor Components

v  Installing Blazor Templates

v  Debugging Blazor Applications

v  Pages

v  Layout and menu

v  Dependency Injection

Razor Components

v  Pages vs Components

v  Routing

v  Rendering Components

v  Binding (one way and two way)

v  Events (and stopping propagation)

v  Code and Code behind files

v  Razor Syntax

v  Razor Directives

Calling REST Services

v  Creating Web API services

v  Web API Controller

v  Implementing Controller Actions

v  Using HttpClient

v  Configuring and Injecting HttpClient

v  Using Get request for Web API service

v  Using Post, Put and Delete

Alternatively Calling gRPC Services

v  What is gRPC?

v  Create a gRPC service (using Proto 3)

v  Define Messages and Remote Procedure Calls

v  Connecting to service

v  Create a client interface for service

Components - continued

v  Parameters

v  Child Components

v  RenderFragments

v  Template Componnts#

Using Entity Framework

v  Introduction to Entity Framework Core

v  Migrations and Database creation

v  DataAnnocations

v  Adding Migrations

v  Creating a Database

v  Creating Web API controller

Validation

v  Introduction to Validation

v  EditForm components

v  Input components

v  Validation components

MVC Security

v  Dealing with common security threats in Web Applications

v  Authentication and Authorization

v  Configuring Authorization

v  Securing Pages and Components

Razor Class Library

v  Creating a Razor Class Library

v  Using Components from a Library

v  Routing to Pages in a Library

Interop with JavaScript

v  Calling JavaScript from Components

v  Referring to Elements within the JavaScript

v  Calling .NET methods from JavaScript

Bootstrap

v  Using Bootstrap to provide a Responsive User Interface

   v  Layout using Bootstrap                

IT Industrial Training .NET Framework

C#, ASP.NET with Window Form Application, Silverlight, WPF, ASP.NET MVC, ASP.NET CORE,Web Service, Web API, Jquery, Bootstraps, Ajax, Javascript , SAP Crystal Report, MS SQL Server, Oracle and Live Projects.