>>I was actually looking at this : a problem with the constructor overloads of StreamReader
>>But would have needed some time to figure out exactly how
>
>Yes, when I read it three times, the overload pointed me to the right direction. Also, in the designer, only one parameter definition is shown but that one can take two. As is, it works. But, if within a Using, it must know exactly what we deal with.
>


Within a Using - it must only know that the object implements IDisposable - the rest, the using doesn't care

Think the problem was that it was not clear which constructor of StreamReader() it had to pick ( string or Stream)



>>Keep us informed whether the extra usings solves your problem
>
>Yes, this one is very random. It might take months before I can confirm that we never had any more occurence of such situation.