Visual Studio 2008/CSLA 3.5
We are using CSLA transaction for database operations.
protected override void DataPortal_Update()
....other code (update/insert/delete) goes here..
Q. How can i control rollback or commit and not depend on CSLA. This is required where based on some conditions i need to do commit/rollback and come out of the process?
Use manual transactions (don't use the Transactional attribute) and create your own TransactionScope object.
Copyright (c) Marimer LLC