> I really appreciate you asking about this but the bug is not in the
> plugin and therefore this bug should not be included in that category.
Ok!
(Wasn't sure how to interpret "directly related", but I assume you
meant "is in the source code of the visual studio plug-in", then.)
> I have not studied this bug extensively enough to know if it's
> a problem in the server or the connector.
I presume there is no workaround in the .NET connector, then ;-).
It's a server problem - I'd make a test case with the visual studio
plug-in to see how it shows it's ugly face here, but if you don't want
a bug report about it, then I guess the point is moot..
