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.