Hello,
I'm ashamed for the name of the class :)
But for the Dispose() of WebClient, I'm not agree with you:
WebClient inherits from Component and need a Dispose() if you attach it via the designer into a Windows Form for example.
But WebClient didn't override Dispose(bool disposed) and thus, no resources will be claimed.
About the empty catch, I already think about a logger. But I think people would want a more verbose logging (about the tag processed, style applied, ...) and the hard and long work it will generate to me.
So I drop the idea but after your post, yes I should implement one. I will read again the MSDN about TraceSource & TraceSwitch ....
I'm ashamed for the name of the class :)
But for the Dispose() of WebClient, I'm not agree with you:
WebClient inherits from Component and need a Dispose() if you attach it via the designer into a Windows Form for example.
But WebClient didn't override Dispose(bool disposed) and thus, no resources will be claimed.
About the empty catch, I already think about a logger. But I think people would want a more verbose logging (about the tag processed, style applied, ...) and the hard and long work it will generate to me.
So I drop the idea but after your post, yes I should implement one. I will read again the MSDN about TraceSource & TraceSwitch ....
