WPF, Xaml and the Future of MS Development

Question

I am starting to invest heavily in WPF and wonder what more knowledgeable than me thought about the wisdom of this decision. Is there any way forward for WPF?

Answer 1

Yes, this is the way forward.

WPF and the use of XAML for interfaces have completely changed the way we develop interfaces for our customers. The possibilities are endless, the learning curve is large, but with dignity.

Now we can do something in XAML that we could not dream of doing 3 years ago with WinForms - or things that take up a few lines of code and an hour of logic that previously took a whole week of logic and four class files.

This is definitely a way to promote MS , but there will always be people using WinForms.

They even developed VS2010 with WPF, which should give it something, right ?;)

Answer 2

Microsoft has begun developing its enterprise applications in WPF. They invest in keeping this for themselves, not a reason to believe that the carpet will simply be pulled. In addition, WPF has a subset of Silverlight that doesn't seem to lose pairs.

Answer 3

XAML is a nice, declarative way to customize your interfaces with a lot of converting the values ​​you made for you, and the ability to add more backstage. However, you can separate it from WPF (although they usually go hand in hand).

I understand that .Net 4 has made some progress in using the XAML declarative language in the Workflow Foundation and in the Windows Communication Foundation, which will be interesting given that the two are already quite declaratively XML-driven.

So, XAML is definitely a way to move around MS, especially considering that it is basically nothing but a way to build a graph of objects — any graph of an object.

WPF is also going to take some steps - for example, to include the very skipped DataGrid (there are already great commercial alternatives) and more complex pixel shaders, which should put more effort into hardware and increase the speed of rendering and launching the WPF Application.

What about the future of WPF? Yes, for Windows-bound people who value stylus input and handwriting recognition and can find a place in their development budgets for attractive user interface development.

Against Flash, Flex, DHTML in general? I dont know. I am inclined to think not that most applications do not need the full strength of developing a fat client and do not care about pixel shaders, etc., happily trading them against the availability of the Internet.

Silverlight and XAML are not compatible with cross-compatibility, and WPF does not automatically go online. (Nevertheless?) Nevertheless, I took the gamble, and found that it was well spent time. If nothing else, this is fantastic for prototyping.