Hi raist,

Would love to hear more details of using the llblgen as the data provider for WF! How far have you gotten along? Any good/bad issues along the way?

greenstone

In the end we're going to use Stateless instead of WF 4.0 http://code.google.com/p/stateless/

Last code in https://github.com/haf/Stateless

We're right now using it to get rid of page Redirects from nowhere and to set manual (long term) workflows.

Reasons for Stateless - Simpler. It has no graphical designer, but you can set a complete WF in just a page of code. - No hidden dependencies. Just set the states, transitions and transition functions and you're done. - Full WF schema control. Save your states in any <ID, state> pair in the database (we have created ad-hoc entities)

Right now, it's not so powerful as WF, but we don't need more before .Net 5.0 is out