>>COM+ is designed to prevent deadlocks and has a long history of doing >>just that. It makes building a transactional application simple as >>building a single user app.
Yes, but doesn't it do so by picking a lock victim and terminating the victim's transaction? I thought that a developer should always be cognizant of the order in which locks are obtained to try to avoid deadlocks -- or potential deadlocks where a victim must be selected. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
