I have seen a lot of questions about properties of WPF, and essentially every answer says that this bee The knees are, but essentially, each answer also talks about many things like XAMML, in which in many cases graphic designers and expression blends are included. My question is, are you in a single encoder working in C #?
Specifically, I do not have any graphic designers, nor have any great talent in that area; I do not use point-and-click tools; I write everything in C #, XML not
Winforms work fine in those situations, whether this is true of WPF, or it is found that important tasks can only be done in XAMML, default settings are not intended for real use and Should you be a graphic designer on the team so that things look good, etc., and would anyone be better in my position to stick Winforms?
Short answer : Yes, you can only do WPF with code Are there.
Long answer : About a designer, the part is capable of working on UI, and a developer on functionality is actually a side effect of the presentation of the decoding functionality
The WPF brings to the table in a powerful way, which is data-binding so that you can use a wide range of design patterns. Much has been discussed.
- To encourage the conference on configuration, you are allowed to write fewer codes to meet the same goal.
- This decoupling also has the good side effect of making your application more testable (you do not want to test if you do not want to, but the least option is there).
Will be moved from WinForms to WPF, you will be able to develop it for new development. You can do in principle that you are doing with WinForms (with only the new libraries), but it gives you the option of incorporating new tools into your development, because you are more comfortable with technology.
If you have not already seen it, then Scott Henslmann is very interesting.
Comments
Post a Comment