Recently in the government projects, this kind of project, originally not big, the main reason, is to take good business needs.

The main is the code TD screen, I code for a long time, has been like no way, the main reason, is to get a block of their own childhood without an integrity of cognition.

A lot of sporadic points, they have it as a sporadic point to do, the final result is that the point has been done to the end and scattered into a group.

It's not supposed to be like this!

Instead, the IOC and service in. NET should be integrated in the first place.

I used to think the service is a bit useless, now I am wrong, service still need to separate, because the code generator for a while to generate the service unit of the basic code, so finally go back to the road ...

was misled by himself.

The IOC and service in MVC should be clearly distinguished!

Finally, MO an administrative project self-feeling.

In fact, a project is nothing but the collation of data, there is a way to show, each point is what to do with, these should be considered clearly, they should be considered clearly in advance, List + status of the statistics + chart!

When filtering, first add the relevant role units, and then search is the state and time of the distinction

As for system-level user distinctions, these need to be judged with a uniform look

Recently in the government projects, this kind of project, originally not big, the main reason, is to take good business needs.