vscode-azurefunctions
vscode-azurefunctions copied to clipboard
Debugging multiple Azure Functions under same solution
Hi, on a project my team and I are working on, we are currently facing some issues concerning the possibility to debug multiple Azure Functions at the same time under vscode.
Currently, the project structure is like the following:
/ProjectName.sln
|_ /AzureFunction1
| |_ AzureFunction1.csproj
|_ /AzureFunction1
| |_ AzureFunction2.csproj
|_ /AzureFunction3
| |_ AzureFunction3.csproj
|_ /CommonProject
|_ CommonProject.csproj
All the Azure Functions are under the same Solution, but in different Projects. They all share some code through the CommonProject, and this is why they are required to be under the same Solution (much easier to deal with it that way).
I saw there is a workaround on the wiki that uses the « multi-root workspace » approach, but this seems quite not scalable and requires to basically recreate the same concept as the Solution.
Would it be possible to support debugging multiple Azure Functions in different projects but under the same solution ?
Kr, V.P.
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
This feature request is now a candidate for our backlog. The community has 240 days to upvote the issue. If it receives 5 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!
Thanks for the answer.
Hopefully, this will become a new feature later on.
Kr, V.P.
This issue has become stale and is at risk of being closed. The community has 60 days to upvote the issue. If it receives 5 upvotes we will keep it open and take another look. If not, we will close it. To learn more about how we handle issues, please see our documentation.
Happy Coding!
:slightly_frowning_face: In the last 60 days, this issue has received less than 5 community upvotes and we closed it. Still a big Thank You to you for taking the time to create it! To learn more about how we handle issues, please see our documentation.
Happy Coding!