For forms, use the [FromForm] attribute instead of the [FromBody] attribute. The below controller works with ASP.NET Core 1.1: public class MyController : Controller { [HttpPost] public async Task<IActionResult> Submit([FromForm] MyModel model) { //… } } Note: [FromXxx] is required if your controller is annotated with [ApiController]. For normal view controllers it can be omitted.
Program and Startup class .NET Core 2.x You don’t need to new IConfiguration in the Startup constructor. Its implementation will be injected by the DI system. // Program.cs public class Program { public static void Main(string[] args) { BuildWebHost(args).Run(); } public static IWebHost BuildWebHost(string[] args) => WebHost.CreateDefaultBuilder(args) .UseStartup<Startup>() .Build(); } // Startup.cs public class Startup … Read more
You can easily access it in ConfigureServices, just persist it to a property during Startup method which is called first and gets it passed in, then you can access the property from ConfigureServices. public Startup(IWebHostEnvironment env, IApplicationEnvironment appEnv) { …your code here… CurrentEnvironment = env; } private IWebHostEnvironment CurrentEnvironment{ get; set; } public void ConfigureServices(IServiceCollection … Read more
You can install the following two NuGet packages: using Microsoft.Extensions.Configuration; using Microsoft.Extensions.Configuration.Binder; And then you’ll have the possibility to use the following extension method: var myArray = _config.GetSection(“MyArray”).Get<string[]>();
The API has been updated. Not sure when it changed but according to Damien Edwards in late December, you can now do this: var remoteIpAddress = request.HttpContext.Connection.RemoteIpAddress;
To break down the error message: Unable to resolve service for type ‘WebApplication1.Data.BloggerRepository’ while attempting to activate ‘WebApplication1.Controllers.BlogController’. That is saying that your application is trying to create an instance of BlogController but it doesn’t know how to create an instance of BloggerRepository to pass into the constructor. Now look at your startup: services.AddScoped<IBloggerRepository, BloggerRepository>(); … Read more
I did a simple workaround using Func when I found myself in this situation. Firstly declare a shared delegate: public delegate IService ServiceResolver(string key); Then in your Startup.cs, setup the multiple concrete registrations and a manual mapping of those types: services.AddTransient<ServiceA>(); services.AddTransient<ServiceB>(); services.AddTransient<ServiceC>(); services.AddTransient<ServiceResolver>(serviceProvider => key => { switch (key) { case “A”: return serviceProvider.GetService<ServiceA>(); … Read more
The IServiceCollection interface is used for building a dependency injection container. After it’s fully built, it gets composed to an IServiceProvider instance which you can use to resolve services. You can inject an IServiceProvider into any class. The IApplicationBuilder and HttpContext classes can provide the service provider as well, via their ApplicationServices or RequestServices properties … Read more
The approach recommended by the ASP.Net Core team is to use the new policy design which is fully documented here. The basic idea behind the new approach is to use the new [Authorize] attribute to designate a “policy” (e.g. [Authorize( Policy = “YouNeedToBe18ToDoThis”)] where the policy is registered in the application’s Startup.cs to execute some … Read more