>>Why not just create a static class?
>
>Short answer: it depends on what purpose the class serves.
>
>In Tim's case, his class needs to be an instance rather than static, because his instance fires events, etc. That wouldn't work with a static class.

That's helpful, thanks!

>
>But, as Tim also says, the Singleton pattern seems to be overused. <g> So, did you have some particular use in mind or is this just a generic question?

It referred to a C# test I saw where the class had to be thread-safe and a singleton.

>~~Bonnie