IActionResult is the equivalent of IHttpActionResult, as you’ve suggested. This is part of the consolidation of what was known as MVC and Web API in ASP.NET Core MVC. As for HttpResponseException, this has been completely removed in ASP.NET Core. There’s an interesting issue around this on GitHub, where David Fowler gives an explanation as to … Read more
When creating an instance of the controller under test, make sure to assign a HttpContext that contains the required dependencies for the test to be exercised to completion. You could try mocking a HttpContext and providing that to the controller or just use DefaultHttpContext provided by the framework //Arrange var mockedAccessor = new Mock<IAccessor>(); //…setup … Read more
You can resolve it as follows: services.AddSwaggerGen (c => { other configs; c.ResolveConflictingActions (apiDescriptions => apiDescriptions.First ()); }); //in the Startup.cs class in the ConfigureServices method or you can put routes to differentiate your methods, for example: [HttpGet(“~/getsomething”)] [HttpGet(“~/getothersomething”)]
Try using [FromForm] instead of [FromBody]. public IActionResult Post([FromForm] PlayerPackage playerPackage) FromBody > Bind from JSON FromForm > Bind from Form parameters You can also remove [FromBody] altogether and trial it then. Because you are expecting form-urlencoded should tell it to bind to object.
Using any context.XyzAsync() method is only useful if you either await the called method or return control to a calling thread that’s doesn’t have context in its scope. A DbContext instance isn’t thread-safe: you should never ever use it in parallel threads. Which means, just for sure, never use it in multiple threads anyway, even … Read more
The sequence of the add statements in the configure function is of importance. Make sure that app.UseAuthentication(); comes before app.UseMvc(); Might this have been the problem?
This happened to me recently. I had the implementation class marked “abstract”, an artifact of an earlier design. I removed it and the container was able to instantiate the class without a problem.
Solution is to have a static reference to the LoggerFactory in a utility static class initialized on startup: /// <summary> /// Shared logger /// </summary> internal static class ApplicationLogging { internal static ILoggerFactory LoggerFactory { get; set; }// = new LoggerFactory(); internal static ILogger CreateLogger<T>() => LoggerFactory.CreateLogger<T>(); internal static ILogger CreateLogger(string categoryName) => LoggerFactory.CreateLogger(categoryName); } … Read more
Add a middleware class to your project to handle the OPTIONS verb. using System.Threading.Tasks; using Microsoft.AspNetCore.Builder; using Microsoft.AspNetCore.Http; using Microsoft.AspNetCore.Hosting; namespace Web.Middlewares { public class OptionsMiddleware { private readonly RequestDelegate _next; public OptionsMiddleware(RequestDelegate next) { _next = next; } public Task Invoke(HttpContext context) { return BeginInvoke(context); } private Task BeginInvoke(HttpContext context) { if (context.Request.Method == … Read more
What you’re trying to do is impossible because the actions are dynamically activated. The request data (such as a query string) cannot be bound until the framework knows the action signature. It can’t know the action signature until it follows the route. Therefore, you can’t make routing dependent on things the framework doesn’t even know … Read more