We don't need this. Azure supports writing tp ~/App_Data. There is no
guarantee that the content will persist, but that's exactly the assumption
of the IAppDataFolder abstraction: it's a local cache, which persists
for _some_ time accross app restarts.
--HG--
branch : dev
- added a DisplayName to the ContentTypeDefinition
- added a CreateRouteValues rvd to go along with the existing display and edit
- set default display, edit and create route values for ContentItemMetadata (* should get fallback route values in a different manner. probably not good to refer to an area, even by string, in core from the fwk)
- starting to shape up the content type list into a more consistent UI
- added create type action, view, etc. for creating new content types
- supporting service has a few default parts hard-coded for now
--HG--
branch : dev
- Relies on the Activated event to weld fields to parts.
- New event Initializing added to the content management lifecycle, old Activated event is now Initializing.
- Unifying part and field template result classes.
- Refactoring.
--HG--
branch : dev
OrchardHost calls into all extension loaders to all extensions descriptor,
allowing each loader to add the set of resource to monitor for change.
OrchardHost resets its list of shells at the beginning of a request if
any monitored resources has changed.
--HG--
branch : dev
Verify consistent use of descriptor and blueprint
Update namespaces, but not folder paths, of same
Add small ISignal component for explicit app-triggered cache expiration tokens
--HG--
branch : dev
First pass is "probing": any loader who thinks it can load a
given extension returns a descriptor for it. The descriptor contains
information about how old the extension is.
The extension manager sorts the descriptor list return by probing all
loaders, and picks the most recent entry.
During the 2nd pass, each loader is called again, with the candidate extension
entry as argument. This allows each loader to be notified that, if they don't
load an extension, they might still need to cleanup some state related to
previous loading.
In essence, this is implementing a complete state machine of loaders and
extension "active/inactive" states/transitions.
--HG--
branch : dev
Refactor IAppDataFolder so that it can be used for implementing
DefaultDependenciesFolder.
--HG--
branch : dev
rename : src/Orchard/Environment/Extensions/Loaders/WebFormsExtensionsVirtualFile.cs => src/Orchard/FileSystems/Dependencies/WebFormsExtensionsVirtualFile.cs
rename : src/Orchard/Environment/Extensions/Loaders/WebFormsExtensionsVirtualPathProvider.cs => src/Orchard/FileSystems/Dependencies/WebFormsExtensionsVirtualPathProvider.cs
rename : src/Orchard/Environment/IVirtualPathProvider.cs => src/Orchard/FileSystems/VirtualPath/DefaultVirtualPathProvider.cs
rename : src/Orchard/Environment/ICustomVirtualPathProvider.cs => src/Orchard/FileSystems/VirtualPath/ICustomVirtualPathProvider.cs
