Figure out solution for `AOT` trimming of our reflection-registered tools
Open
azsdk-cli
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 143
Description
Right now, if we compile with AOT trimming we will lose our tool definitions. Need to ensure this doesn't happen.
Contributor guide
Research direction
Start by locating the reflection-registered tool definitions and the AOT trimming configuration or entry point. Determine how trimming removes those definitions, then validate the chosen solution with an AOT-trimmed build. Done means the tool definitions remain available when the tools repository is compiled with AOT trimming.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100