+
-public string Name {get; set;}
+#### Model
+* Representation of data in code
+* Can also include some logic to retrieve and save the data
+
+
-}
+#### View
+* The data that is shown to the client, e.g. a web page
+* More often than not different from the Model - client does not need to (and often *shouldn't*) see all possible data
+
+
-Get()
+#### Controller
+* Communicates with the Model and the View
+* How the data (models) will be processed before sending it forwards to the client or to the view
+
+
+
-"id": 1
+#### Model
-"name": "Sonja"
+`Models/User.cs`
+```csharp
+namespace MyApi.Models
+{
+ public class User
+ {
+ public int Id {get; set;}
+ public string Name {get; set;}
+ }
}
+```
----
-
-The "view" in APIs is basically just JSON data
-
-# Exercise 1. Setting up the Project
-
-Create a new ASP.NET Core Web API template project. Name it CourseAPI. Delete WeatherForecastController.cs and WeatherForecast.cs.
+
+
-Add a new controller CoursesController by right-clicking the Controllers folder and selecting _Add_ > _Controller… > API Controller > Empty_
+#### View
-Add a new folder Models. Inside, add a new class file ( _Add > Class…_ ) Course.cs
-
-To the Course class, create the properties int Id, string Name and int Credits
-
-# Exercise 2: Creating GET Endpoints
+```csharp
+{
+ "id": 1
+ "name": "Sonja"
+}
+```
+(Basically just JSON data that ASP.NET can show automatically)
-Inside the Controller class, initialize a list of courses with a couple of test courses
+
+
-Create endpoints for GET requests with URIs api/courses and api/courses/{id} which return all courses and a single course with a corresponding ID, respectively
+#### Controller
-# Repositories
+`Controllers/UserController.cs`
+```csharp
+using Microsoft.AspNetCore.Mvc;
+using MyApi.Models;
+namespace MyApi.Controllers
+{
+ [ApiController]
+ [Route("api/[controller]")]
+ public class UserController : ControllerBase
+ {
+ [HttpGet("{id}")]
+ public IActionResult GetUser(int id)
+ // ...
+ }
+}
+```
-* When following the _separation of concerns_ principle, the controllers or models should NOT be accessing the database directly
-* Instead, the web app should have some kind of repository for reading from and writing to the database
-* For now, we can just create a mock repository to a new folder called "Repositories" for our needs, and make it static so that it can be accessed everywhere
- * Later on, we will add services to make the repository available within our program via dependency injection
+
+
+
+```csharp
+using Microsoft.AspNetCore.Mvc;
+using MyApi.Models;
+namespace MyApi.Controllers
{
+ [ApiController]
+ [Route("api/[controller]")]
+ public class UserController : ControllerBase
+ {
+ [HttpGet("{id}")]
+ public IActionResult GetUser(int id)
+ {
+ var person = new Person
+ {
+ Id = 1,
+ Name = "Sonja"
+ };
+ return Ok(person);
+ }
+ }
+}
+```
-// Replace this later on with a database context
+
+
-private List Students { get; set; }
+* Here's an extended implementation of the earlier controller, showcasing the HTTP `GET` method
+* The object that gets sent to the View (the webpage) as a JSON is just hardcoded here, but normally the data comes from a ***database***
-// Constructor to initialize student list
+
+