Azure / Azure/azure-functions-host
ExtensionsMetadataGenerator: Support excluding assemblies from extension probing
- Dominant language
- C#
- Stars
- 2k
- Forks
- 482
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 38
Description
Had an internal request to support excluding specific assemblies from our extension probing logic. The scenario was that they were pulling an assembly from another project into a new project, but didn't want the `FunctionsStartup` to run from the dependency.
The workaround is fairly easy -- split out the logic into a separate assembly and reference that -- but it would be nice to have the ability to specify in the project file that an assembly should be explicitly ignored.
Contributor guide
Research direction
Start by locating ExtensionsMetadataGenerator and the extension probing entry point in the host. Determine how project-file settings could identify assemblies to exclude, then verify that an excluded dependency does not run its FunctionsStartup; the issue does not name tests or files for validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100