The AzureBlobStorageProvider components must be registered as a
per-lifetime-scope in the "Shell" container, not in the "Host" container.
This is why it must be registered in the "Config/Sites.Config" file instead
of the "Config/Host.config" files.
This also allows us to remove the "AZURE" compilation directive from
Orchard.Framework implementation.
All in all, this ensures that the files stored in the "Media" folder
are stored in the Azure Blob Storage even when running locally in
Visual Studio.
--HG--
branch : dev
extra : transplant_source : %3E%E2%82g%18M%AB%26xi%CA%19%99H%3A%A0%20%F0%B2F
We need to copy contents files from Modules, Themes and Core directory
of Orchard.Web into the respective directory in Orchard.Azure.Web.
This is because when running Orchard.Azure.Web in Visual Studio, the web
application runs from the Orchard.Azure.Web directory.
Also update .hgignore file to ignore these directories.
--HG--
branch : dev
extra : transplant_source : %BB%F5j%1ANvL%B2g%2C%7EQ%3A%10VT%EA%D7%28%B5
- Removes automatically teh system.extensions tags which prevents MVC from working on Azure
- Updated web.config with Orchard.Web's one
- Added a machineKey for server farm scenarios
--HG--
branch : dev
Executing ClickToBuild.cmd generates the package for Azure including all modules available in Orchard.Web automatically
AzureSDK in requiered for this tasks. If not present, the package won't succeed, but Orchard.Web will still be built
The Orchard.Azure solution contains the required environment for implementing Azure specific providers, and unit testing
The Orchard.Azure.CloudService solution contains the CloudService enrironment to simulate Azure platform locally
--HG--
branch : dev
