Hi all, Has anyone had any problems using the TransactionScope class in the System.Transactions namespace? It works fine for me locally, but my code falls down when I upload it to the DiscountASP.NET server. I read somewhere that the Distributed Transaction Coordinator service has to be running to use this class. Does anyone know any more re: this? My intention is to use a transaction to make sure that the entire order (with order lines) is commited to the database, or nothing at all (if the event of something going wrong). My code looks something like:
I have never used TransactionScope but it does indeed look very cool. Doing a quick search just now I found this article: http://www.codeproject.com/KB/database/TsFix.aspx I can't answer any specific question regarding this but I did find that article very interesting. Salute, Mark
This won't work on our server because of certain technical difficulties related to the server setup. Bruce DiscountASP.NET www.DiscountASP.NET
I thought it was because of the dependence on distributed transactions that is inherit and supported, although not always required, when using transaction scopes.
The line of code should not have no problems when executed from your .net application junior DiscountASP.NET www.DiscountASP.NET
