Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debugging multiple Azure Functions under same solution #3222

Closed
vpetit-reimagine opened this issue Jun 14, 2022 · 5 comments
Closed

Debugging multiple Azure Functions under same solution #3222

vpetit-reimagine opened this issue Jun 14, 2022 · 5 comments
Labels
feature monorepo out of scope See https://aka.ms/azcodeissuetriaging

Comments

@vpetit-reimagine
Copy link

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.

@alexweininger
Copy link
Member

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 #2521

@AzCode-Bot
Copy link
Collaborator

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!

@vpetit-reimagine
Copy link
Author

Thanks for the answer.

Hopefully, this will become a new feature later on.

Kr,
V.P.

@AzCode-Bot
Copy link
Collaborator

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!

@AzCode-Bot
Copy link
Collaborator

🙁 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!

@AzCode-Bot AzCode-Bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 20, 2023
@AzCode-Bot AzCode-Bot added the out of scope See https://aka.ms/azcodeissuetriaging label Feb 20, 2023
@microsoft microsoft locked and limited conversation to collaborators Apr 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature monorepo out of scope See https://aka.ms/azcodeissuetriaging
Projects
None yet
Development

No branches or pull requests

3 participants