Move DebugProxy out of dev server package

[captainsafia]

As part of the work to support #25643, we need to move the DebugProxy package out of the dev server package. VS Code and VS will need to be updated to download use the DebugProxy from an alternate location.

[ghost]

Thanks for contacting us. We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. Because it's not immediately obvious that this is a bug in our framework, we would like to keep this around to collect more feedback, which can later help us determine the impact of it. 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]

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.

[TanayParikh]

@captainsafia is this something we should be planning for 7.0?

[captainsafia]

@TanayParikh I think it only makes sense to do this if we are planning on pursuing https://github.com/dotnet/aspnetcore/issues/25643 for 7.0.

[TanayParikh]

Thanks @captainsafia! @danroth27 what are your thoughts on this given prioritization of https://github.com/dotnet/aspnetcore/issues/25643?

[danroth27]

I'd really like to get https://github.com/dotnet/aspnetcore/issues/25643 done for .NET 7. I believe this is a prerequisite.

[TanayParikh]

Docs & infra candidate?

[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.

[danroth27]

Note that we're tracking making Blazor WebAssembly debugging working in containers with https://github.com/dotnet/aspnetcore/issues/37565.

[paviln]

Why did this get moved to nice to have? Not having this feature, makes dev containers practical unusable... Maybe ask azure team to help with it, as they would benefit providing this service.

[danroth27]

Why did this get moved to nice to have? Not having this feature, makes dev containers practical unusable... Maybe ask azure team to help with it, as they would benefit providing this service.

@paviln We're tracking making Blazor WebAssembly debugging work in dev container with #37565. If it ends up that this issue needs to be addressed for that scenario, we'll react accordingly.

[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.

[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.