AVOID calling Dispose() on owned objects that have a finalizer.
Instead,rely on the finalization queue to clean up the instance.

>有人可以详细说明这一点,因为我不清楚Dispose的重点是什么,如果我们不从拥有的对象中调用它？
>除了Reflection之外,你怎么知道对象是否有Finalizer？
>你如何知道何时调用Close()/ Close()Dispose(),而不是搜索API文档(如果你有权访问它并且它存在)或反射？对于非常特定的类型(MemoryStream / Form / sqlConnection / etc),我在网络上看到很多问题,但我更关注“如何自己解决”.

根据Dispose Pattern你应该：

CONSIDER providing method Close(),in addition to the Dispose(),if close is standard terminology in the area. When doing so,it is important that you make the Close implementation identical to Dispose and consider implementing the IDisposable.Dispose method explicitly.

但有时你应该像表格一样打电话.像“Close and Dispose – which to call?”这样的问题越来越接近,但除此之外没有明确的方法

As usual the answer is: it depends. Different classes implement IDisposable in different ways,and it’s up to you to do the necessary research.

编辑：这是完整的指南,我没有要求复制许可,但因为它是一个指南(因此假设它应该是自由共享的公共知识)而不是实际培训材料的某些部分,我希望我’我没有违反任何规则.

Guidelines
DO implement a finalizer method only on objects with resources that are scarce or expensive,even though finalization delays garbage collection.
DO implement IDisposable to support deterministic finalization on classes with finalizers.
DO implement a finalizer method on classes that implement IDisposable in case Dispose() is not invoked explicitly.
DO refactor a finalization method to call the same code as IDisposable,perhaps simply calling the Dispose() method.
DO NOT throw exceptions from finalizer methods.
DO call System.GC.SuppressFinalize() from Dispose() to avoid repeating resource cleanup and delaying garbage collection on an object.
DO ensure that Dispose() is idempotent (it should be possible to call Dispose() multiple times).
DO keep Dispose() simple,focusing on resource cleanup required by finalization.
AVOID calling Dispose () on owned objects that have a finalizer. Instead,rely on the finalization queue to clean up the instance.
AVOID referencing other objects that are not being finalized during finalization.
DO invoke a base class’s Dispose() method when overriding Dispose().
CONSIDER ensuring that an object becomes unusable after Dispose() is called. After an object has been disposed,methods other than Dispose() (which could potentially be called multiple times) should throw an ObjectDisposedException.
DO implement IDisposable on types that own disposable fields (or properties) and dispose of said instances.