FrameworkElement에서 파생되고 제어되지 않는 클래스가 있습니다. 이 클래스는 OnInitialize 메서드에 이벤트 핸들러를 등록 합니다.
FrameworkElement가 OnInitialize에 대응하는 것을 제공하지 않기 때문에이 클래스를 적절하게 정리하는 패턴은 무엇입니까?
누수를 일으키는 EventHandler를 제거하는 부분이 없기 때문에 루팅 된 상태로 유지됩니다.
There's no such thing as "deinitializing". Initialization methods are used when it isn't possible to fully initialize an object in its constructor, because it depends on data that isn't available during construction. In these cases construction is broken in two phases: the first step is executed in a parameterless constructor, the second in an initialization method, like OnInitialize, after the external data becomes available
What you describe is object disposal, which is performed by calling an object's Dispose method. A well-written class should clean up its data, release any external resources and release any event handlers.
Visual elements typically have another step in their lifecycle, handled by the OnLoad/OnUnload methods. The Load step occurs when an element is actually placed in XAML view and connected to the other UI elements. Event handlers should be registered in the OnLoad method and removed in the OnUnload method.
If the element has no Dispose method , you may be able to raise the Unload event to force the cleanup, although this is a bit of a hack:
control.RaiseEvent(new RoutedEventArgs(FrameworkElement.UloadedEvent))
이 기사는 인터넷에서 수집됩니다. 재 인쇄 할 때 출처를 알려주십시오.
침해가 발생한 경우 연락 주시기 바랍니다[email protected] 삭제
몇 마디 만하겠습니다