Consider moving DotnetToolResource into Aspire.Hosting.Dotnet for 17

Open
#21,847 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Active
Tech stack
csharp
Domain
backend

Research direction

Start by locating DotnetToolResource and checking the public API layout of Aspire.Hosting and Aspire.Hosting.Dotnet. Then assess compatibility and migration impact, and whether the move fits the version 17 breaking-change window; the issue leaves these questions unresolved, so done requires an agreed direction before implementation.

Written by the indexing model from the issue text.

Description

area-integrations

Summary

Consider moving DotnetToolResource from the Aspire.Hosting assembly into Aspire.Hosting.Dotnet for version 17.

Rationale

The resource represents .NET-specific tooling, so Aspire.Hosting.Dotnet may be a more appropriate assembly boundary than the general hosting assembly.

Open questions

  • Should this move be included in the version 17 breaking-change window?
  • What compatibility or migration impact would moving the public type introduce?

The proposal has not been validated against the current API layout, and affected version details beyond version 17 are unknown.

Dominant language
C#
Stars
6.4k
Forks
1k
Avg merge
3d 3h
Merged PRs (30d)
406

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/aspire

All issues in microsoft/aspire

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.