Alex Weininger

I have verified that this [workaround](https://github.com/OmniSharp/omnisharp-vscode/issues/4903#issuecomment-993015843) allows me to debug .NET 6.0 Functions on macOS Monterey 12.1.

@PleaseStopAsking were you able to try the workaround mentioned above?

This might have broken when we changed the pick tree item stuff.

Currently the multi-root workspace approach outlined in the wiki is the best approach. We are currently limited to one Function project per workspace. Related to https://github.com/microsoft/vscode-azurefunctions/issues/2521

We could try to use the check resource name API to validate resource names to prevent bugs like this. https://docs.microsoft.com/en-us/rest/api/resources/check-resource-name/check-resource-name

Fellow fish shell user here 😄 , thanks for filing a detailed issue 🚀 > This would be fine if there were some way to customise which shell to run...

Currently it's not possible to customize the default value. However, this is a good idea and we'll see if we can include it in the next feature release.

Fixed in https://github.com/microsoft/vscode/releases/tag/1.70.2

What is the value of your Azure Functions Project Subpath setting? (`azureFunctions.projectSubpath`) If you have a value set, try resetting it (leaving it blank) and see if that fixes the...

To test a hidden stack, enable the “Azure Functions: Show Hidden Stacks” setting in VS Code.  With this setting enabled, “Java 17 (Preview)” appears.