AppHost configuration to not attach debugger to a project

[JamesNK]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

It would be useful to be able to configure a .NET project that you don't want the debugger attached when the app host is run with debugger.

I have a niche scenario where I explicitly don't want the debugger because the library has different behavior depending on whether the debugger is attached or not.

A more common ask for this is you don't want to debug into a particular app or be alerted by exceptions thrown in the app. There would also be performance benefits to not attaching the debugger to apps when not wanted.

Describe the solution you'd like

An API in the app host to configure a .NET project not to be launched with the debugger attached.

Additional context

No response

[KLuuKer]

In our case we have teams with different "debugging" needs.

• just Frontend for the majority of developers
• Frontend + Backend for 20%
• only Backend for 9%
• Frontend + Backend + the kitchen sink for the really small handful ones

But everyone MUST run ALL projects or the system won't work

[KLuuKer]

@davidfowl it's really a big blocker for people with large solutions
we literally have 2 AppHost projects that need to be started as a workaround
and i need to use fake dummy projects for health checks to work

and of course i lose all the nice features the dashboard provides me, because i have 2 of them now

still super duper love aspire it really helps to have people not think about setting 7 different projects to startup
and having all those yarn\npm install commands run and the various watch commands that need to be started

p.s. 🎉 .net 10 🎉 aspire 13 🎉

[davidfowl]

I think to make this usable we'd need an "attach" to process from the dashboard.