>I actually prefer to have the disposable feature at the class level so I do not have to negotiate with that in the client class.
>
>Actually, I almost do not have any Using in a client application. All the Using, whereas any problematic of failure, memory leak and so on, are all plugged into the framework. Which is where I believe they all should be. So, any developer following the standards for development a new application, do not have to worry about that.

I'm not sure I understand this. Since Using ... End Using is a block in VB, it is difficult to "plug into the framework" no? My understanding is that it allows us to use an "unmanaged" resource, and control when that resource is relinquished, as opposed to wait until the Garbage Collector kicks in. Managing resources is a Client Application thing no?