Title: No head, no tail - project development notes
Keywords: distributed development C # project division
November 19: In the afternoon, the weather is not cold stomach pain
From essential .......... I don't know what C # is improved than Java. How good more on the propaganda materials or on the website, the book bought from the bookstore and did not see anything special place. They are all inheritance inheritance. Take advantage of it, make it out in Dongdong.
Then the morning wrote. I want to first let's talk about the enterprise-class distributed template for C #.
The following understanding is that I have forgotten the understanding of who's example, maybe the MICROSOFT's pet store example, perhaps the project written by others. The brothers who are not right can refer to.
C #'s enterprise-class template will generate the seven projects below:
DataAccessProjects
Data connection part. That is, our company discussed the DO layer known in it. Data Object. I think the principle of this layer is very simple, that is, in addition to here, other places do not have to write SQL statements directly. Or the method of directly calling the stored procedure. There is nothing to say, come and go to the middle of the other system.data.
2. BusinessFacadeProjects
OK, this layer is more interesting, I have been discussing this layer with the colleagues of the brothers. What is the difference between this layer and the following rules layer. (Don't joke Luo). There are still some twists and turns. At first we used the English version of VS.NET, then we were noisy every day. For example, I thought this layer was a package of business rules, so the basic data operation should be placed here. For example, new, modifications, and delete of basic information. It is only when it is necessary to determine whether the delete operation can be done when deleting. It will only generate a class in the Rules layer to determine. Or if there is anything to use bo. Anyway, I was confused. Later, one day, after we got a Chinese version, suddenly found this Facade called business appearance layer. So, all business can't do it here. Instead, all the operations of Doo are encapsulated in this. The FACADE layer is really a (business appearance)
3. BusinessRulesProjects
This layer is a true business object, that is, the corresponding BO in the three-layer structure is placed in this place.
4. SystemFrameworksProjects
This layer is placed is a system object, comparing a unified package for security processing. (This part is not used in the beginning, and then puts the unified process of the Application and Session at the unified processing of the corresponding object of the Application and Session when using the Web Service, not placed in the Web Service layer.)
5. WebServiceProjects
Nothing, the web service file is placed.
6. Webuiprojects
Places place the ASP.NET file.
7. Winuiprojects
Winform placed place.
This is the structure of automatically generated enterprise distributed applications. Initially, we have very poor understanding of this stuff. I feel that this simple thing is complicated. Experience some benefits in slow development. I don't say a specific benefit first. First, some ideas I have experienced with everyone:
l Why can you write this program?
I think this is too simple, and the technology of hardware is progressing. Ha, hardware progress allows programmers to write programs from the head. If you have written 100 sentences before you write 1000 skills, you will think that you are a master, but now you can find out that the example of C # can find that the execution of a judgment statement may have to pass more than ten levels of inheritance. transfer. Are everyone who is a low hand? The code that the programmer to write is relatively small. The code to be written can be reduced if the code written is not intended to perform less than before. (In order to submit a modification of a table of databases, my program calls nearly ten classes to implement. If it is before, it must be killed.) L Why write the program like this
This problem is a problem that is difficult to answer. But the initial idea is actually the high efficiency of this development in the development of efficiency. I am not very clear about how to make a system for a few weeks, but it is indeed possible to use this way to make people division of division of labor, and the transformation of the development process. This is more troublesome. Looking back :)
l If this method is just a stage of software engineering development, what will be next?
Very Clear. The next phase must be a large number of programmers to be unemployed. Do you want to change your name. What is the architect, an analyst.
l What should I do?
do not know. Work hard (write here, I really don't know what to do in the future.)
The next section writes some of our projects to the enterprise template. These transformation I think it is also based on some thinking about new technologies. . I hope everyone is interested.
