Ok, last time I mentioned I was having problems using VSSwSe 1.3 on my 2008 r2 server, in particular the problems developing Sharepoint Workflows. After going through the process of manually creating a workflow WSP, I decided that this workaround was just not good enough as I'm wanting to concentrate on workflow. Instead I thought I'd jump ship and try WSPBuilder. To be honest, the ast time I had used this I wasn't too impressed as there seemed to be too much manual work to do. However, that was when I was learning sharepoint development. This time around I found it very straightforward and provided the flexibility to do everything I wanted, plus building workflows on my 2008 r2 machine worked without a hickup....guess I'll be sticking with WSPbuilder until MS convince me that VSSwSe can beat it.
Workflow
So, back on to my workflows. First things first and I put together a nice simple workflow just to test things out end to end. After this worked, I then wanted to start to look at what I would really want from Workflow. Having spent a lot of time recently using K2 Blackpearl to put together some beefy workflows to support line-of-business applications, I want to see if Sharepoint WF can do the same and not just provide nice simple 'approval' style workflows.
My first step here is poducing a flexible form solution for task processing. To be honest I really don;t like having to use Infopath for this, so I want to support something that will provide beefy forms processing using ASPX. Now, there is a built in way to do this by using ContentTypes with custom Display/edit pages, along with the custom association/mod forms. My aim here is to build a generic form handler (like the IP forms handler), that will load up on-demand ascx files based on the task definition.
I'll let you know how I get on.