Remove From My Forums

System.Transactions bug is fixed or not in .net 3.5 ?

Question
0

Sign in to vote

User2108726364 posted

Hi,

In my asp.net 3.5 appln i required to use system.transactions (distributed transactions)

and i am checking that topic i found .net have some bugs in the above name sapce implementation

and i would like to know if it is fixed in .net 3.5 or not

this is the discussion regarding the bug for reference

http://social.msdn.microsoft.com/forums/en-US/adodotnetdataproviders/thread/206e0b5d-4dcf-415a-83a8-04ccd90197c4/

thanks in advance

Friday, March 19, 2010 2:22 AM

Answers

0

Sign in to vote
User-952121411 posted

According to the thread you posted, the issue being discussed has been fixed via a new SqlConnection parameter called "Transaction Binding":

http://msdn.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connectionstring.aspx

(in above link read about "Transaction Binding" parameter for an enlisted System.Transactions transaction).

Here is another link detailing the solution:

Strange behaviour of TransactionScope with local transaction:

http://social.msdn.microsoft.com/Forums/en-US/adodotnetdataproviders/thread/78c6f17c-c612-4aa7-82c0-34a8ad69c07c

It appears that the specific issue you referred to has been fixed, and always make sure you have the .NET Framework 3.5 SP1 and all updates installed. If ever you still had a reproducible issue with System.Transactions, you can report it to Microsoft Connect, located at the link below:

http://connect.microsoft.com/
- Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
Friday, March 26, 2010 10:14 AM