Windows Forms and Object Orientation

Question

0.00/5 (No votes)

See more:

Hi. I am a big fun of object oriented programming. I have been using Java in the past. And I used to make fully object oriented console applications. Now, I am using C# to create Windows Forms application. But I'm finding it hard to make a clean object oriented programming. Everything seems to be coded right into the form. And this is not a good practice, as I know.

Some one told me to use User Control along Windows forms to make a clean and more flexible coding but it seems there are few things written about this even on MSDN.

Any useful link on how to design user interface that adheres to object oriented programming principles in C#?

Thanks in advance.

Posted 2-Jul-10 1:00am

Bezawit

Add a Solution

1 solution

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)

Christian Graus · Accepted Answer · 2010-07-02T01:08:00

C# is, by definition, always OO. But, it's up to you to write good code, same as it was in Java. If you put all your code inside your form, then it's not very OO. If you create business logic classes, then you can factor things out in a more orderly fashion. There's no need to create user controls unless you need a custom control, or to group several controls together into a single control for reuse.