Write your own C # framework from scratch-Supplementary description of framework Learning

I am very grateful to xuanyuan for putting forward his views and opinions on this framework, so I will post them here to let everyone know.

The rapid development of this series refers to the fact that after the framework is built, it is very convenient to develop new functions on this basis. You can complete a large number of basic functions in a short time without writing too much code. Of course, if you paste all the Code directly, it may be easier to understand the example directly, but for many friends who want to know the entire framework implementation process, it is difficult to understand the original idea when there are too many codes at once. At the same time, we also see that each chapter will be attached with an independent solution, which is also the same. We will learn it step by step. I originally wanted to write more detailed chapters. However, due to the limited personal free time, it may be hard to understand why I suddenly pasted too much code and did not include many examples and instructions, thank you for your understanding.

Of course, for the convenience of later development, and more functions can be implemented, the logic layer and the UI Layer have a lot of functional encapsulation is inevitable. Generally, after the framework is completed, it will be handed over to those who have only one or two years of development experience for development and maintenance. Because the Code contains detailed comments and a lot of documentation instructions, and many development examples that will be discussed later, they will be able to get started in about one or two days to a week, you can quickly develop the desired functions. For example, you can add the corresponding content editing page to the page with so many functions in Advertisement Management in Chapter 1, generally, it takes less than one hour (mainly for the UI and painting controls). If you are skilled, the time is shorter, and there is very little code they actually need to write, the new and modified functions are also very convenient (this will be shown in the following example). This information is commonly returned after being used by my team.

Of course, from the perspective of the entire development process, it will be difficult, because you have not yet put it into practice, you can understand the entire framework more quickly only from some simple starting points in practice. So when you study it in the early stage, you should not just look at the code, so that you can hardly understand the idea. You need to write all the code in the editor as shown in the picture, at the same time, you don't have to worry too much about every function and algorithm. You just need to remember to have this function. When there are too many two or three chapters to implement the page function, you will know what is going on and how to operate it.

At the bottom layer, this part seems to have a lot of code. In fact, as long as you are familiar with a template generation class function, other classes will be fully understood, because every generated class is similar. For classes or functions that you do not know, you can first mention them. I will add special comments to these areas in the future and post them in the following articles to explain why this operation is necessary.

For both the data layer and the logic layer, because templates are used for implementation, any modifications or changes to the database are generated with one click, and mature templates are provided as examples, most of the new features can be developed simply by modifying the example, which is very convenient. There are indeed a lot of redundant code, and you may have thought about re-encapsulating and merging. However, because templates are generated, there is not much free time at the same time, therefore, many functions are too lazy to encapsulate and process them. They all generate issues that do not affect development efficiency and subsequent upgrade and maintenance... try again later

The UI Layer involves security, verification, and other aspects, so the architecture features are complicated. If you cannot understand this part, you can skip it first, you can directly view the subsequent implementation part and learn from the simple part. (because all the functions you want are encapsulated, you only need to call them. The operation is too simple, haha) it's easier to learn from ease to difficulty. It's much easier to look back at this part later.

Finally, I would like to thank you for your reply and reminders. I will add some examples or image descriptions later to explain how to use a function or function in more detail, at the same time, I hope to give more comments and make progress together.

 

 

 

 

Copyright:

This article was originally published by AllEmpty and published in the blog Park. You are welcome to repost it. You must keep this statement without your consent and provide the original article link clearly on the article page,Otherwise, the right to pursue legal liability is reserved.. If you have any questions, you can use1654937@qq.comThank you very much for contacting me.

 

 

 

As long as you are interested in learning and making progress together, you can add Q group: 327360708 to this topic.

 

 

For more information, please refer to blog: http://www.cnblogs.com/EmptyFS/