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.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
Like this:
http://www.premiumpixels.com/freebies/apple-iphone-chat-bubbles-psd/
I have a tcp/ip chat application, I used listbox, but its not the best solution...
As you are programming with the default set of Visual Studio (C#, .NET, winforms) I expect that you also use the defaulted listbox, meaning that that one uses defaulted .
This component can be overridden (even to use customized resources like images, fonts, etc.) It is even documented on MSDN:
ListBox.DrawItem Event
If I were you, I'd look into that example provided there!
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'm new to WPF and MVVM pattern. I've been reading about it and I come to a little doubt.
I'll build an WPF application that mainly does access to a database (oracle), but this access is done by an WebService (DataService). My question is in the Model part.
Should I create a class to each table on the database, on my Model, or should I just use the entities that the service provides me?
My guess is use the entities of the service, and then just do the CRUD operations in my application. But I want your opinion.
Thanks in advance.
It is always a good practice to use your own Models. That way, if the Service changes the structure, you will only need to change one point (where you map the item to your own entity), else you would have to change your whole application
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.
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.