Just submitted 5 sessions that hit just about every angle of WF4 so hopefully they will add me in the lineup for speaking at DevConnection next year. I have spoken at the conference before however I was a co-speaker.

Just finished my session on hosting workflows using WF4 in Windows Server AppFabric! I actually thought that I might not have enough demos for the session time, however my work paid off last week and I made more than I could show. First I showed how to build a custom workflow host with persistence. I demonstrated that I could shut down the host and pick back up where the workflow left off. Then I moved to building a workflow exposed as WCF. I showed how this was using raw ADO.Net but also showed how Entity Framework 4.0 could be used as well. Finally I pushed the workflow service into AppFabric and connected a client to it. On purpose I added more characters than the database field could hold so that the call would fail. I did this because I was able to work with the monitoring senarios with AppFabric when I got the same error by mistake:(. This was a nice turn into how AppFabric worked and how monitoring could be used to detect the errors that the client app could not see.

You might not see this error until you start deploying workflow services to Windows Server AppFabric and configuring persistence or host management!

 

 All it means is that you need to add "net.pipe to the list of protocols the applicaiton can use. To do this

1. Click on the deployed Application
2. Click "Advanced Settings..."
3. Look for "Enabled Protocols" which probably has "http" already added
4. Add ",net.pipe" like below

This weekend I am headed over to Tally once again to present on hosting workflows on Windows Server AppFabric at their code camp. I have finished my slides and VMs and currently I am working on the demos.