Core插件系统中插件程序集通过自定义AssemblyLoadContextALC加载与宿主程序的 Default ALC 保持隔离。当插件内部若需要自托管一个 Web 服务调用Host.CreateDefaultBuilder()启动 WebHost 时此时必然会出现一条致命异常异常被捕获但应用仍能正常运行所以看起来只是一条日志污染但它却出现crit级别难免让我们心生疑惑。机制背景HostingStartup 是什么IHostingStartup是 ASP.NET Core 提供的启动扩展点。标记[assembly: HostingStartup]特性的程序集会在构建IWebHostBuilder时被自动加载并执行允许外部组件在启动阶段注入服务和中间件无需修改应用代码、也不需要应用显式依赖这些组件。这是 Azure 等 PaaS 平台实现零侵入集成的核心机制。典型场景可观测性— Application Insights 通过 HostingStartup 自动注入请求追踪、依赖遥测、性能计数器应用完全无感知平台集成— Azure AppService的AzureAppServices.HostingStartup注入诊断日志、应用预热Application Initialization、ARR 亲和性 Cookie 等平台级中间件配置增强— 在 Configure()中读取远程配置中心数据追加到 IWebHostBuilder实现启动阶段的动态配置注入程序集发现配置指定— 环境变量ASPNETCORE_HOSTINGSTARTUPASSEMBLIES或配置键hostingStartupAssemblies自动扫描— 遍历 deps.json 中列出的程序集检查是否标记了 [assembly: HostingStartup]加载方式GenericWebHostBuilder.ExecuteHostingStartups()内部调用var assembly Assembly.Load(new AssemblyName(assemblyName));Assembly.Load(AssemblyName)仅在Default ALC中查找对自定义 ALC 完全无感知。冲突链路源码分析GenericWebHostBuilder.ExecuteHostingStartups()的实际实现private void ExecuteHostingStartups() { var webHostOptions new WebHostOptions( _config, Assembly.GetEntryAssembly()?.GetName().Name); if (webHostOptions.PreventHostingStartup) return; var exceptions new ListException(); var assemblyNames webHostOptions.HostingStartupAssemblies .Except(webHostOptions.HostingStartupExcludeAssemblies, StringComparer.OrdinalIgnoreCase) .Distinct(StringComparer.OrdinalIgnoreCase); // 1) 先 Except(excludeAssemblies)再 Distinct 去重 // 2) 逐个程序集独立 try/catch异常不中断循环 foreach (var assemblyName in assemblyNames) { try { var assembly Assembly.Load(new AssemblyName(assemblyName)); foreach (var attr in assembly.GetCustomAttributesHostingStartupAttribute()) { var hostingStartup (IHostingStartup)Activator .CreateInstance(attr.HostingStartupType); hostingStartup.Configure(_hostingStartupWebHostBuilder); } } catch (Exception ex) { exceptions.Add(ex); // 收集异常继续处理后续程序集 } } if (exceptions.Count 0) _hostingStartupErrors exceptions; }每个程序集包裹在独立的 try/catch中异常只影响当前程序集循环继续执行后续程序集不存在 StartupFilter 链断裂问题Except(excludeAssemblies)在Assembly.Load()之前执行被排除的程序集根本不会进入加载循环这是解决方案生效的根基。所有异常最终存入 _hostingStartupErrors由 GenericWebHostServiceOptions.HostingStartupExceptions对外暴露日志组件据此输出crit级别日志。异常复现第一步创建控制台宿主程序新建 .NET 控制台项目ConsoleApp。宿主需要两件事启动WebHost然后通过自定义 ALC 加载插件并调用其初始化方法。using System.Reflection; using System.Runtime.Loader; using Microsoft.AspNetCore.Builder; using Microsoft.AspNetCore.Http; using Microsoft.Extensions.Hosting; // 1. 在 Default ALC 中启动第一个 WebHost Console.WriteLine([ConsoleApp] Starting first web host...); var mainHost Host.CreateDefaultBuilder(args) .ConfigureWebHostDefaults(webBuilder { webBuilder.UseUrls(http://localhost:5001); webBuilder.Configure(app app.Run(async ctx await ctx.Response.WriteAsync(Hello from main host!))); }) .Build(); await mainHost.StartAsync(); Console.WriteLine([ConsoleApp] First host listening on http://localhost:5001); // 2. 通过自定义 ALC 加载插件程序集 var pluginPath Path.Combine( AppContext.BaseDirectory, Plugins, TestLib.dll); var alc new CustomAssemblyLoadContext(pluginPath); var asm alc.LoadFromAssemblyPath(pluginPath); // 验证隔离TestLib 不在 Default ALC 中 Console.WriteLine($[ConsoleApp] TestLib in Default ALC: ${AssemblyLoadContext.Default.Assemblies.Any(a a.GetName().Name TestLib)}); // 输出: False // 3. 调用插件初始化方法 asm.GetType(TestLib.Initializer)! .GetMethod(Initialize)! .Invoke(null, null); Console.WriteLine(Press ENTER to shut down...); Console.ReadLine(); await mainHost.StopAsync(); // 自定义 ALC仅加载 Plugins 目录下的程序集其余交给 Default ALC internal sealed class CustomAssemblyLoadContext : AssemblyLoadContext { private readonly AssemblyDependencyResolver _resolver; public CustomAssemblyLoadContext(string pluginDir) : base(isCollectible: true) { _resolver new AssemblyDependencyResolver(pluginDir); } protected override Assembly? Load(AssemblyName assemblyName) { var path _resolver.ResolveAssemblyToPath(assemblyName); return path is not null ? LoadFromAssemblyPath(path) : null; } }确保 ConsoleApp.csproj中TestLib不作为项目引用。TestLib.dll 通过构建后事件拷贝到 Plugins/ 子目录使其脱离 Default ALC 的探查路径Target NameCopyTestLibToPlugins AfterTargetsBuild MakeDir Directories$(OutputPath)Plugins / Copy SourceFiles..\TestLib\bin\$(Configuration)\net10.0\TestLib.dll DestinationFolder$(OutputPath)Plugins / /Target第二步创建测试插件类库新建 .NET 类库项目TestLib引用Microsoft.AspNetCore.App框架。using Microsoft.AspNetCore.Hosting; using Microsoft.AspNetCore.Builder; using Microsoft.AspNetCore.Http; using Microsoft.Extensions.Hosting; // 标记为 HostingStartup 程序集 [assembly: HostingStartup(typeof(TestLib.TestHostingStartup))] namespace TestLib; public class TestHostingStartup : IHostingStartup { public void Configure(IWebHostBuilder builder) { // 观测点 1记录 Configure 被调用证明 TestLib 被成功加载为 HostingStartup Console.WriteLine([TestLib.HostingStartup] Configure() invoked.); // 观测点 2检查当前程序集归属的 ALC var currentAlc AssemblyLoadContext.GetLoadContext( typeof(TestHostingStartup).Assembly); Console.WriteLine($[TestLib.HostingStartup] Loaded in ALC: {currentAlc?.Name ?? Default}); Console.WriteLine($[TestLib.HostingStartup] Is Default ALC: {currentAlc AssemblyLoadContext.Default}); // 观测点 3注册一个诊断中间件验证 HostingStartup 注入是否生效 builder.Configure(app { app.Use(async (ctx, next) { ctx.Response.Headers[X-HostingStartup] TestLib-Injected; await next(); }); }); Console.WriteLine([TestLib.HostingStartup] Diagnostic middleware registered.); } }TestHostingStartup本身也是一个观测手段——如果Configure()被调用说明 ASP.NET Core 在 Default ALC 中成功定位并加载了 TestLib反之如果只有FileNotFoundException日志而Configure()从未触发则证实了加载失败。public static class Initializer { public static void Initialize() { Console.WriteLine([TestLib] Called from custom ALC context.); // 模拟被注入到环境变量的场景 Environment.SetEnvironmentVariable( ASPNETCORE_HOSTINGSTARTUPASSEMBLIES, TestLib); var host Host.CreateDefaultBuilder() .ConfigureWebHostDefaults(webBuilder { webBuilder.UseUrls(http://localhost:5002); webBuilder.Configure(app app.Run(async ctx await ctx.Response.WriteAsync(Hello from inner host!))); }) .Build(); host.Start(); Console.WriteLine([TestLib] Inner host started on http://localhost:5002); } }第三步启动控制台程序TestLib in Default ALC: False —— 插件确实只存在于自定义 ALC异常来自GenericWebHostBuilder.ExecuteHostingStartups()→Assembly.Load()—— Default ALC 中找不到 TestLib解决方案在插件的ConfigureWebHostDefaults中排除自身程序集Host.CreateDefaultBuilder() .ConfigureWebHostDefaults(webBuilder { // 在 Assembly.Load 发生之前就排除 TestLib webBuilder.UseSetting( WebHostDefaults.HostingStartupExcludeAssembliesKey, TestLib); webBuilder.UseUrls(http://localhost:5002); webBuilder.Configure(app app.Run(async ctx await ctx.Response.WriteAsync(Hello from inner host!))); }) .Build();WebHostOptions在构建待加载列表时先执行assemblies.Except(excludeAssemblies)再交给ExecuteHostingStartups。排除发生在Assembly.Load()之前加载尝试根本不会触发。令人疑惑的API直觉上我们可能想直接清空HostingStartupAssemblieswebBuilder.UseSetting( WebHostDefaults.HostingStartupAssembliesKey, ); // 无效但在WebHostBuilder内部配置会按以下优先级合并AddInMemoryCollection(_settings) ← UseSetting 写入低优先级 .AddConfiguration(hostConfig) ← 环境变量在此高优先级_settings中的空值被hostConfig中的环境变量覆盖因此UseSetting无法清空由环境变量注入的值。而HostingStartupExcludeAssemblies没有对应的环境变量UseSetting写入的值不会被覆盖。
.NET Core自定义 ALC 中启动WebHost的HostingStartup解析异常
Core插件系统中插件程序集通过自定义AssemblyLoadContextALC加载与宿主程序的 Default ALC 保持隔离。当插件内部若需要自托管一个 Web 服务调用Host.CreateDefaultBuilder()启动 WebHost 时此时必然会出现一条致命异常异常被捕获但应用仍能正常运行所以看起来只是一条日志污染但它却出现crit级别难免让我们心生疑惑。机制背景HostingStartup 是什么IHostingStartup是 ASP.NET Core 提供的启动扩展点。标记[assembly: HostingStartup]特性的程序集会在构建IWebHostBuilder时被自动加载并执行允许外部组件在启动阶段注入服务和中间件无需修改应用代码、也不需要应用显式依赖这些组件。这是 Azure 等 PaaS 平台实现零侵入集成的核心机制。典型场景可观测性— Application Insights 通过 HostingStartup 自动注入请求追踪、依赖遥测、性能计数器应用完全无感知平台集成— Azure AppService的AzureAppServices.HostingStartup注入诊断日志、应用预热Application Initialization、ARR 亲和性 Cookie 等平台级中间件配置增强— 在 Configure()中读取远程配置中心数据追加到 IWebHostBuilder实现启动阶段的动态配置注入程序集发现配置指定— 环境变量ASPNETCORE_HOSTINGSTARTUPASSEMBLIES或配置键hostingStartupAssemblies自动扫描— 遍历 deps.json 中列出的程序集检查是否标记了 [assembly: HostingStartup]加载方式GenericWebHostBuilder.ExecuteHostingStartups()内部调用var assembly Assembly.Load(new AssemblyName(assemblyName));Assembly.Load(AssemblyName)仅在Default ALC中查找对自定义 ALC 完全无感知。冲突链路源码分析GenericWebHostBuilder.ExecuteHostingStartups()的实际实现private void ExecuteHostingStartups() { var webHostOptions new WebHostOptions( _config, Assembly.GetEntryAssembly()?.GetName().Name); if (webHostOptions.PreventHostingStartup) return; var exceptions new ListException(); var assemblyNames webHostOptions.HostingStartupAssemblies .Except(webHostOptions.HostingStartupExcludeAssemblies, StringComparer.OrdinalIgnoreCase) .Distinct(StringComparer.OrdinalIgnoreCase); // 1) 先 Except(excludeAssemblies)再 Distinct 去重 // 2) 逐个程序集独立 try/catch异常不中断循环 foreach (var assemblyName in assemblyNames) { try { var assembly Assembly.Load(new AssemblyName(assemblyName)); foreach (var attr in assembly.GetCustomAttributesHostingStartupAttribute()) { var hostingStartup (IHostingStartup)Activator .CreateInstance(attr.HostingStartupType); hostingStartup.Configure(_hostingStartupWebHostBuilder); } } catch (Exception ex) { exceptions.Add(ex); // 收集异常继续处理后续程序集 } } if (exceptions.Count 0) _hostingStartupErrors exceptions; }每个程序集包裹在独立的 try/catch中异常只影响当前程序集循环继续执行后续程序集不存在 StartupFilter 链断裂问题Except(excludeAssemblies)在Assembly.Load()之前执行被排除的程序集根本不会进入加载循环这是解决方案生效的根基。所有异常最终存入 _hostingStartupErrors由 GenericWebHostServiceOptions.HostingStartupExceptions对外暴露日志组件据此输出crit级别日志。异常复现第一步创建控制台宿主程序新建 .NET 控制台项目ConsoleApp。宿主需要两件事启动WebHost然后通过自定义 ALC 加载插件并调用其初始化方法。using System.Reflection; using System.Runtime.Loader; using Microsoft.AspNetCore.Builder; using Microsoft.AspNetCore.Http; using Microsoft.Extensions.Hosting; // 1. 在 Default ALC 中启动第一个 WebHost Console.WriteLine([ConsoleApp] Starting first web host...); var mainHost Host.CreateDefaultBuilder(args) .ConfigureWebHostDefaults(webBuilder { webBuilder.UseUrls(http://localhost:5001); webBuilder.Configure(app app.Run(async ctx await ctx.Response.WriteAsync(Hello from main host!))); }) .Build(); await mainHost.StartAsync(); Console.WriteLine([ConsoleApp] First host listening on http://localhost:5001); // 2. 通过自定义 ALC 加载插件程序集 var pluginPath Path.Combine( AppContext.BaseDirectory, Plugins, TestLib.dll); var alc new CustomAssemblyLoadContext(pluginPath); var asm alc.LoadFromAssemblyPath(pluginPath); // 验证隔离TestLib 不在 Default ALC 中 Console.WriteLine($[ConsoleApp] TestLib in Default ALC: ${AssemblyLoadContext.Default.Assemblies.Any(a a.GetName().Name TestLib)}); // 输出: False // 3. 调用插件初始化方法 asm.GetType(TestLib.Initializer)! .GetMethod(Initialize)! .Invoke(null, null); Console.WriteLine(Press ENTER to shut down...); Console.ReadLine(); await mainHost.StopAsync(); // 自定义 ALC仅加载 Plugins 目录下的程序集其余交给 Default ALC internal sealed class CustomAssemblyLoadContext : AssemblyLoadContext { private readonly AssemblyDependencyResolver _resolver; public CustomAssemblyLoadContext(string pluginDir) : base(isCollectible: true) { _resolver new AssemblyDependencyResolver(pluginDir); } protected override Assembly? Load(AssemblyName assemblyName) { var path _resolver.ResolveAssemblyToPath(assemblyName); return path is not null ? LoadFromAssemblyPath(path) : null; } }确保 ConsoleApp.csproj中TestLib不作为项目引用。TestLib.dll 通过构建后事件拷贝到 Plugins/ 子目录使其脱离 Default ALC 的探查路径Target NameCopyTestLibToPlugins AfterTargetsBuild MakeDir Directories$(OutputPath)Plugins / Copy SourceFiles..\TestLib\bin\$(Configuration)\net10.0\TestLib.dll DestinationFolder$(OutputPath)Plugins / /Target第二步创建测试插件类库新建 .NET 类库项目TestLib引用Microsoft.AspNetCore.App框架。using Microsoft.AspNetCore.Hosting; using Microsoft.AspNetCore.Builder; using Microsoft.AspNetCore.Http; using Microsoft.Extensions.Hosting; // 标记为 HostingStartup 程序集 [assembly: HostingStartup(typeof(TestLib.TestHostingStartup))] namespace TestLib; public class TestHostingStartup : IHostingStartup { public void Configure(IWebHostBuilder builder) { // 观测点 1记录 Configure 被调用证明 TestLib 被成功加载为 HostingStartup Console.WriteLine([TestLib.HostingStartup] Configure() invoked.); // 观测点 2检查当前程序集归属的 ALC var currentAlc AssemblyLoadContext.GetLoadContext( typeof(TestHostingStartup).Assembly); Console.WriteLine($[TestLib.HostingStartup] Loaded in ALC: {currentAlc?.Name ?? Default}); Console.WriteLine($[TestLib.HostingStartup] Is Default ALC: {currentAlc AssemblyLoadContext.Default}); // 观测点 3注册一个诊断中间件验证 HostingStartup 注入是否生效 builder.Configure(app { app.Use(async (ctx, next) { ctx.Response.Headers[X-HostingStartup] TestLib-Injected; await next(); }); }); Console.WriteLine([TestLib.HostingStartup] Diagnostic middleware registered.); } }TestHostingStartup本身也是一个观测手段——如果Configure()被调用说明 ASP.NET Core 在 Default ALC 中成功定位并加载了 TestLib反之如果只有FileNotFoundException日志而Configure()从未触发则证实了加载失败。public static class Initializer { public static void Initialize() { Console.WriteLine([TestLib] Called from custom ALC context.); // 模拟被注入到环境变量的场景 Environment.SetEnvironmentVariable( ASPNETCORE_HOSTINGSTARTUPASSEMBLIES, TestLib); var host Host.CreateDefaultBuilder() .ConfigureWebHostDefaults(webBuilder { webBuilder.UseUrls(http://localhost:5002); webBuilder.Configure(app app.Run(async ctx await ctx.Response.WriteAsync(Hello from inner host!))); }) .Build(); host.Start(); Console.WriteLine([TestLib] Inner host started on http://localhost:5002); } }第三步启动控制台程序TestLib in Default ALC: False —— 插件确实只存在于自定义 ALC异常来自GenericWebHostBuilder.ExecuteHostingStartups()→Assembly.Load()—— Default ALC 中找不到 TestLib解决方案在插件的ConfigureWebHostDefaults中排除自身程序集Host.CreateDefaultBuilder() .ConfigureWebHostDefaults(webBuilder { // 在 Assembly.Load 发生之前就排除 TestLib webBuilder.UseSetting( WebHostDefaults.HostingStartupExcludeAssembliesKey, TestLib); webBuilder.UseUrls(http://localhost:5002); webBuilder.Configure(app app.Run(async ctx await ctx.Response.WriteAsync(Hello from inner host!))); }) .Build();WebHostOptions在构建待加载列表时先执行assemblies.Except(excludeAssemblies)再交给ExecuteHostingStartups。排除发生在Assembly.Load()之前加载尝试根本不会触发。令人疑惑的API直觉上我们可能想直接清空HostingStartupAssemblieswebBuilder.UseSetting( WebHostDefaults.HostingStartupAssembliesKey, ); // 无效但在WebHostBuilder内部配置会按以下优先级合并AddInMemoryCollection(_settings) ← UseSetting 写入低优先级 .AddConfiguration(hostConfig) ← 环境变量在此高优先级_settings中的空值被hostConfig中的环境变量覆盖因此UseSetting无法清空由环境变量注入的值。而HostingStartupExcludeAssemblies没有对应的环境变量UseSetting写入的值不会被覆盖。
