Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
There are two ways to create a form in c# application:
Add a new class describing form elements and behavior
Generate it all dynamically.
Q : What are the advantages of the second method?
Which can give more performance or reduce memory using and how about scalability?
Static UI should be your first choice. Dynamic UI is an option to consider, but only if you have a compelling reason. If you don't have a concrete reason to look for dynamic UI, and just have a vague feeling that one might be better then the other, then stick to static UI.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I am curious when there is a correct time to use the attribute [Obsolete] and the time to just delete the code. Is this something that should be considered in certain patterns like Factory vs Builder? Thanks!
You should use it in situations where there is code that is not under your control that consumes your class and you want to make a public API change and discourage or block future usage of the old API method/property without breaking binary compatability.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I have a simple layout
What would the best way to achieve this? using WPF or Win forms with a custom list view?
You could use WPF with Styles and Templates.
Please notice there is a difference between ControlTemplates and DataTemplates, even though you can sometimes use either one for a given goal, only in slightly different ways.
It would be easier for you to use WPF to mimic this. As you can style almost anything. While in WinForm you would have to handle the drawing yourself.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am working in a company that wants to make a CMS program.
I say that the UI layer should be written with MVC but they say that MVP is better.
I dont know which one is good for this project or any other.
What do you think?
And they want to use WPF.
How do you think about WPF in a web project like this?
Thank you all.
Go to beside your management and say "be satisfy"
MVC is better thing.. :)
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Assuming I was writing my own version of .Net :)
What would be the downside of such a setup?
Yes, I am talking about a new anti-pattern here to avoid creating endless tuples and EventArgs. I think such a setup would have made coding a lot cleaner.
No. The Tag property has history, it was important in VB6 and Winforms was meant to replace it. It needed to be added to make porting code relatively simple.
It is entirely unnecessary in .NET. It supports implementation inheritance, a feature that VB6 didn't have. So if you want to add extra properties then you just derive a class and add them. And you'll be able to give them a good name and a type so you don't have to cast every time you read the property. This works just as well with Winforms controls.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I have two features: one that presents the details of a single entity (EntityX) and one that allows the user to view a list of all EntityXs.
Using MVP, is it better to have an EntityXController with two methods (View and List, for example) that use the appropriate View and List views, or should I comply with my interpretation of the SRP and create an EntityXListController and an EntityXViewController to narrow the responsibilities of each?
That sounds more like same Model, different View-Presenter for Details, and another View-Presenter for List.