Good OOP Desing in WinForm App

didn't think this fit into the other discussion boards so I thought this would be the most acceptable place to post these questions... I’m in the process of building a Windows app with C# and I’m cannot seem to find any detailed information on “good” OOP design… honestly. Basically, I’m having trouble determining how certain classes and forms “should” be designed. For example: 1. I assume I should separate the logic from the UI. I have a number of forms that have comboboxes that contain generic information such as a list of states or sales person names. What is the “best” way to do this, do I create a class, incorporate it in the form, etc… 2. The program is an order entry app so I have a one-to-many relationship between the order information and the items ordered. I thought about creating two classes one for the order and one for the item ordered. I assume I would have to create a collection of the items ordered class to populate the UI. Is this approach sound? Is there a standard way of creating these classes? Any help, examples, book ideas would be greatly appreciated. Regards, Andrew

I'm also building a Windows app (although with vb.net). OOP design is all about re-useability of code. In my app, i've got my classes for states, cities, and countries. What I do, is just load instantiated objects of those classes into the combobox, and have the Name display via the .tostring method. This way, I am able to keep my city state country logic contained within a class, but the UI part of it remains all on the form. My 'Demographic' classes assume nothing of how it is going to be used, wether it is a combobox, listbox text field or printed in a report. As for the one-to-many relationship, it sounds like you are on the right path. As for a standard way of creating classes, I do not believe there is one. Each class is specific to its needs. Hope this helps?

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Adam Erstelle22y ago
I'm also building a Windows app (although with vb.net). OOP design is all about re-useability of code. In my app, i've got my classes for states, cities, and countries. What I do, is just load instantiated objects of those classes into the combobox, and have the Name display via the .tostring method. This way, I am able to keep my city state country logic contained within a class, but the UI part of it remains all on the form. My 'Demographic' classes assume nothing of how it is going to be used, wether it is a combobox, listbox text field or printed in a report. As for the one-to-many relationship, it sounds like you are on the right path. As for a standard way of creating classes, I do not believe there is one. Each class is specific to its needs. Hope this helps?