dotnet/aspnetcore

If one hosting startup class fails to execute, subsequent hosting startup classes defined in the assembly won't be executed.

Open

#5,902 创建于 2017年8月1日

在 GitHub 查看
 (3 评论) (0 反应) (0 负责人)C# (37,933 star) (10,653 fork)batch import
affected-very-fewarea-hostingarea-networkingbughelp wantedseverity-minor

描述

This should probably have a low priority, because I don't know of any real assemblies that define multiple hosting startup classes.

However, the order of attributes returned by Assembly.GetCustomAttributes<HostingStartupAttribute>() can affect whether or not a hosting startup class gets executed or not. It should also be trivial to fix.

贡献者指南

技术栈
csharp
领域
backend
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
2
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
under 1 hour
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
C#.NET reflectionASP.NET Core hosting startup
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
75
研究方向
Investigate the order of attributes returned by Assembly.GetCustomAttributes<HostingStartupAttribute>() in the hosting startup execution code. Identify where the enumeration stops on failure and modify to continue to subsequent attributes. Refer to the HostingStartupAttribute and related classes in the repository. Check if there are any existing tests for hosting startup execution.