Are WinForms gonna Die?

Question

2.00/5 (3 votes)

See more:

VS2012

Well I was just googling and Found out a lot of queries regarding Microsoft abandoning WinForms and moving to WPF and HTML5/CSS/JS as alternatives.

So is this true , i mean i am shocked to see that , is Microsoft really gonna move upto WPF and leave behind the WinForms. There are a really less no. of tutorials available on the Internet for WPF and for WinForms there are a ton. So It is easier to learn WinForms.But After learning this , Should i too abandon learning WinForm programming and devote my time to WPF?

Posted 25-Sep-13 3:41am

Abhinav Gauniyal

Updated 25-Sep-13 5:50am

Richard MacCutchan

v2

Add a Solution

Comments

Mike Meinz 25-Sep-13 9:43am

Not anytime soon.

See Future of Windows Forms

See What is the future of WPF?

Abhinav Gauniyal 25-Sep-13 9:58am

The person who posted this and i have same thoughts regarding the problem , but the more i read , the more i realize that WinForms are being abandoned.

Mike Meinz 25-Sep-13 10:02am

Maybe, yes, a long, long time from now. Worrying about it now means you lose the productivity benefit of using Windows Forms now. Wait until necessary and better tools for WPF will be available or Microsoft will have decided on another direction like HTML5.

2 solutions

Solution 1

This isn't really a question we can answer in this format - it requires more of a discussion becasue there is no "right" answer.

I would suggest that you bring this up here: http://www.codeproject.com/Forums/1580229/General-Indian-Topics.aspx[^] becasue not only is it a better layout for a discussion, but it's also largely populated by people working in your industry in your country - so they will probably have a better "feel" for how developement is heading in India! :laugh:

Posted 25-Sep-13 3:44am

OriginalGriff

Comments

Abhinav Gauniyal 25-Sep-13 9:55am

They are just talking about onions :|

Abhinav Gauniyal 25-Sep-13 9:57am

But seriously , I do want to learn , and i was heading the right way , till i discovered that issue. So , Should i first clear my concepts of WinForms adn try to learn them the move to WPF or should i abandon WinForms and move onto WPF?

OriginalGriff 25-Sep-13 10:56am

Seriously - start a new message thread, and bring up the subject - they don't just talk about onions, sometimes they discuss cricket as well...

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Accepted Answer · 2013-09-25T06:56:00

Yoda wrote:
Clouded, this boy's future is.

You really need to use your own judgement. Who will want to take responsibility for leading or misleading you in such a shaky matter?

There are problems in both libraries. The problem with Forms is that they are based on the very obsolete and rusty Windows API and inherited a number of Windows problems. WPF is actually a brave step to get away from Windows. WPF has very little to do with Windows API as it is based on ActiveX, and only the main window obey some Windows API rules, while all inner elements don't use anything from Windows and don't use Windows message pumping. Did your hear about non-Windows Microsoft OS called "Singularity"? It is based on CLR build directly on top of the HAL, without the unmanaged layer. It works, and development of the possible Windows replacement based on Singularity technology (code name "Midory") was announced. There are other "pure-managed" OS projects, please see below. In principle, it would be a great boost for non-Windows APIs like WPF. However, we don't know any further plans. We know that many good project have been undertaken, and a lot of complete trash was successful on the market.

Please see:

Microsoft Singularity:
http://en.wikipedia.org/wiki/Singularity_%28operating_system%29[^],
http://research.microsoft.com/en-us/projects/singularity/[^];

Cosmos:
http://en.wikipedia.org/wiki/Cosmos_%28operating_system%29[^],
http://cosmos.codeplex.com/[^];

SharpOS:
http://en.wikipedia.org/wiki/SharpOS_%28operating_system%29[^],
http://www.sharpos.org/[^];

ETH Zurich — Microsoft Research Barrelfish:
http://en.wikipedia.org/wiki/Barrelfish[^],
http://www.barrelfish.org/[^].

Microsoft Midori (code name):
http://en.wikipedia.org/wiki/Midori_%28operating_system%29[^].

So, think by yourself. Nobody will guarantee anything.

[EDIT]

Practical advice? Sure. Learn both. And learn a lot more. You need wider look.

Afraid to waste of time? If you are going to be afraid of waste of time, it will lead to even greater waste of time. To minimize such waste of time, focus on fundamentals and also the aspects of technology and detail needed for your immediate work.

—SA