8 Commits

Author	SHA1	Message	Date
Antony Male	f36de34bb2	Execute.Dispatcher can never be null, and dispatches synchronously by default ... The previous behaviour was to raise an exception unless Execute.Dispatcher had been explicitly defined. This was to detect cases where the user hadn't set up Execute correctly, and treat them as errors rather than simply going ahead with some possibly-unexpected behaviour. However, since BootstrapperBase sets Execute.Dispatcher automatically, it's highly unlikely that itwould ever not be set when it needed to be. Exceptions are design mode and unit tests, both of which want (or can cope with) a synchronous dispatcher. Hence the behaviour change. Execute.Dispatcher is a synchronous dispatcher by default, but is overridden to one that uses Application.Current.Dispatcher by the bootstrapper if we're in a real application.	2015-01-04 21:30:34 +00:00
Antony Male	9ee23f1469	Remove Execute.TestExecuteSynchronously, in favour of a synchronous IDispatcher implementation	2015-01-04 13:10:37 +00:00
Antony Male	6d72032f8c	Allow IModelValidator to return IEnumerable<string> rather than string[] ... Closes #1	2014-12-26 22:55:41 +00:00
Antony Male	94d4a31b85	Be draconian about using readonly where appropriate	2014-12-04 17:06:12 +00:00
Antony Male	25e025f542	Fix warning in unit tests	2014-08-04 07:59:44 +01:00
Antony Male	9532f3eca1	Change capitalisation of ValidationModeBase.AutoValidate	2014-08-02 17:54:15 +01:00
Antony Male	bac99ab647	Refactor ValidatingModelBase slightly to support easier overriding	2014-05-13 17:56:54 +01:00
Antony Male	1e76531e36	Add test code coverage for ValidatingModelBase	2014-05-08 17:37:33 +01:00