Some architectural advice on various methods of using WinForms

I am reviewing my own code to see where I could have done things better.  I have built many dialogs which get an object passed in as a parameter, to the contructor.  Then in the Load function, I assign values to the various controls by accessing properties on the object.  Once the user closes the dialog, I read the contents of the control then pass the values to the properties of the object.

Using standard .NET Framework 2.0, what better ways are there for this interrelationship to exist?

How about .NET Framework 3.5?

And lastly, wouldn't the MVC Framework change this relationship fundamentally?  How does one use the MVC Framework with Windows, and would it still be with WinForms?  Is MFP a better choice with MVC?

Thanks for the help.  I'm trying to upgrade my skills to try and keep up with Microsoft!

newbiewebSr. Software EngineerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dude ytou are asking questions that require ansers that are far t long to be published in a forum such as this one.  I suggest that google for articles on the MVC and MVP patterns to get to understand the evolution from MVC to MVP.  I have however found the acronym MVC is very often being ued to refer to the MVP pattern.

Remember that MVC is a pattern and is equally applicable to windows or  As far as I know (I am not a web developer) the MVC Framework is Framwork developed to be used with

Their is however a site that promotes the use of one framework that can be used in and winform apps.  It has the added bonus (or not depending on who you ask) tat introduces some workflow type of functionality to the pattern.  Check out the link:
Bob LearnedCommented:
Where to start...

Hmmm...MVC with Windows forms...

1) Define a Form as a view with controls

2) Define as a "model" for the "real world" case.

3) Define a controller class that understands both the View and the Model.  It will attach to events in the View, and update the model, and attach to events in the model to update the view.

Simplified approach.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
newbiewebSr. Software EngineerAuthor Commented:
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.