How to Convert WPF applications into Windows Form Application

No, not really because WPF and Windows Form Application handle their form differently from each other. You may have luck finding one of those Code converters, i have seen visual basic to c# and so on not a specific one for WPF to Windows Form. WPF is heavier on the graphics and therefore uses bit different methods to execute your code, it allows better design of the GUI while your regular windows form is unable to do what WPF can. However your code can still be executed but you have to physically create new project using windows form and paste your code to over.

Posted 1-Jul-15 15:25pm

Silver13

Comments

sreeyush sudhakaran 4-Aug-15 3:34am

See Here : http://stackoverflow.com/questions/5008082/convert-xaml-wpf-window-to-winform

Solution 3

Converting WPF to WinForms is not trivial, there is certainly no automated way, and if you want to go back to .net 1.1 as well you'll lose a whole load of other features like generics etc, so it's not just the UI you'll be changing.

Posted 9-Aug-15 23:04pm

ambesh kumar

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)

Thomas Nielsen - getCore · Accepted Answer · 2015-04-09T20:31:00

That's not really a good idea.

But essentially you can reuse your code behind in most parts and will have to rewrite the UI. If you seperated logics from presentation you should already have a business layer and the change is not that difficult.

If you didn't and have a so-called fat client, i would recommend the step one is to identify everything with logics, data retrieval etc and move that to a library assembly at the very least (if not a seperate tier, which for logistics and updateability would be better,) once that is done, your UI is just presenting and interacting and the process of building the UI is pretty straight forward.

I dare say, though, that these years the process is normally in reverse the move to wpf which also, generally is something which is adviced against ;)
Zero value-adding pile of complexity.

But moving the logics to seperate anchoring will enable you to build another UI and easily maintain both platforms in the transcision phase.

hope that helps

How to Convert WPF applications into Windows Form Application

3 solutions

Solution 1

Solution 2

Solution 3

Add your solution here

Preview 0

Existing Members

...or Join us