Nesting instincts: getting more out of transactions inside AutoCAD using .NET

I received this question by email last week: Is it ever required to use more than one transaction per program? The simple answer is that you mostly only need one transaction active per command: you shouldn't leave a transaction active outside of a command, as this is likely to cause problems at some point, and within your own command one transaction is typically enough to do what you want. That said, the transaction mechanism inside AutoCAD has some pretty cool nesting capabilities that make it very flexible and a great way to manage sets of database operation and to... Read more →