My vote is leaking ADO.NET database connections. My gut feel is that ADO
devs who are used to deterministic destruction of their ADO connection
objects will find it difficult (at first) to write the appropriate try
... finally blocks *everywhere* in their code to handle the cases where
the methods within the try {} block throw exceptions.What other errors have folks seen based on their own (or others) experiences? Has someone attempted to assemble a FAQ along these lines already? Thanks, -John http://www.iunknown.com You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
