dotnet / dotnet/aspnetcore

Remove dependency on dotnet-serve?

Open
#28,388 7 comments 0 reactions 0 assignees View on GitHub
affected-very-few area-blazor blocked not-on-roadmap Pillar: Technical Debt Priority:2 severity-nice-to-have task
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 10h
Merged PRs (30d)
281

Description

https://github.com/dotnet/aspnetcore/blob/fdbeaaccd265227d6c1a26b7e9802cdea8bde02e/.config/dotnet-tools.json#L5-L8

This tool is maintained by an individual (Nate), we should consider removing our dependency on it. Looks like we currently use the tool for a Blazor test: https://github.com/dotnet/aspnetcore/commit/1c3ae1549e3f3137ccfafc0de4753dc358b4e441

CC @dotnet/aspnet-build @pranavkm @javiercn @captainsafia

Contributor guide

Open the contributing guide

Research direction

Start with .config/dotnet-tools.json lines 5-8 and the Blazor test introduced by commit 1c3ae1549e3f3137ccfafc0de4753dc358b4e441. Trace how the test uses dotnet-serve and determine whether it can be removed or replaced. Done means the dependency is gone and the affected Blazor test still works.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
testing, tooling
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.