dotnet/aspnetcore

Improve population of application parts when there's no entry-point assembly

Open

#43,460 opened on Aug 22, 2022

View on GitHub
 (4 comments) (0 reactions) (0 assignees)C# (10,653 forks)batch import
area-mvchelp wanted

Repository metrics

Stars
 (37,933 stars)
PR merge metrics
 (Avg merge 16d 9h) (258 merged PRs in 30d)

Description

Currently the application parts population eventually ends up using Assembly.GetEntryAssembly which may return null in native hosting scenarios (direct hosting through hostfxr, or IJW/COM). When this happens the population will silently do nothing, which is unexpected.

See https://github.com/dotnet/runtime/issues/73516 for more details on one such scenario

Contributor guide

Research direction
Investigate how the application parts population falls back when Assembly.GetEntryAssembly returns null in native hosting scenarios. Look at the linked issue dotnet/runtime#73516 and trace the code path in Microsoft.AspNetCore.Mvc.ApplicationParts to find a robust alternative.
Tech stack
csharp
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#.NET
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40