Skip to content

Commit 0880232

Browse files
authored
Merge pull request #110513 from zr-msft/ds-faq-multi-workspace
[Dev Spaces] add FAQ callout for multiple applications in a solution
2 parents ff8d11b + 4ea35da commit 0880232

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

articles/dev-spaces/faq.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -76,6 +76,14 @@ When using Visual Studio to prepare your project, you have the option of enablin
7676

7777
Currently, Azure Dev Spaces does not support using [pod managed identities][aks-pod-managed-id] on AKS clusters with Azure Dev Spaces enabled. If you have pod managed identities installed and would like to uninstall it, you can find more details in the [uninstall notes][aks-pod-managed-id-uninstall].
7878

79+
## Can I use Azure Dev Spaces with multiple microservices in an application?
80+
81+
Yes, you can use Azure Dev Spaces in an application with multiple microservices, but you must prepare and run the individual microservices at their root. The Azure Dev Spaces CLI, Azure Dev Spaces VS Code extension, and Visual Studio Azure Development workload expect the *azds.yaml* file to be at the root of the microservice in order to run and debug. See the [Bike Sharing sample application][bike-sharing] for an example of multiple microservices in a single application.
82+
83+
In Visual Studio Code, it is possible to [open separate projects in a single workspace][vs-code-multi-root-workspaces] and debug them separately through Azure Dev Spaces. Each of the projects must be self-contained and prepared for Azure Dev Spaces.
84+
85+
In Visual Studio, it is possible to configure .NET Core solutions for debugging through Azure Dev Spaces.
86+
7987
[aks-auth-range]: ../aks/api-server-authorized-ip-ranges.md
8088
[aks-auth-range-create]: ../aks/api-server-authorized-ip-ranges.md#create-an-aks-cluster-with-api-server-authorized-ip-ranges-enabled
8189
[aks-auth-range-ranges]: https://github.com/Azure/dev-spaces/tree/master/public-ips
@@ -84,6 +92,7 @@ Currently, Azure Dev Spaces does not support using [pod managed identities][aks-
8492
[aks-pod-managed-id]: ../aks/developer-best-practices-pod-security.md#use-pod-managed-identities
8593
[aks-pod-managed-id-uninstall]: https://github.com/Azure/aad-pod-identity#uninstall-notes
8694
[aks-restrict-egress-traffic]: ../aks/limit-egress-traffic.md
95+
[bike-sharing]: https://github.com/Azure/dev-spaces/tree/master/samples/BikeSharingApp
8796
[dev-spaces-prep]: how-dev-spaces-works-prep.md
8897
[dev-spaces-routing]: how-dev-spaces-works-routing.md#how-routing-works
8998
[ingress-nginx]: how-to/ingress-https-nginx.md#configure-a-custom-nginx-ingress-controller
@@ -92,4 +101,5 @@ Currently, Azure Dev Spaces does not support using [pod managed identities][aks-
92101
[ingress-https-traefik]: how-to/ingress-https-traefik.md#configure-the-traefik-ingress-controller-to-use-https
93102
[quickstart-cli]: quickstart-cli.md
94103
[supported-regions]: https://azure.microsoft.com/global-infrastructure/services/?products=kubernetes-service
104+
[vs-code-multi-root-workspaces]: https://code.visualstudio.com/docs/editor/multi-root-workspaces
95105
[windows-containers]: how-to/run-dev-spaces-windows-containers.md

0 commit comments

Comments
 (0)