Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Well, from experience I can tell that some things won't work in Silverlight like they do in WPF. Some things I've encountered recently (although there are many more):</p> <ul> <li>Bindings don't work exactly like you want. For instance, in WPF by default your bound property changes on keyUp on a text field. In Silverlight that's not the case: it will update on Blur. Frameworks like Caliburn.Micro fix this by adding this implicitly.</li> <li>WPF has something called Adorners. These basically allow you to add small UI elements for things like resize, rotate, etc. Things you typically see in designers (drag to resize). You can make something like that in Silverlight, but it's a bit more complex.</li> <li>I'm not sure about WPF, but in Silverlight a call to a webservice is eventually done on the UI thread. You can set it up wherever you want, but the actual call and callback is done on the mainthread. Something to keep in mind when dealing with a result from a web call which might take a while to execute (someone can correct me on this if I'm wrong).</li> </ul> <p>I think the typical way you should work with a new application is start in Silverlight, and move to WPF if you really need to. Also, I've been told that it's slightly easier to port a Silverlight application to winRT/Metro, so that might be something you would want to check out.</p> <p><strong>Addition</strong> Here's a link from MSDN describing various differences: <a href="http://msdn.microsoft.com/en-us/library/cc903925%28v=vs.95%29.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/cc903925%28v=vs.95%29.aspx</a></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload