asp.net MVC was asked to be depressed. .

razorman

Go to the interview today, ask me, explain the three-tier structure
I said, "These three layers are the presentation layer, the business layer, and the data layer.
The presentation layer writes some user interfaces, the business layer writes the application business code, and the data layer writes what the database accesses. "

He said that I was wrong. There are many things in the real three-layer structure, which is not so simple.

How to explain mvc in the end? MVC is just to put the corresponding code in different places, isn't it enough ??? There are so many things?

azraelmoon

Almost the same.

razorman

No, he drew a picture for me, has three circles, represents these three layers, and then painted a lot next to these three circles. I have n’t heard anything about it. . how depressing. . .

shenmue024

He must be talking about the architecture of mvc

Microsoft's asp.net and java struct are based on this structure

Simply put, it is the module (business code), view (interface), and controller (related operations that handle http requests, such as Request.Response, etc.)
What I said may not be rigorous enough, you can search for standard answers online.

razorman

MVC architecture and three-tier structure are not the same thing? ? ? ? ? ? ? ? ? ? ?

Is it not the same thing at all, is still similar, is also different?

azraelmoon

Then I painted a lot next to these three circles

It is estimated to be a specific method.

saintfrosty

If you compare many control patterns in design patterns with .net delegation / event theory articles, you will understand that many of the models that look very deep actually rely on "control classes" to win points. If you take a break for each control class in the pattern with delegates / events, you will find that the pattern is actually very simple and there are not so many gimmicks.

saintfrosty

We have repeatedly emphasized that your code does not need to call the page mechanism under asp.net, it will call your code. You only need to assign the code to the most appropriate event according to your responsibilities, and do not force everything to do everything in one event (such as page_load).

As for the interface to be separated from business logic, I believe many people have this concept.

I think that if you understand the specific development framework, forget about the low-level framework of MVC, it is better than those who quarrel with MVC but invent MVC there all day.

saintfrosty

If I interview, I will ask "How does asp.net know to call the SelectChanged event of DropdownList without calling other events?", "How does WinForm program and asp.net program share business processing class library?" Talk about the specific and comprehensive questions as much as possible in the chat, and try not to ask the "how to explain MVC" question that is too loud and has only a little book concept.

开心花生

How does asp.net know to call the SelectChanged event of DropdownList without calling other events? "," How do WinForm programs and asp.net programs share business processing class libraries? ",

I don't know how to say these two?