… tempted to give up when working with the Windows Workflow Foundation – I was glad to find another frustrated developer. I’ll blog about my experiences of this so far, once I’ve calmed down enough to be coherent. Being able to attached a UI to the workflow tasks in SharePoint would be nice too, but that eludes me.

Still, maybe that’s for the best – we’re supposed to be using Infopath 2007, and my colleague working with that has started talking to himself. In a high-pitched voice. It’s not pretty. Seems there is even less documentation about this, and both of us are left with one question – wtf d’you want Infopath for? Yes, it makes XML, but that’s pretty trivial – we’ve all written forms that do that. (Well, all the geeks in the house).

So you can have a rich client for Infopath. Um, why? Lets see, zero footprint web forms, or Microsoft install. The phrase ‘lead or silver’ springs to mind – pay silver for our client, or get shot down with our web forms. And as our form is going to display an image from another document management system, and as the client will not be using the rich client thingy, well, we’re busy puzzling what we get from Infopath over ASP .net forms, apart from heartache and ulcers.