Yes, for SDK-based projects the new launch profile UI is really confusing. They are trying to get it to behave like VS Code and it is a ways off.
To configure a DLL project to be debuggable (instead of having a corresponding unit test or test app project) you need to go to the launch profile UI dialog via the project properties or Debug menu. Once in the UI you should have a default profile for the class library but this doesn't work for DLLs. Add a new profile from the toolbar at the top and select
Executable. Then you can enter executable information like you could before. Behind the scenes it is just updating the
launchsettings.json so you could also just edit that file directly.
At least with the current version of VS 2022 you cannot select the profile to run against when you debug (like you can for VS Code). The only way I have found to work around this is to delete the auto-generated profile that was created. It appears the debugger first tries to use the profile matching the project name. If it doesn't find it uses the first one it finds but I could be wrong about this.
thanks a lot! this is really helpful!