Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p><strong>Short answer</strong>: is yes, you can do WPF with code only.</p> <p><strong>Longer answer</strong>: The part about a designer being able to work on the UI and a developer on functionality is really just a side-effect of decoupling functionality from presentation. </p> <p>What WPF brings to the table in a powerful way is data-binding which enables you to use wider range of design patterns. <a href="http://msdn.microsoft.com/en-us/magazine/dd419663.aspx" rel="nofollow noreferrer">MVVM</a> has been discussed quite a bit <a href="https://stackoverflow.com/questions/tagged?tagnames=mvvm&amp;sort=votes&amp;pagesize=15">recently</a>.</p> <ul> <li>The various <a href="https://stackoverflow.com/questions/1409553/what-framework-for-mvvm-should-i-use">MVVM framework</a> encourage convention over configuration allowing you to write less code to accomplish the same goals. </li> <li>This decoupling also has the nice side effect of making your application more testable (you don't have to write tests if you don't want to, but at least the option is there).</li> </ul> <p>Moving to WPF from WinForms will most likely be worth it for you for new development. You could in theory keep doing what you've been doing with WinForms (just with new libraries), but it gives you the option to incorporate newer tools into your development as you become more comfortable with technology.</p> <p><em>If you haven't seen it already, the <a href="http://www.hanselman.com/blog/CategoryView.aspx?category=BabySmash" rel="nofollow noreferrer">BabySmash series</a> by Scott Hanselman is pretty interesting.</em></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