« Xamarin - Notes on Handling Rotations across Platforms | Main | Sitecore 7 Page Editor Ribbon Fix »

July 23, 2013


TrackBack URL for this entry:

Listed below are links to weblogs that reference Memory Management Pitfalls in Xamarin.iOS - Pitfall 2:


Feed You can follow this conversation by subscribing to the comment feed for this post.

Thanks for the article. With a bit of coding WeakReference can be used for event handlers too. This means your event handler will never prevent your ViewController from being disposed. This has the big benefit of you never having to unsubscribe from the event. MvxWeakEventSubscription is an example of this pattern which is found in the excellent MvvmCross framework.

Excellent point. I know Xamarin has also shown using WeakReference to keep parent/child view relationships from causing issues as well. I don't personally love the 'stuff' that goes with using WRs, but maybe if it was wrapped up in something it would feel better. Thanks for the comment!

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.


Post a comment

Comments are moderated, and will not appear until the author has approved them.