This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
In an older asp.net webforms site we create a What is the best way to prevent SaveChanges() in this case if some kind of application error has occurred where you don't want pending changes persisted? Is there a property that can be set on the Context, UnitOfWork or PerRequestUnitOfWorkScope that can be later checked before SaveChanges() is called in EndRequest or do we just to roll out own boolean property for this? |
|
|
You will need to roll something yourself to cater for this, so presumably performing some action in Application_Error which is later picked up in EndRequest would cover this.
|
|