Support for stored procedures in EF Core 1.0 is resolved now, this also supports the mapping of multiple result-sets. Check here for the fix details And you can call it like this in c# var userType = dbContext.Set().FromSql(“dbo.SomeSproc @Id = {0}, @Name = {1}”, 45, “Ada”);
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
This answer was originally written for ASP.NET Core RC1. In RC2 ASP.NET Core moved from generic httpPlafrom handler to aspnetCore specific one. Note that step 3 depends on what version of ASP.NET Core you are using. Turns out environment variables for ASP.NET Core projects can be set without having to set environment variables for user … Read more
As a general rule, converting a Web Forms or MVC5 application to ASP.NET Core will require a significant amount of refactoring. HttpContext.Current was removed in ASP.NET Core. Accessing the current HTTP context from a separate class library is the type of messy architecture that ASP.NET Core tries to avoid. There are a few ways to … 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
Quick and Easy Solution. Simply add this middleware before ASP.NET routing into your middleware registrations. app.UseExceptionHandler(c => c.Run(async context => { var exception = context.Features .Get<IExceptionHandlerPathFeature>() .Error; var response = new { error = exception.Message }; await context.Response.WriteAsJsonAsync(response); })); app.UseMvc(); // or .UseRouting() or .UseEndpoints() Enable Dependency Injection for logging and other purposes. Step 1. … Read more
To get a more detailed error message: Verify that the log directory exists at the path referenced by the web config. If it does not, create it. The path shown in your config would place the “logs” directory in the root folder of the deployed site. Verify that the application pool has write access to … Read more
HttpContext.Current doesn’t exist anymore in ASP.NET Core but there’s a new IHttpContextAccessor that you can inject in your dependencies and use to retrieve the current HttpContext: public class MyComponent : IMyComponent { private readonly IHttpContextAccessor _contextAccessor; public MyComponent(IHttpContextAccessor contextAccessor) { _contextAccessor = contextAccessor; } public string GetDataFromSession() { return _contextAccessor.HttpContext.Session.GetString(*KEY*); } }
Because you have a very simple CORS policy (Allow all requests from XXX domain), you don’t need to make it so complicated. Try doing the following first (A very basic implementation of CORS). If you haven’t already, install the CORS nuget package. Install-Package Microsoft.AspNetCore.Cors In the ConfigureServices method of your startup.cs, add the CORS services. … Read more
This has had a few twists and turns. I’ve modified this answer to be up to date with ASP.NET Core 2.0 (as of 26/02/2018). This is mostly taken from the official documentation: To work with settings in your ASP.NET application, it is recommended that you only instantiate a Configuration in your application’s Startup class. Then, … Read more