> DEBUG info at no price.. so to speak
Can't help on the buffering, but your comment above isn't necessarily correct at any rate. It depends on where the performance his of the Debug() call is. Sure there's a hit on writing the log to disk, and the buffering helps there, but there is also the hit of generating the text for the debug call in the first place. There's the method call, there's the string concatenation, there's likely numerous .ToString() calls, if you're looking for line#s in the log file then there's the (high) cost of getting that information. None of these issues will be removed by buffering the write to disk. I'm not saying buffing won't buy you something, it will. But it doesn't give you DEBUG at no price. -Walden -- Walden H Leverich III Tech Software (516) 627-3800 x3051 wald...@techsoftinc.com <mailto:wald...@techsoftinc.com> http://www.TechSoftInc.com <http://www.techsoftinc.com/> Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.)
