Is there any performance penalty if not using XAML to design WPF windows and controls ?

Question

0.00/5 (No votes)

See more:

I want to use only C# code to create all windows and controls dynamically at runtime of the application , I have many reasons why . But i am new to WPF and i want to know if there is any penalty doing it that way ? , May it cause any leaks/bugs or another issues ?

Posted 24-Feb-13 23:14pm

Member 8061245

Add a Solution

3 solutions

Solution 1

No, there's no runtime performance penalty as the XAML will just get turned into C# anyway by the XAML compiler. Not if you do it right.

But there will be a design time penalty as it will most likely take you longer to build your UIs.

Hope this helps,
Fredrik

Posted 24-Feb-13 23:55pm

Fredrik Bornander

Solution 3

Hi. If i was you , i mix two method.Because Using XAML in complex DataBinding Or DataTemplating that is very simple.in these situation if you work with C# your programming become tedious.
in my experience when i need create control dynamically such as create a table then i use C# code. and when i need create static control and layout their appearance by Style i prefer use XAML.
but it is good to know in very situation you need load UI before working with UI elements.
Choose yourself.
Good Luck.

Posted 25-Feb-13 0:18am

aliwpf

Updated 25-Feb-13 0:24am

v3

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)

V. · Accepted Answer · 2013-02-25T00:01:00

The more "dynamic" your code, the less performant, however this is mostly negligible unless you are doing some heavy stuff.
The way you design these dynamic controls (and how and when to load them) will be the determent factor here.

Memory leaks are very unlikely, bugs only if you develop them :-).

Quote:
another issues

Designing a good flow and stable dynamic creating and loading controls requires proper design. Don't jump into it too quickly. I also propose to keep stuff static as sort of a skeleton in which your dynamically created controls move. eg a mainwindow with fixed frames, a dialog with OK/Cancel buttons on which you place a user control depending on the usage, etc ...

Make sure to use "user controls" :-)

hope this helps.
good luck.