Consume API in MVC Application

-

 To map the response from API (https://localhost:7264/api/Product) to a .NET MVC Web App, you need to call the API from your controller and deserialize the response into a model, which you can then pass to a view.

1: Create the Product Model
2: Call API from MVC Controller
3: Register HttpClient in Program.cs (or Startup.cs)
4: Create the Razor View (Views/Product/Index.cshtml)
5: Route to Controller



Step 1: Create the Product Model

public class Product

{

    public int Id { get; set; }

    public string Name { get; set; }

    public decimal Price { get; set; }

}


Step 2: Call API from MVC Controller
using Microsoft.AspNetCore.Mvc;
using ProductManagementMVC.Models;
using System.Net.Http.Headers;
using System.Text.Json;

namespace ProductManagementMVC.Controllers
{
    public class ProductController : Controller
    {
        private readonly HttpClient _httpClient;

        public ProductController(IHttpClientFactory httpClientFactory)
        {
            _httpClient = httpClientFactory.CreateClient();
        }

        public async Task<IActionResult> Index()
        {
            var apiUrl = "https://localhost:7264/api/Product";

            var request = new HttpRequestMessage(HttpMethod.Get, apiUrl);
            request.Headers.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json")); // Use JSON for easier deserialization

            var response = await _httpClient.SendAsync(request);

            if (response.IsSuccessStatusCode)
            {
                var responseStream = await response.Content.ReadAsStreamAsync();
                var products = await JsonSerializer.DeserializeAsync<List<Product>>(responseStream, new JsonSerializerOptions
                {
                    PropertyNameCaseInsensitive = true
                });

                return View(products);
            }
            else
            {
                // Handle errors
                return View(new List<Product>());
            }
        }
    }
}



Step 3: Register HttpClient in Program.cs

builder.Services.AddHttpClient();


Step 4: Create the Razor View (Views/Product/Index.cshtml)

@model List<ProductManagementMVC.Models.Product>

<h2>Product List</h2>

<table class="table">
    <thead>
        <tr>
            <th>ProdId</th>
            <th>Name</th>
            <th>Price</th>
        </tr>
    </thead>
    <tbody>
        @foreach (var product in Model)
        {
            <tr>
                <td>@product.ProdId</td>
                <td>@product.ProductName</td>
                <td>@product.Price</td>
            </tr>
        }
    </tbody>
</table>


Step 5: Route to Controller

app.MapControllerRoute(
    name: "default",
    pattern: "{controller=Product}/{action=Index}/{id?}");





Comments

Post a Comment

Popular posts from this blog

API development using .NET Core - ProductManagmentCRUD

-
Image
 1) Create Database and Table as mentioned below queries create table products(ProdId int Primary key, ProductName varchar(20), Price int ) insert into products (ProdId, ProductName, Price ) values (1,'Laptop','45000'); insert into products (ProdId, ProductName, Price ) values (2,'Mouse','500'); insert into products (ProdId, ProductName, Price ) values (3,'Router','1800'); select * from products; 2) Create ASP.NET Core API Project Install NuGet Packages  3)  AppSettings.json {   "Logging": {     "LogLevel": {       "Default": "Information",       "Microsoft.AspNetCore": "Warning"     }   },   "ConnectionStrings": {     "DbConnection": "Server=Server_name; Database=ProductManagementCrud; User Id=sa; password=oj#$kdfn; TrustServerCertificate=True;"   },   "AllowedHosts": "*" } 4) Model -  Product.cs namespace ProductManagmentCRUD.Mo...
Read more

Singleton Design Pattern Realtime Example of banking

-
Image
Logger Utility in a Banking System using Singleton In a banking application, you might have a logger that logs important events like transactions, errors, and user activities. You want to ensure that only one instance of the logger exists throughout the application to maintain a consistent log format and avoid file access conflicts. 1) Why Singleton? A logging class doesn't need multiple instances. One instance is sufficient and more efficient. 2) Consistency: All log messages are centralized through one instance. 4) Resource Management: Avoids file access conflicts and redundant memory usage. using System; public sealed class Logger {     private static Logger instance;     // Private constructor to prevent instantiation from outside     private Logger()    {         Console.WriteLine(" Logger Initialized. ");     }     // Public method to get the single instance     public static Logger ...
Read more