We have a site design that makes use of modules that are developed separately from the master site. Thru reflection, we pick up the modules when the main app starts.

This works fine in local development and on a normal web server. But in the Azure environment when we try to use FTP to deploy the modules to our Azure-hosted site we are unable to because the main Azure deployment is read-only (because it is running from a package). Is it possible to not have the main site running from a package? Is it acceptable to run it that way?

Is there another way to deploy Dlls to the Azure-hosted site without having them be part of the main site's build and deploy? Ultimately we are trying to avoid rebuilding the main site every time we want to add a module.

CodePudding user response：

What can help in this situation is to build and publish the modules using Azure Artifacts.

There are several approaches please check the best practices page over here:

Refer to this doc.