Saturday, November 14, 2009

Slides and Demos from VS/Architect Connections This Week

I gave 4 sessions and repeat recorded a 5th this week at Visual Studio and Architect Connections in Las Vegas. The line up was as follows:

Build Workflow 4.0 Service Applications – covered the service messaging capabilities of workflow 4.0. Covered the Receive activity (and coupled SendReply) for exposing service operations from workflows, as well as Send/ReceiveReply (and the code generated activities) for calling services. Also covered the three forms of correlation: Request-Reply, Context (protocol), and Content correlation.

Slides    Demos

Wrap Your Head Around Concurrency in WF 4.0 – Covered all the many forms of concurrency in workflows. Where threads are doing what, how to use the parallel activities and the pseudo-concurrency that you get with that. Also showed how the built-in InvokeMethod executes asychronously, as well as how to build a custom async activity.

Slides   Demos

Connecting Smart Clients Through the .NET Service Bus – Covered basic use of .NET Service Bus to connect a client to back end services and the benefits of doing so. Also spent a good deal of time on event driven scenarios -  being able to push things to the client from back end services or for peer-to-peer communications from other clients. Discussed current and future state of affairs for document/data sharing and synchronization.

Slides   Demos

Build Testable Client and Service Applications – Covered practices and patterns for making applications more testable. Discussed benefits and principals of TDD, S.O.L.I.D., IoC, DI, Repository, Separated Presentation, and closed with a number of testability tricks for unit testing.

Slides   Demos





Saturday, November 14, 2009 6:56:11 PM (GMT Standard Time, UTC+00:00)
Comments [2]  | 


Monday, November 16, 2009 9:51:43 AM (GMT Standard Time, UTC+00:00)
Thank you,

All the new foundations open many new possibilities.
Monday, November 23, 2009 7:11:23 PM (GMT Standard Time, UTC+00:00)
<u>DI, DI, and IoC..."Who's on first?"</u><br>
One point I'd like to draw out is that it appears you have drawn very clean and distinct definitions between Dependency Inversion (a S.O.L.I.D. principle), Dependency Injection (a pattern), and an IoC Container (a tool). That distinction has been very helpful for me to understand these terms and how they play together. However, you then refer to an IoC Container in subsequent slides as a DI Container which I think then re-blurs those distinctions. I can see why they are often blurred because the recommendation is that people always use those three concepts together in order to be productive towards testability but I think that belabors . Hopefully this feedback helps.
Matt Poland
Comments are closed.









Ads by Lake Quincy Media









Sign In
Copyright © 2006-2007 Brian Noyes. All rights reserved.
Advertise on this site through Lake Quincy Media
designed by NUKEATION STUDIOS