using EntityFramework.Exceptions.SqlServer; using IRaCIS.Core.Domain.Share; using IRaCIS.Core.Infra.EFCore; using Medallion.Threading; using Medallion.Threading.SqlServer; using Microsoft.EntityFrameworkCore; using Microsoft.EntityFrameworkCore.Diagnostics; using Microsoft.Extensions.Configuration; using Microsoft.Extensions.DependencyInjection; namespace IRaCIS.Core.SCP { public static class EFSetup { public static void AddEFSetup( this IServiceCollection services, IConfiguration configuration) { services.AddHttpContextAccessor(); services.AddScoped(); services.AddScoped(); //这个注入没有成功--注入是没问题的,构造函数也只是支持参数就好,错在注入的地方不能写DbContext //Web程序中通过重用池中DbContext实例可提高高并发场景下的吞吐量, 这在概念上类似于ADO.NET Provider原生的连接池操作方式,具有节省DbContext实例化成本的优点 services.AddDbContext((sp, options) => { // 在控制台 //public static readonly ILoggerFactory MyLoggerFactory = LoggerFactory.Create(builder => { builder.AddConsole(); }); var logFactory = LoggerFactory.Create(builder => { builder.AddDebug(); }); options.UseSqlServer(configuration.GetSection("ConnectionStrings:RemoteNew").Value, contextOptionsBuilder => contextOptionsBuilder.EnableRetryOnFailure()); options.UseLoggerFactory(logFactory); options.UseExceptionProcessor(); options.EnableSensitiveDataLogging(); options.AddInterceptors(new QueryWithNoLockDbCommandInterceptor()); options.AddInterceptors(sp.GetServices()); options.UseProjectables(); }); //// Register an additional context factory as a Scoped service, which gets a pooled context from the Singleton factory we registered above, //services.AddScoped(); //// Finally, arrange for a context to get injected from our Scoped factory: //services.AddScoped(sp => sp.GetRequiredService().CreateDbContext()); //注意区分 easy caching 也有 IDistributedLockProvider services.AddSingleton(sp => { //var connection = ConnectionMultiplexer.Connect(configuration["Redis:Configuration"]!); return new SqlDistributedSynchronizationProvider(configuration.GetSection("ConnectionStrings:RemoteNew").Value); }); } } }