It's that time of year again - PDC 2010 kicks of tomorrow! Join the Silverlight Performance Team as we take you through the high level analysis of common performance issues that apps commonly run into. I'll be giving a live session titled "Optimizing Performance for Silverlight WP7 Apps" at 3:15pm (PDT) on day 1 (28 October 2010).
Even if you couldn't make it here to heckle me in person, the rest of the team will be online and answering your questions (or heckling on your behalf) as you watch the live stream via the online player, which you'll be able to find at http://player.microsoftpdc.com
Make sure to check out the session before mine ("Things I Wish I Knew about Building WP7 Apps" by Jaime Rodriguez) and all of the rest of the Windows Phone 7 track. There's other great content at PDC that's worth checking out, but we all know that that's secondary!
See you there!
I'm working on a WP7 library which helps analyze your VisualTree and to provide a visual aid, I take WriteableBitmap snaps of the elements. Unfortunately I (seemingly) randomly encounter the following exception:
A first chance exception of type 'System.Exception' occurred in System.Windows.dll
What's going on?
You guessed it - this isn't random! In fact, this only happens on completely obscured (or off screen) elements which have never had a chance to render. In this case when you try to take a WriteableBitmap snap, instead of it forcing the control to render, it simply fails. This will hit you in the case of any element that has always been obscured. As soon as the element is unobscured it will be good to go (so you could do some VisualTree manipulation if you *really* needed to grab that shot).
... as opposed to multiple apps, each with a different locale.
Happy App Hubbing!
YES! Visit: http://create.msdn.com/en-us/home/getting_started and click "Install Now" to download the tools, directly, for free, without the need to sign up first.
Ever since the release of the new developer portal (http://create.msdn.com) I've been hearing that you need to signup to get the tools, hence they must no longer be free. In reality, what happened is that the old developer website url redirects directly to a login screen, instead of to the new site, leading people to believe that the tools are no longer free. Let me assure you - they are :)