Replacing an iPhone

Some time ago I got myself an iPhone and I have to admit I really love the little machine. But even good things can go bad and in my case it was a problem with the sound over the headphones. Well the machine has been replaced and I somewhat dreaded getting a new one and having to reinstall all apps and redo all settings.   Turns out I didn’t need to worry [:)] As it turns out Apple really thought about this experience and made sure it was as easy as it could be. Today when the replacement iPhone I … Continue reading Replacing an iPhone

Data and Windows Workflow Foundation 4

  One thing that has completely changed in Windows Workflow Foundation is the way we work with data in a workflow. In WF 3 we used properties to store data. We could use regular .NET properties but most of the time dependency properties where the smarter choice. Dependency properties left the way data was stored to be handled by the workflow runtime but in our program we could use them just like any other property. And the big bonus was we could use property binding to tie different properties on different activities together in any way we saw fit. These … Continue reading Data and Windows Workflow Foundation 4

More asynchronous work in Windows Workflow Foundation 4

In my previous post I showed how to use an AsyncOperationBlock to do some basic asynchronous work in WF 4. As I mentioned this was for relatively short lived asynchronous operations as the workflow could not be persisted and unloaded while this asynchronous work was executing. So how about real long running work, the kind you run into with real business application like waiting for an invoice to be paid?   With these king of jobs an AsyncOperationBlock will not work because you don’t want to keep the workflow in memory all the time. So what do we need to … Continue reading More asynchronous work in Windows Workflow Foundation 4

Basic asynchronous work in Windows Workflow Foundation 4

The whole asynchronous execution model in WF 4 has changed quite a bit from WF 3. Not really a surprise as this one of the areas where WF 3 was really hard to work with.   Below is a very simple example. It does nothing useful, it’s only task is to show how to get started with asynchronous work in WF 4. class AsyncWorker : CodeActivity { protected override void Execute(CodeActivityContext context) { var asyncContext = context.SetupAsyncOperationBlock(); var task = new Task(DoAsyncWork, asyncContext); task.Start(); }   private static void DoAsyncWork(object state) { var asyncContext = (AsyncOperationContext)state;   Console.WriteLine("Doing some work."); … Continue reading Basic asynchronous work in Windows Workflow Foundation 4

What does Windows Workflow Foundation 4 mean for existing workflow developers?

  The question of what Windows Workflow Foundation version 4 means for developers currently developing using WF recently came up. As I mentioned before WF 4 is a complete rewrite and doesn’t use any of the existing WF 3 classes. The design of WF 4 is even quite different from the design of WF 3.   So are WF 3 developers completely left in the dark and have to start from scratch? And what about their existing applications, will they still run on .NET 4 or are they stuck in .NET 3.5 until the end of times?   Fist of … Continue reading What does Windows Workflow Foundation 4 mean for existing workflow developers?

Congratulations 2009 Microsoft MVP!

Dear Maurice de Beijer, Congratulations! We are pleased to present you with the 2009 Microsoft® MVP Award! This award is given to exceptional technical community leaders who actively share their high quality, real world expertise with others. We appreciate your outstanding contributions in Connected System Developer technical communities during the past year.   O yes, I am happy again [:)]   [f1] [f2]