cjard
Well-known member
- Joined
- Apr 25, 2006
- Messages
- 7,081
- Programming Experience
- 10+
I'm facing an issue using the Transactions namespace with the System.Data.OracleClient
Something on the system, I suspect an oracle DLL, does not like having a debugger attached to it; As soon as I attempt to run any database related statement within a transactionscope, while in debug mode (though not necessarily singlestepping), i receive an error message saying "Attempt to read or write protected memory"
I'm presuming this is caused by the debugger attampting to attach to what oracle's driver dll code is doing. If i run the project in Release mode the code works perfectly. I havent had an answer from oracle, so i'm wondering if I can prevent the debugger from attaching to anything related to System.Data.OracleClient or any library within the transactions namespace?
Something on the system, I suspect an oracle DLL, does not like having a debugger attached to it; As soon as I attempt to run any database related statement within a transactionscope, while in debug mode (though not necessarily singlestepping), i receive an error message saying "Attempt to read or write protected memory"
I'm presuming this is caused by the debugger attampting to attach to what oracle's driver dll code is doing. If i run the project in Release mode the code works perfectly. I havent had an answer from oracle, so i'm wondering if I can prevent the debugger from attaching to anything related to System.Data.OracleClient or any library within the transactions namespace?