DOTNET software development framework

DOTNET software development framework If the copyright is reprinted, please indicate the source. With my personal abilities, I do not have enough time and resources to develop a complete platform on my own. Select a number of outstanding projects for integration among many existing open-source projects. "Standing on the shoulders of giants" is Newton's sentence Famous saying . It is also suitable for our IT industry. My idea of the technical architecture of the Platform is to use the open-source ORM framework for the data persistence layer. Asp.net does not have a suitable web layer framework and is written in Asp.net code-behind mode. Code The connection between the data persistence layer and the WEB presentation layer adopts the IOC container. 1. Open-source framework Selection: both the data persistence layer nhib.pdf and ibatisnet are excellent data persistence layers. nhib.pdf is an excellent hibernate DOTNET porting version. Community Ibatisnet is a data mapper framework and a porting version of ibatis for Java. It is also a very popular tool in the open-source community of DOTNET. Nhib.pdf is used to support very good object-oriented design models, and ibatisnet is used to support applications Program The two frameworks have requirements for developers. In this way, it is more elastic. IOC containers spring. NET and Castle, which are two very good IOC containers of DOTNET. Spring. net is also a port version of spring in Java. The current version is 0.6, and Castle is a new IOC container under DOTNET. It has more functions than spring in terms of maturity. net is much better, and Castle is used in the framework. the final technical architecture of the platform is nhib.pdf/ibatisnet + Castle + ASP. net2. Architecture integration: Asp.net on the web layer is responsible for data input and output, responding to user events, and input validation. How can we obtain the Nhibernate session and ibatisnet sqlmapper on the web layer? In this architecture, Dao, service, Nhibernate session, and ibatisnet sqlmapper are all managed through Castle. How does the web layer obtain an instance of the castle IOC container? Here we use httpmodule to process it, use httpcontext. current. to save container instances, see http://www.tobinharris.com/nhibernateasp.aspx. The Asp.net page processes the business logic through the service. The service is responsible for the Use Case Logic, and the domain-related logic is delegated to the domain model for implementation. the Service uses Dao to persist the domain model. the Service manages database transactions and nhib1_session/ibatisnet sqlmapper. Domain model is responsible for displaying the data of the problem domain. Dao uses nhib.pdf/ibatisnet for persistent data and query. when implementing Dao, we use Castle's nhib.pdf/ibatisnet Dao support, which greatly simplifies the code. Many methods only use a simple line. This architecture has obvious advantages, clear layers, and clear responsibilities at each layer, which facilitates hierarchical design and development. Combining the IOC of mock and Castle, unit test is also very easy. in addition, the backend (Service, domain model and Dao) Code does not depend on the Asp.net framework. The same code can be used in Web apps or winform, and you only need to change the UI Layer. Linked http://www.castleproject.org/castle/show/HomePagehttp://nhibernate.sourceforge.net/ for frame tool used Http://sourceforge.net/projects/ibatisnet/ In addition, there is a wonderful articleArticle Application System Architecture Design