T
Tom Shelton
Problem: XmlTextReader Constructor hangs until underlying socket closes
when passed a NetworkStream.
Example:
Dim reader As New XmlTextReader (New NetworkStream(s, False))
I can positively confirm by the way that this only happens AFTER
installation of SP1 for framework 1.1. So, has anyone else have this
issue? I was able to recreate this on 3 different boxes (All windows
XP, 2 with SP2 and 1 without). Everytime, our custom dataprovider hangs
on that line of code. The code is actually in C#, but I don't think
that makes a difference What I do know is that this provider has
been working for several months now for several months - pre SP1.
Anyone experience this issue with SP1? Anyone know of a work around?
Other then rewriting our dataprovider
This is sort of a big issue, since SP1 is on windows update - and I'm
sure were going to get several customers calling in with this problem
over the next few days. Fortunately, we found that uninstalling the
runtime and reinstalling the old version makes everything work again,
but we would rather find a permanent fix if there is one...
when passed a NetworkStream.
Example:
Dim reader As New XmlTextReader (New NetworkStream(s, False))
I can positively confirm by the way that this only happens AFTER
installation of SP1 for framework 1.1. So, has anyone else have this
issue? I was able to recreate this on 3 different boxes (All windows
XP, 2 with SP2 and 1 without). Everytime, our custom dataprovider hangs
on that line of code. The code is actually in C#, but I don't think
that makes a difference What I do know is that this provider has
been working for several months now for several months - pre SP1.
Anyone experience this issue with SP1? Anyone know of a work around?
Other then rewriting our dataprovider
This is sort of a big issue, since SP1 is on windows update - and I'm
sure were going to get several customers calling in with this problem
over the next few days. Fortunately, we found that uninstalling the
runtime and reinstalling the old version makes everything work again,
but we would rather find a permanent fix if there is one...