Explore ASP.NET Core by delving into MVC design, JSON web APIs, repository patterns, and adding authentication. Gain insights to confidently develop full-stack or backend applications.

asp.tar.gz

ASP.NET

MVC in ASP.NET Core - Models in ASP.NET

MVC in ASP.NET Core - Models in ASP.NET-copy

This course is for you if you’re looking to start your journey in either full-stack MVC or backend development with ASP.NET Core.

In the first half of the course, you’ll learn about the Model-View-Controller design pattern and how you can use it to organize and develop your web application. You’ll then dive into JSON web APIs which allow communication between your back-end ASP.NET application and front-end web/mobile application.

In the latter half, you’ll learn about the repository pattern, how relationships work, and how to add authentication and authorization to your application.

By the end of this course, you will have the confidence to develop your own applications in ASP.NET Core.

Developing Applications with ASP.NET Core

Create a new model class `TeacherContactInfo`. Establish a one-to-one relationship between `Teacher` and `TeacherContactInfo`.

Adding a one-to-one relationship between `ContactInfo` and `Teacher`.

Create a model class `User` with an attribute of `Type`, which specifies if a user is a student or a teacher. A One-to-One relation between `User` and `ContactInfo`.

In the previous lessons, we have configured relations between Student and Teacher and between Student and ContactInfo. This allowed us to:
- Save student information in one table and their contact information in another table.
- Save teacher information in one table and assign multiple students to multiple teachers.

However, we are unable to save the teacher's contact information. What is the best approach from the given options to resolve this issue?

In the previous lessons, we have configured relations between Student and Teacher and between Student and ContactInfo. This allowed us to:
<ul>
<li>Save student information in one table and their contact information in another table.</li>
<li>Save teacher information in one table and assign multiple students to multiple teachers.</li>
</ul>
However, we are unable to save the teacher’s contact information. What is the best approach from the given options to resolve this issue?

Currently, there is not a relationship established between `Teacher` and `Department`. What relationship could exist between the two?

Currently, there is not a relationship established between <code>Teacher</code> and <code>Department</code>. What relationship could exist between the two?

Create a new model class called `HOD` which stores all of HOD's information. Establish a one-to-one relation between `HOD` and `ContactInfo` and between `HOD` and `Department`.

Store HOD's information in the Teachers table. Rename the `Teacher` model class to `Faculty` (which updates the table name as well). Add attribute `isHOD` of datatype `bool` and add any additional attributes to the `Faculty` model class which are required. 

Add more attributes into the `Department` model class to store HOD's information. Make a one-to-one relation between `Department` and `ContactInfo`.

Currently, we are only storing the name of HOD in the `Department` model class. We wish to store more information about the HOD, such as their qualification and contact information. What can be the best way to address this problem?

Currently, we are only storing the name of HOD in the <code>Department</code> model class. We wish to store more information about the HOD, such as their qualification and contact information. What can be the best way to address this problem?

Suppose you are creating a hospital management system. The hospital contains a list of doctors and patients. Which relation between doctor and patient makes the most sense?

Suppose you are creating a hospital management system. The hospital contains a list of doctors and patients. Which relation between doctor and patient makes the most sense?

```C#
public class Student
{
 public int ID { get; set; }
 public StudentInfo StudentInfo { get; set; }
 public Subject Subject { get; set; }
}

public class StudentInfo
{
 public int ID { get; set; }
 public Student Student { get; set; }
}

public class Subject
{
 public int ID { get; set; }
 public List<Student> Students { get; set; }
}
```

```C#
public class Student
{
    public int ID { get; set; }
    public int SubjectID { get; set; }
}

public class StudentInfo
{
    public int ID { get; set; }
    public int StudentID { get; set; }
}

public class Subject
{
    public int ID { get; set; }
}
```

```C#
public class Student
{
 public int ID { get; set; }
 public StudentInfo StudentInfo { get; set; }
 public int SubjectID { get; set; }
 public Subject Subject { get; set; }
}

public class StudentInfo
{
 public int ID { get; set; }
 public int StudentID { get; set; }
 public Student Student { get; set; }
}

public class Subject
{
 public int ID { get; set; }
 public int StudentID { get; set; }
 public List<Student> Students { get; set; }
}
```

```C#
public class Student
{
 public int ID { get; set; }
 public StudentInfo StudentInfo { get; set; }
 public int SubjectID { get; set; }
 public Subject Subject { get; set; }
}

public class StudentInfo
{
 public int ID { get; set; }
 public int StudentID { get; set; }
 public Student Student { get; set; }
}

public class Subject
{
 public int ID { get; set; }
 public List<Student> Students { get; set; }
}
```

```C#
public class Student
{
    public int ID { get; set; }
    public StudentInfo StudentInfo { get; set; }
    public int SubjectID { get; set; }
    public Subject Subject { get; set; }
}

public class StudentInfo
{
    public int ID { get; set; }
    public int StudentID { get; set; }
    public Student Student { get; set; }
}

public class Subject
{
    public int ID { get; set; }
    public Student Student { get; set; }
}
```

Which of the following will create

- A one-to-one relationship between `Student` and `StudentInfo`
- A one-to-many relationship between `Subject` and `Student`?

Which of the following will create
<ul>
<li>A one-to-one relationship between <code>Student</code> and <code>StudentInfo</code></li>
<li>A one-to-many relationship between <code>Subject</code> and <code>Student</code>?</li>
</ul>

Quiz on relationships in <t>ASP.NET</t> Core

Quiz on relationships in <t>ASP.NET</t> Core

A quiz to test your understanding of relationships in ASP.NET Core.

Introduction

Getting Started

MVC in ASP.NET Core

JSON Web APIs in ASP.NET Core

Working with Repositories

Relationships

Authentication and Authorization

Appendix

Conclusion

Quiz: Relationships in ASP.NET Core