See intro blogpost here.
Well technically this is not a WPF vs Silverlight post, but a SL vs WP7, but it still kinda belongs in this series.
Generally the differences in the API’s between Browser Silverlight and Windows Phone Silverlight are pretty slim. However dealing with the phone can be quite different anyway. First there’s often less security restrictions on the phone to worry about. Secondly there’s a lot of phone specific APIs like sensor data, camera, contacts etc). The screen is also smaller so often some controls doesn’t make sense to have on the phone, or needs to have a separate layout to enhance the experience on this small touch-centric screen. Lastly (and very importantly) the small amount of memory, processing power and battery life means that performance is a concern. This often forces you to go down a slightly different avenue for your application, and for certain custom controls.
For the API differences I’m again going to be cheap and just point you to the main resource on MSDN that has some really good info on that matter:
Other notable things:
- In Silverlight for Windows Phone, effects such as Blur and DropShadow are not supported.
- Custom pixel shaders are not supported, so the PixelShader type is not supported.
- Isolated storage on Windows Phone does not enforce quotas to restrict the size of isolated storage for Silverlight-based applications. The default quota size of 1 MB does not apply. (however there’s still a 2Gb limit on Isolated Storage for WP7, or less if you run out of space).
- Manipulation events that Silverlight doesn’t have (well technically they are there but throw a not supported exception), are the same as in WPF, so WP7 has better touch closer to WPF than Silverlight.
Next: WPF vs. Silverlight - Part 11– Silverlight on Phone vs. Browser