CQRS is potentially a large and complex topic with Enterprise Service Bus, Message Queues, etc. The Design Pattern Framework 4.5 does not cover these areas, but it focuses on the core 'Fire and Forget' aspect of CQRS. You will find this implemented in the Art Shop reference application, specifically when the shopping cart is updated with Ajax calls.
The CQRS pattern issues the request, starts a separate thread that will execute the update, and returns immediately without waiting for the results. The assumption is that it will execute without problems -- which it will in 99.999% of the cases. Essentially, the CQRS pattern states: "we are not going to have all users wait for the very, very small chance it may fail". In our mind, this philosophy makes a lot of sense.
Dependency injection is addressed and included. We use stubbed repositories, rather than a third party tool.
OAuth is covered in combination with SimpleMembership. It includes a fully functioning, end-to-end example in which users can sign up with Facebook.
I hope this answers your questions.
Jack Poorte, Sep 12, 2013