Tags
Language
Tags
June 2025
Su Mo Tu We Th Fr Sa
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30 1 2 3 4 5
    Attention❗ To save your time, in order to download anything on this site, you must be registered 👉 HERE. If you do not have a registration yet, it is better to do it right away. ✌

    ( • )( • ) ( ͡⚆ ͜ʖ ͡⚆ ) (‿ˠ‿)
    SpicyMags.xyz

    Web API in ASP.NET Core 5 with a real project

    Posted By: lucky_aut
    Web API in ASP.NET Core 5 with a real project

    Web API in ASP.NET Core 5 with a real project
    Duration: 6h 53m | .MP4 1280x720, 30 fps(r) | AAC, 44100 Hz, 2ch | 3.59 GB
    Genre: eLearning | Language: English

    In a real project (Server & Client side) you will be familiar the concepts of API's

    What you'll learn
    Login and Register API
    Delete, Select, Insert, Update (CURD)
    Submit a form with images of files
    Repository Pattern
    Memory and Response Caching
    Authentication with JWT (JSON Web Token)
    Validation
    Client and Server Side
    Authentication
    Swagger (Documentation)
    Paging
    Manage HTTP Headers
    Seed Data

    Requirements
    ASP NET
    C#
    Entity Framework

    Description
    In this tutorial, we will implement API related topics in .NET Core 5. We start the training with a real project that has a server and client-side. The two sections communicate via the API. In this tutorial, we will cover important issues and avoid issues that you know about.

    On the Server-side, we implement the ApiConntrollers, methods such as Post, PUT, Get and Delete. We can also authenticate users using JWT (JSON WEB Token). We also implement how to save photos or files via the API. We will also implement things like Paging, Response, and Memory Caching, Validation, Repositories Login, and Register API. In addition, we can change the header for HTTP and put information that we use in the client section.

    In contrast on the Client-side, we create a project with a news template. And we will receive and send information from the server through the API. To do this, we receive the token from the server at login time, then store it in the client and send it to the APIs along with the requests. Also, on the Client-side, we have a section for managing information, which is Authorized so that unauthorized users cannot manipulate the information. Finally, for all APIs, we use Swagger to create documentation that is important to developers.

    Who this course is for:
    Meddle-level developers

    More Info