Safia Abdalla

@josundt Thanks for filling this issue! Things actually work the other way around with respect to API versioning + OpenAPI in ASP.NET Core. The `Asp.Versioning.Mvc.ApiExplorer` package that you referenced above...

Removing the `No Recent Acitivity` label to give @josundt a chance to comment on the question below before the bot auto-closes. > Have you tried using Microsoft.AspNetCore.OpenApi in a project...

@josundt Apologies for the delay here! My focus has been on dev-related work over the past few weeks as we barrel closer to RC1. 😄 > Schema duplication I think...

> It seems this task was auto closed by bots and not actually resolved. Is the workaround used in the e-shop the only way to do this? For the moment,...

@bitlab-ruizhi @efie45 Catching up on some issue triage here. Can you verify if you are able to repro this in 8.0.400? Here's the behavior I see for the provided repro:...

@michaeltg17 Thanks for filing this issue! Unfortunately not, there isn't a super great way to do this with minimal APIs at the moment. We've been tracking this in the backlog...

> The fact it returns empty 400 bad request response is the icing on the cake :)) Debugger can't reach into the area where the response is set so you...

I'm seeing the same thing on Apple Silicon (M2) as well. Issue seems to have shown up after the Sequoia upgrade as well. Similar to you, I can debug test...

I was able to repro this on both the pre-release and release builds of the extensions. C# extension version: v2.48.31 (pre-release), v2.45.25 C# Dev Kit version: v1.11.9 (pre-release), v1.10.18 The...

I'm able to debug my Aspire apps after upgrading. Would be good to get confirmation from other folks as well.