- 343 students
- 46 lessons
- 0 quizzes
- 16 week duration
1. Getting Started
- 1.1 Introduction to the course
- 1.2 What we will build
- 1.3 What is ASP.NET Core and Why to use it
- 1.4 Install Visual Studio 2017
- 1.5 Install SQL Server 2017 and SSMS
- 1.6 Create Basic MVC Project in ASP.NET and ASP.NET Core
- 1.7 Compare Folder Structure (ASP.NET and ASP.NET Core)
- 1.8 Get Ready for your first challenge
2. Working with Data
- 2.1 Introduction and understand entity framework
- 2.2 Create Project and add domain classes
- 2.3 Add DbContext
- 2.4 Add Connection String
- 2.5 Configure DbContext as Service and add DbSet to Application DbContext
- 2.6 Add Migration and Update Database
- 2.7 Verify tables in Database using SSMS
- Exercise and Next challenge
- 2.8 Apply Constraints and rollback previous database migration
3. Understanding MVC Fundamentals
4. Implementing CRUD Operations
- 4.1 Make – Bootstrap migration and create list page for makes of vehicle
- 4.2 Make – Create operation to add new Makes
- 4.3 Make – Delete operation to delete makes
- 4.4 Make – Edit operation to Edit makes and add beautiful icons on buttons
- 4.5 Model – Implement CRUD using ViewModel – Part-1
- 4.6 Model – Implement CRUD Part-2 and Refactor existing code
- 4.7 Extension methods and using it to refactor existing method
6. Deployment on Azure
7. Completing Application
- Adding Bike
- Upload Bike Image and implement Delete Bike Functionality
- Server side and client side data validation
- Implement Cascading Drop down List using WebAPI and Ajax
- Decouple domain and service layer
- Using Automapper to map Service and domain layer objects
- Implement Pagination on Bike Index Page
- Filtering and Sorting a Bike
- Edit Bike
- Bike search on home page
7. Some advance concepts
1.3 What is ASP.NET Core and Why to use it
What is ASP.NET Core
While million of developers used ASP.NET to build web application since last many years, but latest ASP.NET Core frameworks offer far more benefits than the classic ASP.NET.
Since many years Microsoft have been provided close source tool. Many of developers and organization who are the lover of open source were very reluctant to use Microsoft technology. So making ASP.NET Core an open source have broadened the scope of ASP.NET in the world.
ASP.NET Core is not the extended version of ASP.NET , instead it is the rebirth of ASP.NET. it’s an open source, cross platform rebuild of ASP.NET developed by Microsoft and its community.
Why ASP.Net Core
1. Open Source and Cross Platform
ASP.NET uses System.Web.dll (with all of it’s Windows based API hooks), while ASP.NET Core uses a new web server called Kestrel, which makes you able to host application on a Linux or MAC Server as easily as you can host on a Windows server.
In addition to this, development environment is also not dependent on windows. Now developers are free to choose their preferred OS and collaborate. In simple term, now developers can work across MacOS, Linux or Windows and they can still work on same project.
In short, ASP.NET Core framework is now capable to develop and run web application on multiple OS i.e. Linux, Mac and Windows.
Unlike ASP.NET, new .NET Core frameworks provide inbuilt support for two most popular JS frameworks – Angular and React.
3. Razor markup more natural with HTML
4. Increased Performance
One of the biggest advantage of ASP.NET is increased performance. When you compile code it automatically optimize it in order to increase the performance.
According to the study done by TechEmpwer, ASP.NET Core’s performance is 800 times faster than the previous performance records.
5. Improved Testability and readability
ASP.NET Core provides inbuilt dependency injection and unlike ASP.NET you do not need to depend on 3rd party frameworks. If you are not aware of what the Dependency Injection is, let me explain you in short what it is.
Dependency Injection (DI) is a software design pattern. It allows us to develop loosely-coupled code. The intent of Dependency Injection is to make code maintainable. it reduces the hard-coded dependencies among your classes by injecting those dependencies at run time instead of design time.
Dependency injections make your code
- Easily testable
- More reusable
- More cleaner
- Easily extendable