*Edit* Service Fabric - Can't Debug With .NET 6

Question

Now that I have figured out what is going on (can't debug services using .NET 6 in Service Fabric), does anyone have an idea of how to get this to work? Some setting in VS, or just a limitation of support from Service Fabric?

I have a collection of service fabric services all hosted in a local cluster. As of a few days ago, I lost the ability to step into those when I attach to the various processes. For the life of me I don't see what has changed in any of my settings, projects, etc.

Since it happened I have tried a number of things.

1. Multiple reboots.
2. Launch the debugger directly from a service method (it gets called and debugger window launches, but nothing to debug due to the "application in break mode" issue).
3. Have updated to latest SF packages (and runtime).
4. Torn down and restart my local cluster.

I can debug into unit tests and other code just fine, seems something odd is going on with the SF side of things.

Has anyone else experienced this behavior and can offer some insight?

Edit 5/9/22 Since my post I have also done the following.

1. Reset all settings back to default in VS 2022
2. Updated to VS 17.1.6
3. Update local SF runtime to 9.0.1017 (also updated all SF nuget packages to latest version)
4. Removed certs and reverted to an unsecured local cluster
5. Went back to an OLD version of the code (one I know was debuggable) to see if it was a change I made

Edit 5/11/22 Found the culprit. Seems to be that even though Service Fabric now supports .NET 6, there is something broken with respect to debugging it. If I revert back to a version of my code using .NET 5, I can once again debug on the fabric. If all I do then is update the project to .NET 6, debugging goes away. Curious.