Do winform development front back-end separation mode, front end don't know what the back-end wrote, feeling a bit about how to programming?

CodePudding user response:

Products on foxconn workers, should know the working principle of the apple phone
He doesn't know the working principle of apple mobile phone, it is how to produce mobile phones,

Conclusion: they don't need to know what the back-end wrote, he need only according to the assembly diagram to assemble it,

CodePudding user response:

The building Lord asked: sure is WinForm isn't WebForm?

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

No, I do not expect WinForm,
WinForm design thought itself is vc + +, however, that s: new forms, controls, control the event code written,
WinForm this mode: code architecture separate coding space itself is not much, given the code separation, will only make the late maintenance worse,
I met a project, WinForm, is an open source project in a foreign country, on the basis of the total code line 20 w, code cow force (e) (xin) :
You to change the event behavior of a button, you have to jump a few dozen code files, compile all get 2 minutes,
You to add a form, you have to imitate his model, create dozens of class files,
I really don't think that to write some code is elegant, more do not think such good code maintenance, more do not think someone dared to take over such a code,

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

If you want to be with code architecture, or use WPF (WPF development pattern is a bit similar to Asp.Net - the MVC)
Such a code would be easy to separate,

CodePudding user response:

Interface for you call, tube behind him to write what, you're a UI
"

CodePudding user response:

Want to understand the principle, but some code and don't understand

CodePudding user response:

I don't think it's necessary points too thin, my habit is to use less than the function of the interface elements encapsulation, interface mainly call transfer, reaction operating results,

CodePudding user response:

Why should the front know wrote back end?
Don't you write the Web front end, also want to know what the back-end wrote?

CodePudding user response:

refer to 6th floor szjay response:

why front end to know what the back-end wrote?
Don't you write the Web front end, also want to know what the back-end wrote?

WinForm can end before and after the separation, such as make the RPC with WCF, before and after the end of the company good interface, and unified platform, also need not convert JSON/XML to transfer, more efficient,

CodePudding user response:

Want to just points ah, and the WEB are the same, not through the API and the back-end data interaction is finished,
Just too much stronger than the H5 WINFORM function, may be some originally the back-end I write this do things front-end himself the
Another use WINFORM, more optional communication protocol

CodePudding user response:

Just a matter of back-end provide interface

CodePudding user response:

As mentioned in # 8 concurrence

CodePudding user response:

refer to the eighth floor HHDDZZ response:

want to just points ah, and WEB are the same, not through the API and the back-end data interaction is finished,
Just too much stronger than the H5 WINFORM function, may be some originally the back-end I write this do things front-end himself the
Another use WINFORM, optional communication protocol more

Communication protocol to name a few