Framework Plan essay I. Background and vision, Framework Plan essay vision

Framework Plan essay I. Background and vision, Framework Plan essay vision

It has been 11 years since I registered my blog. In fact, I forgot how I registered my blog. Afterwards, I never remembered writing my own blog.

Recently, I am working on my own architecture plans, and I am gradually guiding the back-up for coding, and I plan to write my own. net-based ORM, IOC components, MVC, and so on.

Of course, this text is not a formal article, but a record of recent research and analysis.

Knowledge Background:

Early access to. net, written architecture is the traditional three-tier, data access is directly used ADO. NET, enterprise lab, and some tools similar to code generator based on this.

Later work was interspersed with winform, java, and DBA work.

In recent years, in addition to writing server-side code, we have been working on front-end development for most of the time, and the JS Code volume is also more than 10 million lines.

The most widely used ORM is Ibatis.net, and the IOC component uses MEF and spring.net. Because. net skill tree is a bit messy, so I plan to sort it out recently. while compiling my own architecture demo, I try to use the native C # method, compile commonly used frameworks and components at various levels.

Plan:

In the first stage, build a framework demo with a framework or component that has not been used or is rarely used. The self-constraint is as follows:

1. Try not to use the following frameworks or components: Enterprise Library, * batis, MEF, spring.net, and nhib.pdf

2. Reduce the use of configuration files

3. Frame priority

4. Select open-source frameworks and components as much as possible and require rich community resources.

5. Set up the server framework first, and then proceed to the front-end.

The second stage explains the source code of the framework and components used.

1. Write research notes for source code analysis

2. Try to reproduce it in your own way

3. Modify the source code to adapt to various problems encountered in the demo.

In the third stage, all self-compiled components and frameworks are used to re-build the entire development framework.

1. In addition to native language methods, third-party components and frameworks are not used.

2. Try to move the previous project to the new development framework, and do not fully implement the business logic, but only perform regular use verification and verification of a small number of complex businesses.

3. fast development and multi-person collaboration

4. Compile relevant documents and scripts

5. Try to promote the framework or find a solution for verification