Well, yes, I guess you could call it - I doubt there is any harm (try it in Instruments? See if it does release it).
The GC is pretty agressive (too agressive at times), so I doubt you'd be saving yourself much, except peace of mind, which is worth a lot :) On 20 February 2013 17:40, Len Charest <l...@shingl.com> wrote: > Sure, but Dispose seems like an attractive alternative to the deprecated > ViewDidUnload method for hosting cleanup logic that you'd like to execute > immediately. > > > On Tue, Feb 19, 2013 at 12:23 PM, Nic Wise <n...@fastchicken.co.nz> wrote: >> >> I've never bothered, and it's never been an issue. Just make sure you >> are not holding a reference to it anywhere, and the GC should clean it >> up for you. >> >> On 19 February 2013 17:24, Len Charest <l...@shingl.com> wrote: >> > Is it necessary and/or best practice to dispose view controllers that >> > have >> > been popped off of a navigation controller? E.g., programmatically: >> > >> > myNavigationController.PopViewControllerAnimated(true).Dispose(); >> > >> > If so, what is the best way to capture a reference to the controller >> > that is >> > popped when the user touches the back button? (A back button touch does >> > result in a call to PopViewControllerAnimated, but the nav bar delegate >> > does >> > not pass a reference to the target controller in its DidPopItem method.) >> > >> > Thanks, >> > Len >> > >> > _______________________________________________ >> > MonoTouch mailing list >> > MonoTouch@lists.ximian.com >> > http://lists.ximian.com/mailman/listinfo/monotouch >> > >> >> >> >> -- >> Nic Wise >> t. +44 7788 592 806 | @fastchicken >> b. http://www.fastchicken.co.nz/ > > -- Nic Wise t. +44 7788 592 806 | @fastchicken b. http://www.fastchicken.co.nz/ _______________________________________________ MonoTouch mailing list MonoTouch@lists.ximian.com http://lists.ximian.com/mailman/listinfo/monotouch