![]() ![]() However, assuming you’re leveraging an existing codebase you’ve written in 1.x, or you have another request for the TableAdapters, you can simply take advantage of partial classes to add just about any functionality you’d like. If you search this blog you’ll see several references to using the new TransactionScope object to very easily wrap several TableAdapters in a single transaction that will automatically enlist DTC when needed, or simply leverage SQL 2005 transactions when working with a single database. With 2.0 we now have a great solution with System.Transactions. ![]() It may be related to supporting transactions across multiple updates, or how do I set the UserId as a parameter on an update statement that isn’t represented in the DataTable?įor Transactions, we don’t expose a Transaction Property by default because this was tedious task in 1.x of the framework. A number of posts have asked how to extend TableAdapters to support additional functionality. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |