Remove dependency on dotnet-serve?

[wtgodbe]

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

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[pranavkm]

Our triage decision was to look at replacing this with https://github.com/dotnet/aspnetcore/issues/17528 if that becomes a thing. At this point, that's not scheduled work. Given that this package is stable and all we use it for is a standalone HTTP server during our testing, we think it's 🆗 to use it until a replacement is found.

[JunTaoLuo]

Given that this is used only by blazor, I'll remove the infrastructure tag, fyi @dotnet/aspnet-build.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[mkArtakMSFT]

Moved the dependency to .NET 9. We'll address this after that.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.