I think what is happening is that the caller is calling reader.NextResult() which returns false as it is pointing past the last item in the result set. The caller should stop at this point, but must not be checking the return value. Then it calls reader.Read() which throws.
From the stack trace reported, it's the only way I can see that this could happen.
Fixes #102
I think what is happening is that the caller is calling
reader.NextResult()which returns false as it is pointing past the last item in the result set. The caller should stop at this point, but must not be checking the return value. Then it callsreader.Read()which throws.From the stack trace reported, it's the only way I can see that this could happen.
I've made
reader.Read()more robust.