[Best practices question] Web dev tapped to work on VS Windows Form app. Is there a common strategy in these apps that is analogous to the “Model View Controller” pattern for separating back, front, and interface code?

Pretty much the title. I'm trying to do a rewrite on some fairly lazy code someone did. There are a number of forms, and calls to backend actions seem to be sprinkled in wherever was most convenient at the time, functions added to the form's class just because that's where the scope was easiest, etc.

I'm going to do a quick rewrite and separate out the backend out into their own logical classes, but wondered if there was a common strategy for how to orchestrate the form classes (View in web dev), backend (Model), and overall logic glueing them together for different actions (Controller)

Thanks for any help!

by externalDialog via /r/csharp

Leave a Reply