Home/ Questions/Q 9157793
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-17T13:06:21+00:00

I’m planning to develop a multi-tier .NET application, with at least three separate layers

  • 0

I’m planning to develop a multi-tier .NET application, with at least three separate layers hosted on Azure:

  • Web frontend
  • Backend / worker role
  • Database

I would like to use Azure Git Publishing with GitHub to enable continuous deployment of each of the layers separately. What’s the best way to organize the git branch(es) to enable Azure deployments for each of the components individually, while also sharing code between them?

Preferably, I would like to have all the code in one git branch and set up separate build/publish processes for each in Azure. However, I suspect this won’t work because:

  1. Azure uses any push in a branch to trigger a deployment. I don’t want updates to my frontend to trigger a deployment of my backend.
  2. As far as I know, there’s no way to configure the build command that Azure uses to generate outputs to publish.

If I need to use separate Git branches, what’s the easiest way to share code between them?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    According to this related question, Azure git publishing is only available for websites, not cloud services.

    So, the question of organization to allow for separate project publishing is irrelevant. The easiest option will be to keep projects in a single Git branch and use traditional Azure deployments (not automatic Git publishing).

    • 0