Asp.net core
44 results found
-
How to call a DELETE REST API with body by using HttpClient in ASP.NET Core
I have an issue when trying to call HTTP delete with some information inside of the request body. I'm using HttpClient class and using DeleteAsync method but I can't push anything into the body
-
How can I implement implicit and explicit casting in ASP.NET Core
How can I implement implicit and explicit casting in ASP.NET Core? I need an example to understand.
-
How to handle all exceptions in ASP.NET Core 3.1?
How to handle all global exception in ASP.NET Core 3.1? I don't want to catch the exception in each action from controllers because it's waste of time to do
-
JsonException: A possible object cycle was detected which is not supported
JsonException: A possible object cycle was detected which is not supported. This can either be due to a cycle or if the object depth is larger than the maximum allowed depth of 32.
-
JWT Authentication and refresh token in Asp.Net Core Web API
JWT authentication is standard for Json Web Token, It is a best solution for login with some stateless application type such as Restful Api. The Jwt uses a bearer token to check and allow users access to the application. In this article I will guide how to implement Jwt authentication and refresh tokens in Asp.net Core Web Api.
-
Param of POST method always get null value in Asp.Net Core
The param of POST method always get null value when calling from the client in Asp.Net Core 3.1
-
The type initializer for ‘System.Drawing.GDIPlus’ threw an exception
The type initializer for ‘System.Drawing.GDIPlus’ threw an exception. Unable to load DLL ‘gdiplus’: The specified module or one of its dependencies could not be found.
-
Detected package downgrade: Microsoft.NETCore.Platforms from 3.0.0 to 3.0.0-preview.19073.11
error NU1605: Detected package downgrade: Microsoft.NETCore.Platforms from 3.0.0 to 3.0.0-preview.19073.11. Reference the package directly from the project to select a different version
-
Asp.Net Core 3.0 throw HTTP Error 500.30 - ANCM In-Process Start Failure
Asp.Net Core 3.0 throws HTTP Error 500.30 - ANCM In-Process Start Failure when running the application in the browser.
-
Synchronous operations are disallowed. Call WriteAsync or set AllowSynchronousIO to true instead.
System.InvalidOperationException: Synchronous operations are disallowed. Call WriteAsync or set AllowSynchronousIO to true instead.
-
EndpointRoutingMiddleware matches endpoints setup by EndpointMiddleware when migrate asp .net core 2.2 to 3.1
EndpointRoutingMiddleware matches endpoints setup by EndpointMiddleware and so must be added to the request execution pipeline before EndpointMiddleware
-
JwtBearerDefaults is missing in Asp.Net Core 3.0 and 3.1
JwtBearerDefaults is missing in Asp.Net Core 3.0 and 3.1. It's worked in version 2.2 when migrating to version 3.1 it throws error.
-
Caching data by using in-memory cache in Asp.Net Core 3.1
In this article I will guide you how to cache data in Asp.net Core using in-memory cache. As you know, cache helps access and return data faster than many times if compared with getting data from the database. In Asp.net framework we have IIS cache (Http cache) but in Asp.net core microsoft replace it with In-memory cache technique.
-
The specified framework 'microsoft.aspnetcore.app', version '3.0.0' was not found.
It was not possible to find any compatible framework version. The specified framework 'Microsoft.AspNetCore.App', version '3.0.0' was not found.
-
It was not possible to find any compatible framework version The framework 'Microsoft.AspNetCore.App', version '2.2.0' was not found
It was not possible to find any compatible framework version The framework 'Microsoft.AspNetCore.App', version '2.2.0' was not found