As a result of being activated/deactivated/closed, a child of a conductor
might do something which results in the conductor changing its items
collection. Therefore make sure that this collection is copied before
calling into the children while iterating.
Fixes#13
* release/1.1.17:
Update changelog
Add default FlowDirection and TextAlignment to MessageBoxViweModel
StyletIoC: Detect basic copy constructors, and don't attempt to call them
Dispose Instance bindings by default, but allow this to be configured
This removes the MessageBoxOptions input to MessageBoxViewModel, and
replaces it with explicit FlowDirection and TextAlignment inputs.
I think this is fair enough - we weren't using most of the members
of MessageBoxOptions, so allowing them to be provided was misleading.
Fixes#12
This can be used to manually change the state of properties, without using
the IModelValidator stuff. This handles more niche use-cases which don't
fit the pattern established by the IModelValidator.
There's no nice way to make it work alongside CanCloseAsync when you're
in a conductor hierarchy. There will always be difference between how
CanClose and CanCloseAsync behave when there are children which need
to be interrogated as well, and that's confusing.
NuGet's 'content' approach broke horribly when we tried to upgrade:
it removed App.xaml.cs.
Using powershell through and through is more powerful: we can have a
package which immediately uninstalls itself, which means it doesn't
remain part of the user's package set. We can also be smarter about
upgrading the project: we don't nuke anything that's in App.xaml, we
don't need the user to manually delete MainWindow.xaml, and we can keep
anything that's currently in MainWindow.xaml
* release/1.1.14:
Update changelog
Fix bug in ViewManager when searching multiple assemblies
Throw (by default) if ToAllImplementations does not find any implementations
Fix typo in DesignMode sample
Fix DesignMode sample
This will happen if someone takes a concrete class (with no subclasses), uses
ToAllImplementations on it (and InSingletonScope), and wonders why the singleton
registration didn't 'take': the ToAllImplementations didn't create any bindings,
so we fell back to auto-binding the type