I am currently creating a WCF web service.
As part of its job, it will unfortunately need to do some fairly intensive computations, however these computations can fo
Am I interpreting this correctly in thinking it means that MS does not guarantee that SqlCommand works in a multi threaded scenario?
It works fine in a multi-threaded scenario as long as you use it correctly.
If several threads try to use the SAME SqlCommand, what do you think will happen? How could it possibly work?
but if different threads using different connections issue different commands to the same database, there is no problem.
The notes about thread safety on MSDN are really broken and badly worded, and must be written by someone who didn't know what thread safety is.
What they're trying to say with that message (which is tacked onto 99.9% of the classes and functions documented on MSDN) is that "Any static method of this type can be safely called concurrently by multiple threads. Any instance members on the same instance is not guaranteed to be safe if invoked concurrently by multiple threads, but accessing the same member on different objects is perfectly fine."