MSDTC is not technically required on the BeerHouse, just SQL forces you down that path - TBH uses nested transactions over the same connection - an outer tran to create the order ID and the inner ones to add each product to that order - comitting all transactions in one big bang at the end.
I also began coding round it and got it working by closing the tran to get the order ID and opening a new one to add each product (storing order ID in a local var and passing it through each time) - dig around in MB.TheBeerHouse.BLL.Store. But you don't want to do that -
Just add this to the end of the connection string ...
;Enlist=false
...this tells sql server not to worry about promoting transactions and just get on with the job - as long as the connection remains open you are laughing and the site will work without begging for MSDTC to be turned on. NO CODE REQUIRED!!
The up side - the web site will perform a bit quicker and you can host it anywhere.
The down side - you are not using the full promoted transaction scope of SQL 2005 and run a miniscule risk of the transaction not rolling back if it loses the connection half way through. TBH stores the order in the database anyway so the user can go to the orders page an finish at a later date.
Have fun! John ...c/o blickberry.com (work in progress)
