"WPF is old, can not eat"-say then said that the future of WPF This Life (ON): Fear

Microsoft recently released the latest WPF roadmap, a hot discussion; for the old control provider, this is an important opportunity for the WPF series of controls, and as a result, Spread studio for WPF products have made an important update and are released with Spread Studio 8.0. In view of this, choose to translate and organize a self-codeproject article: "is WPF dead:the present and the future of WPF", and talk about the programmer in the mind of WPF.

650) this.width=650; "Width=" "height=" "title=" style= "image" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none; "alt=" image "src=" http://images.cnitblog.com/blog/139239/201412/ 031206489513911.png "border=" 0 "/> 650) this.width=650;" Width= "" height= "[title="] ["]" image "style=" border:0px;p Adding-top:0px;padding-right:0px;padding-left:0px;background-image:none; "alt=" image "src=" http:// Images.cnitblog.com/blog/139239/201412/031206506708651.png "border=" 0 "/>

Introduction

As a veteran WPF programmer, the question that has been focused over the years is how the next client-side programming will go after Microsoft releases the latest WINRT framework.

Obviously I have good reason to worry about this, known as the halfway aground of Silverlight, it has caused great damage to downstream developers, as the saying goes: Once bitten, ten years afraid of twice shy. This is the true portrayal.

I've been devoting a lot of effort to WPF since 2009, using it to develop financial-related industry software, and now I'm still here, but the focus has shifted to training-related work. As a professional development and training instructor, the future of WPF is important to me, and this is the root knot of my deep thinking on this issue.

This article I will be in an objective and transparent way to share my findings and sentiment, hope to play a role in order to provide better prospects for the community of WPF.
In addition, at the end of this article, I will provide some strategic and personal insights for enterprise and personal development.

Have reason to worry

First, I'll show you the iconic signals I'm worried about, and if you're a WPF stakeholder, that's what you're worried about.

WPF Team Blog Break more

Like all Microsoft technical teams, the WPF team has its own blog, and the main topic is to share with the community the experiences of the members of the team within the WPF.
The last article of the blog, published three years ago in May 2011, or another precise statement, is when WINRT announces the start and as the next big goal.
A broken blog will imply a lot of questions, and I'm sorry to say that there is no good aspect: Maybe the team was downsized so that the blog was squeezed out of the task priority list, or perhaps the best team members had moved to other projects, such as WINRT; Perhaps this is the signal that the team is sending out to the community ...
From a public relations perspective, an active team blog is a very basic point, as it demonstrates the willingness of technology development and loyal development teams to proactively express their job satisfaction and share.
You may have noticed that Microsoft's MSDN blog is not actually active, with a few exceptions being the EntityFramework team blog, thanks to Rowan Miller, who regularly updates the blog post, And that's one of the main reasons I've always preferred this technology: it was developed by a talented team and a responsible team.

Official WPF Toolkit not updated

WPF Toolkit is an open source free project developed by the Microsoft team, with the goal of being an important auxiliary kit and outpost for WPF.

650) this.width=650; "Width=" 222 "height=" "title=" image "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none; "alt=" image "src=" http://images.cnitblog.com/blog/ 139239/201412/031206523731566.png "border=" 0 "/>
A very typical example of this is the DataGrid control, which was not in the initial release of WPF (WPF3.0 and WPF4.0), but in toolkit, and eventually WPF4.0 put it into the official release.
The official toolkit has been playing this role until 2010, but since the project began to good stopgap, there has been little focus on the release of the so-called next release.
The sign of inactivity is that the Google search engine's Toolkit of the keyword "WPF" puts the official Toolkit second, while the third party occupies the first (more detailed description in the second part of the article)

WPF no longer has a certification exam

The official WPF Certification exam (70-511) is not continuing and will expire in the summer of 2015.

650) this.width=650; "Width=" 244 "height=" 203 "title=" image "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none; "alt=" image "src=" http://images.cnitblog.com/blog/139239/201412/ 031206540614550.png "border=" 0 "/>
This gives developers a strong clear signal that the technology is not invested in, the corresponding can be considered to invest time and energy to WINRT, so that the certification exam will be rewarded.
Maybe someday Microsoft will delay the revocation of this certification exam, as they have done, and there will be compromises after receiving a lot of community developers, but inevitably, WPF is no longer important.
Personally, I have been hesitant to pass this certification exam because I can't guarantee time and value (yes, I pay for it myself). On the contrary, I firmly believe that we can prepare WINRT certification exam, because it will be effective in the future years.

Window 8+ system integration is no longer available

Recall that WPF4.0 released a lot of Windows 7 system-related integrations and enhancements, such as taskbar customization (pop-up list, progress, masking, etc...) ）。
But when WPF4.5 arrives, it does not fully integrate the Windows 8+ system functions, such as the sidebar (Charm bar), and most applications can only interact through interoperability.
As a result, Microsoft has not invested in these integration efforts, which clearly reveals that WPF is no longer a first-class citizen of the window system, in fact it is preferred to invest in WINRT's embrace, which the individual believes is a reasonable decision.

WPF does not support WINRT

Microsoft, the once-established software vendor, is now diversifying into a hardware vendor that mimics its competitors, Apple and Samsung.
Microsoft has bought Nokia in the hope of gaining a permanent seat in the mobile market.

650) this.width=650; "Width=" 244 "height=" 181 "title=" image "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none; "alt=" image "src=" http://images.cnitblog.com/blog/ 139239/201412/031206552803078.png "border=" 0 "/>
In the Tablet and notebook, Microsoft launched the Surface series to compete with Apple's ipad tablet and MacBook Pro notebook.
Surface generation and second generation are divided into two versions based on hardware architectures (x86 and ARM), which correspond to their own proprietary systems: Windows RT (not to be confused with WINRT as a software layer), but Windows RT does not support (at least officially unsupported) the old application interface. such as the excellent old-fashioned Win32 interface, and therefore does not support the "wrapper" on the basis of the derivative technology, such as WinForm and so on, of course, including WPF, and therefore cannot run the WPF application on the surface version.
The reason Microsoft is not investing here is simply that it wants to remove Win32 from the latest IT trends and replace it with tailor-made WINRT.

Complete Article series:

• WPF old, still can rice no--say then said the future of WPF This Life (ON): Fear

• WPF old, still can rice no-say then said the future of WPF (middle): strategy [Translate ...]

• WPF old, still can rice no--say then said the future of WPF This Life (bottom): Peace of mind [translate ...]

This article is from the "Grape City Control Technology Team Blog" blog, be sure to keep this source http://powertoolsteam.blog.51cto.com/2369428/1585868

"WPF is old, can not eat"-say then said that the future of WPF This Life (ON): Fear