Understandably some developers were a bit upset when they found out that their native Windows Mobile code couldn't be moved forward to Windows Phone 7. Their effort investment had essentially reached a dead end. While the decision to use Silverlight as a core technology for Windows Phone broght an end to the usefulness of some code it also opened the door for other existing code to become useful in the mobile space. I was playing with an accelerometer driven program that I had written and was working on making a desktop component that would let me visualize my recorded accelerometer data. I was using the Infragistic Silverlight Data Visualization Controls (version 9.2) for Silverlight 3. I couldn't help but think "Man, if I could use these controls on Windows Phone 7 then I wouldn't need to make a desktop component." Then I decided to try it. I made a simple chart in a Windows Phone 7 project and deployed it to both an emulator and a real device and to my surprise it worked!
I personally invested a lot more in managed code than I did native code and feel that it's nice to be able to share more of my desktop development knowledge with my mobile development activities. But I'm overjoyed to see that my Silverlight 3 investments extend into Windows Phone 7
Tags: Windows Phone