Visual Studio and .NET Framework Home
Getting a ObjectDisposedException in a TransactionCompleted when TransactionScope ends
8/20/2007 8:06:20 AM
User(s) can reproduce this bug
When registering to a TransactionCompleted event of a TransactionScope I get a ObjectDisposedException when trying to access the TransactionScope to figure out how the transaction ended (commited or rolled back).
Searching the web, I found that other users have the same problem. A very detailed description and a workarount are published here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=914869&SiteID=1
As the problem seems not to be reported here I thought I shoud do it...
.NET Framework 2.0
Windows XP Professional
Operating System Language
Steps to Reproduce
using (TransactionScope scope = new TransactionScope())
Transaction.Current.TransactionCompleted += new TransactionCompletedEventHandler(delegate(object sender, TransactionEventArgs e)
TransactionStatus status = e.Transaction.TransactionInformation.Status;
Getting an ObjectDisposedException when accessing e.Transaction.TransactionInformation.Status
Getting the status (committed / rolled back) of the exception
TAP Code (if applicable)
You can indicate your satisfaction with how Microsoft handled this issue by completing this quick
3 question survey
to post a comment.
Please enter a comment.
on 11/24/2008 at 1:36 AM
I am having the same problem in a more complicated scenario (in a WCF service) using Visual Studio 2008 SP1.
on 8/20/2007 at 8:07 PM
Thanks for your feedback. We have reproduced this bug on Visual Studio 2008 Beta 2, and we are sending this bug to the appropriate group within the VisualStudio Product Team for triage and resolution.
Visual Studio Product Team.
on 8/20/2007 at 5:07 PM
Thank you for your feedback. We are currently investigating. If this issue is urgent, please call support directly (see http://support.microsoft.com).
Visual Studio Product Team
to post a workaround.
Please enter a workaround.
© 2013 Microsoft