SOLID – The Five Commandments of Good Software

This session shows how you can set up the architecture for your Windows Store App in a way that works well, both from a development point of view and from a designer point of view. Adopting the MVVM pattern is a step in the right direction, but unforutnately it isn't enough. Getting the most out of the tools requires the architecture to play nice, and working without the support of the tools is hard, so getting the architecture right is paramount.
May I know if it would cover the Blend tool? Thanks.
Hi Eric!
No, this talk will unfortunately not cover Blend at all. This is all code and architecture...
Cheers,
Chris
I enjoyed the session, but I must disagree with your assertion that async/await is more complex than callbacks.
First, there is an exception in the Task: Task.Exception. Conceptually, the Task<T> type can represent either success or error; it has both a Result and Exception property, which are roughly analogous to the two parameters for your callback.
Secondly, an implementation of IProgress<T> is already provided (Progress<T>), which you can instantiate with a delegate as such: "new Progress<int>(value => { ... })". In an MVVM app there's no need to create your own.
Those are the only real drawbacks to async/await that you mentioned. However, async/await also has several advantages over callbacks:
This conversation has been locked by the site admins. No new comments can be made.