Process tasks

Process tasks

Old forum URL:

Joentje posted on Tuesday, December 27, 2011


CSLA supports an easy way to develop business objects. But how do I implement use cases? That is, where do I put the code that goes beyond the responsibility of individual business objects? We use Task classes to accomplish that. But does CSLA prescribe a ready-for-use solution for this common problem?

Thank you very much in advance for your answer!

Kind greetings,

JonnyBee replied on Tuesday, December 27, 2011


We often call this a UnitOfWork (UOW) model and it translates into a

For non-CRUD operations on a database we use CommandObject (from CommandBase).


ColourHaze replied on Monday, May 27, 2013

Hi jeroen,


i understand the idea of task objects, or as johnny adviced, uow, but how do you "glue" them together?


point 5 of rocky's post describes the process object consisting from command objects, but this does not seem to be a "standard" pattern. 

Also found a post on orchestration pattern idea Looks quite clever as well.

I dont exactly know how to approach this. Curious on your ideas!

Best regards,


Copyright (c) Marimer LLC