Hi Guys,

I have a wizard thats collects user actions to a unit of work object and commits them. All in all, seems to be working quite well util I reach the following code:

                
//  delete current relationships                
IRelationPredicateBucket bucket = new RelationPredicateBucket(ProductVsCategoryFields.ProductId == entity.ProductId);
work.AddDeleteEntitiesDirectlyCall("ProductVsCategoryEntity", bucket); 
                
// create new relationships
foreach (int categoryid in categories)
{
ProductVsCategoryEntity category = new ProductVsCategoryEntity();                   
category.ProductId = entity.ProductId;
category.CategoryId = categoryid;
category.IsNew = true;
work.AddForSave(category);
}  

Independantly, the delete parts and the save parts work correctly but when used together the Saves are performed first and the Deletes afterwards. Is there anyway around this?

Cheers,

Th

This thread discusses similar issues:

http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=6694&HighLight=1

I ran in to a similar problem and ended up using a transaction instead of a UOW.

Hi there,

I stumbled across that thread also. Luckily I can code around it with a extra line or two in the controller but I was a little disappointed that I don't have more control over how the UoW is saved. Thanks for the link though,

Marcus, did you ever implement your own UoW object?

Cheers,

This feature will be implemented in the upcoming upgrade (was already planned).

Great news. Thanks