ADO.NET Async command no-no number 2

Monday, August 16, 2004

As I worked on async ADO.NET commands on Sunday, I learned an important lesson. If you have a pending async command that has not executed its end execution command, don't try to start off another one. if you do, you will get an InvalidOperationException with the message: A command execution cannot proceed due to a pending asynchronous operation already in progress.

Wally

3 Comments

I believe that it is per-command object. If a command has a pending async command and you try and execute another async command on the same command object that is currently waiting for an async command object to complete.

Wally

Wallym - Tuesday, August 17, 2004 4:19:00 PM
OK. That I would expect. Maybe MARS will fix that in VS 2005.

Doug Reilly - Tuesday, August 17, 2004 4:57:00 PM
That should be on Sql2k5. On Sql2k, I think it is per command and per connection.

Wally

Wallym - Monday, August 23, 2004 2:51:00 PM

Comments have been disabled for this content.