A WPF Application question:

Question

0.00/5 (No votes)

See more:

Hello all,

I am actually looking the main advantages between WPF and WinForm application style.

I have already implemented an MDI WinForm application and I would like if such MDI application can also be implemented in WPF style.
Here are my current investigations:

1. Windows Forms Multiple Document Interface (MDI) features to WPF:

This is not a standard feature in WPF and I found Codeplex provides
MDI Functionality to cover it (http://wpfmdi.codeplex.com).

I have also found Actipro WPF Studio which is a bundled suite of professional user interface controls and components for Windows Presentation Foundation (WPF) but I would like to know your feedbacks about this controls/components suite?

2. Using ActiveX OLE Control on WPF MDI child window:

To play with ActiveX control, like for example a 2d chart control, we need first to define on the WPF form a WindowsFormsHost container. This container will contain standard WinForm where we can place our activeX control.

This where I have a question about developping application with WPF if we have to use WinForm anyway to include ActiveX control.  Why not developping directly a WinForm MDI application, this will reduce the overhead?  Could somebody confirm this ? Is there an easier way to use ActiveX control on WPF ?

Please let me know if there two points can be covered differently.

Thank you very much in advanced.
Best regards.
MiQi.

Posted 20-Dec-10 1:44am

SuperMiQi

Add a Solution

Comments

johannesnestler 20-Dec-10 9:30am

In my last project I did the opposite of your 2nd point.
I developed a WinForms app and used a WPF-HostControl to render the "fancy" GUI-Parts. So I could use my existing WinForms assets.
Knowing both worlds I'd say it depends on your problem domain which way to go, but when I'm looking back now, my WPF projects seem so easy to develop. If UI is not important Forms is OK, but when you want to do a more polished UI WPF is great (especially if you work together with a designer)

SuperMiQi 20-Dec-10 10:49am

Hello Johan,

Thank you for you reply.

I would like to clarify your comment about ActiveX on WPF form.

Let's say I develop the MDI main application with WinForm window style, if I decide to encapsulate a WPF user control, will I use the DirectX drawing technilogoy or will this be routed to GDI+?

As I have lot of 3rd parties ActiveX controls, maybe do I have to use as you mentionend and then open a way for WPF Mdi Child form ?

What do you think ?

Thank you in advanced.
MiQi.

johannesnestler 21-Dec-10 7:19am

Hi MiQi,

I would base my decision on the assets I have. If you have a working application template - why change?
This was the main reason for me hosting the WPF content in a Forms App also influenced by the first paragraph here:
http://msdn.microsoft.com/en-us/library/ms742215.aspx

Maybe this helps you too:

http://www.simple-talk.com/dotnet/.net-framework/mixing-wpf-and-winforms/

http://blogs.msdn.com/b/scoberry/archive/2006/09/01/735844.aspx

About the performance:

I can only say I was satisfied - the WPF content was rendered as fast as in a normal WPF app. But I'm not shure about the internals. Fist I had a Problem with loading time of Forms but I solved it like this:

http://www.jaylee.org/post/2009/08/09/On-the-Startup-Performance-of-a-WPF-ElementHost-in-Winforms.aspx

Best luck with your app!

Johannes

SuperMiQi 21-Dec-10 8:40am

Hello Johan,

Thank you so much with your hints.

Have a nice day.

Best regards.
MiQi.

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)