Thanks for the feedback!

I’m glad the post is helping. The series on IDisposable was probably my favorite, up until my new MVVM one Both are trying to tackle a subject that’s been talked about a lot, but take it on from a slightly different angle, in a bit more depth. I hope you find them useful.

-Reed

Thanks for explaining it clearly, I just forgot the purpose of the IDisposable interface. Actually, here AFactory class implements IDisposable interface to make it can be release it’s managed resources explicitly.

Keep your good work, I decide to go through all your MVVM articles. Actually, I get to know you in msdn forums, and find you can always explaining tech in clear words, and your suggestions in the blogs are very helpful.

It won’t be a problem. If AFactory is every a candidate for finalization, that means that all of its private managed resources (in this case, LicenseGenerator) will also be candidates for finalization. When LicenseGenerator’s finalizer runs, it will dispose of the unmanaged resource. There is no need for an explicit finalizer in AFactory, only in LicenseGenerator.

This is why, when encapsulating an IDisposable, you don’t need a finalizer – even though you still want to be IDisposable, and why the pattern is differnet in this case. If you directly contain a native resource, you need a finalizer – otherwise, you typically do not need one.

In this case, if the user forgets to call the dispose method of AFactory, unmanaged resources of LicenseGenerator will not be released. While in pattern1 and partter2. the finalizer will call dispose(false) to dispose unmanned resource when they forget to. Will this be a problem?