What did you learn about VB. NET (6th)

1. UML diagram 2, three-tier architecture 3, sqlhelper 4, Configuration File 5, interface 6, design mode

Next I wrote a few articles, but the last design pattern was not mentioned. This article has been put on hold for a long time because there are some things that have been busy, so I am really sorry to send this article so late. Next, let's take a look at the last article in the series of. Net <IDC charging system personal reconstruction edition>, which is the design mode.

 

In fact, this article has been put on hold for a long time. I previously mentioned that this series of articles may not be so professional, because we use it relatively. net restructuring system is just moving towards a slightly more formal and standardized direction, therefore, my articles in this series focus on experience, feelings, difficulties encountered in the system process, and solutions. Therefore, the experts who are very professional will forgive me for a moment.

During the reconstruction of the personal version of the data room charging system, I used three-layer knock for the first time, and did not add design patterns, interfaces, and sqlhelper, after I typed it, I thought it was perfect, because I thought there were more rules to use VB for the first time. At that time, I knew it was far from the standard. At that time, I really felt that it was very easy to use VB for the first time. At that time, I simply realized the function to implement the function. Now it's different. I feel like I have used three layers to finish the work, although there are a lot of troubles and things seem complicated, after all, the division of work at each layer seems a lot of rules. You can use the layer-3 model to add the design mode to it, and use sqlhelper to know that it is still far from the standard. Fortunately, you don't have to worry about implementing the function when adding the design model. Now we can see that both the design mode and the design mode have advantages and disadvantages. The advantage of adding a design pattern after a layer-3 knock is that it is not so difficult to start with. After clarifying the responsibilities of each layer, it is easier to find out what to look for between the layers; at the same time, it seems easy to clear the logic with three layers first, so that you can break down the several difficulties to be implemented first with peace of mind, and then add a design pattern with peace of mind, without having to worry about implementing functions. However, the disadvantage is that this takes a long time, because after three layers are knocked out, the design mode is added, which is equivalent to re-reading the entire system. If we add all the three-tier architecture and design patterns at the beginning, the disadvantage is that it is difficult to start with. In fact, whatever the case, you will find that at the beginning, it's hard to start with. It's just that you add the design model and everything in the first place. It's hard to get started with everything, the eyes almost crawled. In this way, after figuring out the model and idea, the idea of the entire system is much clearer when several lines are laid out. In this way, you don't have to spend two times, the time consumed will be less. At the same time, however, it is quite difficult to consider how to implement the functions required by the system while adding design patterns. In short, both methods have advantages and disadvantages. They are really "difficult at the beginning of everything", but it is easy to figure out the business logic and find out how to find the business logic, just try to figure out the path. The same was true when I added the design mode. I suggest you read the book first when adding the design mode. If you can, you can try to add any design mode. Of course, I didn't do this because everyone was doing it and I heard what design patterns were added. So I went straight into the target and went to look at those design patterns. At that time, I felt very difficult, but fortunately,
It is very difficult to ask others where they don't understand.

In this way, my personal version of the data center billing system has come to an end. During this period of time, I was working together to check for missing information, consolidate the previous personal version, improve the previous missed knowledge points, and also look at how my companions completed their work, in addition, cooperation can train everyone's team collaboration capabilities, which is an opportunity for us.