Visual studio 2022 diagnostic tools not working for aspire projects

[mip1983]

Hi there, recently I'm not seeing the profiling diagnostic tools working when debugging my Aspire app (still working for non-aspire apps).

This is on Version 17.10.0 Preview 6.0 with Aspire preview 6.

It says: "the diagnostic tools window does not support the current debug configuration". Is this just me, or more widespread?

[karpinsn]

Nope, this is not just you. We intentionally disabled the tools for Aspire projects for now since the tools only support single process debugging. We are investigating how to enable multiprocess debugging in the tools which would make them applicable to Aspire projects. This is being tracked with the following Visual Studio Suggestion Ticket. I realize the ticket is a bit old but we are actively investigating this now to hopefully support .NET Aspire.

[mip1983]

Thanks @karpinsn. Is it possible in the interim to still have single process debugging enabled and be able to choose a single process?

[karpinsn]

Is it possible in the interim to still have single process debugging enabled and be able to choose a single process?

Not yet, though we are working towards that. There are two things to work through here, the first is collecting the data from the different processes, the second is figuring out the multi-process user experience. We are starting with collecting from multi-processes and using a process selector, then we are going to figure out how to properly show multiple processes in the user experience.

Right now if we enable the tools for the scenario we show data from whatever is the first process we get the process start event from which is random. This felt weird and broken so we opted to disable it until we can provide a more reasonable experience.

[Suundumused]

may 2025 and still not working...

[sagarok]

August 2025.. The same problem. :(