- 235 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.8 Get Ready for your first challenge
This is a very common question from new software developer that from where we should start. So I thought to explain you the various steps involved from requirement gathering to actually start the development.
What are use cases
So after getting the requirement from a client, the first thing in software development is to break the requirement into smaller tasks. These smaller tasks are called Use cases. Basically these smaller tasks are the activities performed by different users into any software.
Use Case Diagram
So before creating the use cases, business analyst creates high level diagram of use case, that is called “Use case diagram”
Let’s look at the use case diagram of the application we are going to build. I have not added all the activity in this use case for our application, as it will make our diagram too much complicated to understand.
I have created diagram for two roles here and in the same way we can create diagram for other roles as well.
This one is very basic use case diagram, If you want to know more about use case diagram, you can watch the video from the following link
So after creating the high level use case diagrams, I writes detailed use cases for each activity
Once I have all the use cases, I create dependency graph for each activity. So let’s pick one of use case for our application, i.e.
Sort Bike – So in order to create this functionality, we should have List of Bike, so we should have List Page first
List Page – In order create list of bikes, we should be able to add bikes
Add Bike – So you have the order in which you will have to add the functionality in your application.
Add Bike -> Bike List -> Sort Bike
Isolate your mind
When working on any activity, you should isolate your mind only for that activity. And always first try to create very basic functionality, for example if you are working on Listing Bike, you should not be worried about sorting, layout of page and other fancy features.
After creating very basic list page, you can further go ahead and can make your list page more attractive by adding style sheet and images.
Add Bike Dependency
After creating the dependency chart we can start implementing the use cases. So let’s implement “Add Bike” use case. To implement any use case, we have to think that how our user will interact with our system for that use case. So to add a Bike we will have a user interface something like below
Make – We will have drop down list here for various makes i.e. Harley Davidson, Ducati etc.
Model – After selecting the make, related model should be populated for that particular make in this dropdown. So will will create cascading dropdown here.
Features – And to select features we will have check boxes to select various features on this screen.
Let’s go back to our Dependency Graph and further analyse that what is needed to add MAKE in our application.
Add Bike – To add the Bike , we should have a user interface, in MVC Framework, user interface is created from View, that is “V” in MVC.
View – In order to save the Make , we should have database tables
Database Tables – As we are using code first approach in our course, So to create a table in database, we will add domain classes first
Domain Classes – So here we will add domain class “MAKE”
We will take baby steps here, we will just create Database and Domain Model for our first challenge.
Week #1 Activities
We will complete following activities in coming week
- Create Basic MVC project
- Add connection string
- Create domain class for Make
- Add Database Migration
- Run Update-database command to create Database and MAKE table in our database.
I will complete these activities in coming week and will publish the video and code by the end of week.
So let’s GET STARTED