PROGRAM OVERVIEW

Course Description

Microsoft .NET Core is a completely new thing in the Microsoft web stack when it was introduced. So before going to .NET Core some introduction of the history of .NET web stack is necessary.

ASP.NET Web forms

ASP.NET Web forms were released with the first version of .NET in 2002. In early web development, web forms were the heart of ASP.NET. Web forms provide the User Interface UI of the application. In web forms developers have two options to design the UI. The first is to use tool box and design UI by dragging and dropping every control and setting the layout of the web page. The second is to write full HTML scripts in order to add controls like textbox, labels, buttons etc. In design view, web page written in HTML code looks similar to that which is done by drag and drop of controls. The logic of the page is in .cs file where C# or VB code is available. Later web forms are enhanced and their functionality become more and more better by use of bootstrap, javascript and other javascript libraries.

ASP.NET MVC

In 2009, Microsoft introduced a new framework for web development named ASP.NET MVC, which is based on Models, Views and Controllers patterns to keep a separation between business logic and presentation logic and allow complete control over HTML mark-up. For developers, it became easier to write code in ASP.NET MVC as compared to Web forms. It was so easy to write code as Models, handle the business logic in controllers and generate Views from controllers. Everything is controlled in ASP.NET MVC.

But ASP.NET MVC, although solving the problem of slow release cycle and removing HTML markup abstraction, still suffered from the dependency on .NET framework and System.Web which strictly made it coupled with IIS and windows.

ASP.NET Web API

Later a new web programming model was introduced by Microsoft. In this model, instead of processing the data server-side and sending fully rendered pages to the browser this new paradigm was introduced. It is also called Single Page Application (SPA). It used mostly in static web pages which fetches data with ajax from server and renders the UI directly on the client with javascript.

This library was even more modular than libraries. It was developed by Windows Communication Foundation (WCF) team instead of ASP.NET team so it doesn’t rely on System.Web and IIS. This made this library completely independent from ASP.NET and IIS.

What will you Learn?

After learning ADO .NET start ASP .NET. Learn what it is, why it is used, what are the controls, what are ASP tags, what are attributes for a control etc.

1. Learn Grid View control, events in Grid View, its properties.

2. Learn MultiView Control

3. Learn Template and Bound fields

4. Learn about client side and server-side validation

5. Learn about view state, session state variables

6. Cache management in asp .net

7. Exception handling

8. Global.asax file

9. User defined controls which include User controls and custom controls

10. Master pages.

11. Action filters

12. Dependency injection

13. jQuery ajax

14. Targeting to mobile

Prerequisites

Start to learn the front-end technologies like:

1. Html, CSS, JavaScript

And learn some of the most used Javascript frameworks as well. I would suggest you learn:

1. jQuery - to manipulate Html DOM

2. Angular /React- to build SPA applications

After that learn a back-end programming language (systems language):

 C#

Then at the end learn a language used to manipulate data in Database. I would suggest you learn:

SQL

Framework like:

Entity Framework (.Net framework to interact with data)