DefaultOrchardHost may now implement eventhandler interfaces directly
DefaultOrchardHostEventSink assistant is obsolete for that reason
DefaultOrchardEventBus changed to use interface methodinfo rather than class methodinfo
OrchardStarter includes EventsModule with root container to allow components to receive event firing proxies
Special case added to CompositionStrategy to prevent DefaultOrchardHost from being re-registered when shell container is built
EventsModule is internal to prevent it from being re-registered in the same way
--HG--
branch : dev
ShellSettings and ShellDescriptor string-named events removed
IShellSettingsManager and IShellDescriptorManager have associated event interfaces
Orchard host event sink forwards those two interfaces to default orchard host (special case - orchard host can't enlist normally)
--HG--
branch : dev
- Refactoring ZoneManager to use IEventHandlers.
- Other related changes to event handler based components, removing unneeded looping through handlers in the component since the event bus does that.
--HG--
branch : dev
Need some autofac tweeks as ShellSettingsManager can't have a dependency on, and DefaultOrchardHost can't implement IEventHandler
Currently modified IOrchardHost by adding InvalidateShells() which is called by TenantService.
To do: Remove InvalidateShell, make DefaultOrchardHost implement IShellSettingsEventHandler, and make ShellSettingsManager fire the events
--HG--
branch : dev
- It's used in part for the content widget wrapper. Would be nice to have real wrapper template functionality. Something to keep in mind when we get on with the theme/UI composition story.
--HG--
branch : dev
- tenant database setup can be preconfigured
- site setup UI reflects available settings (e.g. if database setup is preconfigured then don't show db options)
- updated jQuery from 1.4.1 to 1.4.2 (finally)
--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
