Building Asp_net Logical Component Library

Building Asp_net Logical Component Library
Profile
Use asp.net to develop highly reusable, loosely coupled, well framed Web applications. And can form a highly available component library.
Object
This article is mainly for the use of ASP. NET develops BS system developers, project managers, and leadership in charge of software quality.
Background and the way to solve it
Background, the characteristics of the application software: 1, the value of business, business complex, a lot of unique customer requirements, many versions, some companies for each customer to produce a new version, very few people understand the differences between all versions, so many versions of the company's heavy burden, 2, product function coupling is serious, function is difficult to reuse, 3, Software modification task is heavy, perhaps this is the most frustrating, a project after the development, customers continue to make changes, many developers in the long-term into the change task. These characteristics and problems make the company development department like Snowball roll the bigger and heavier, the workload is more and more heavy.
Way to solve the problem:
For the above problems, application software development can solve the problem using the following methods:
1, the extraction component, enhances the reuse.
2, interface change skin, easy to modify, the interface is changeable.
3, the script passes the parameter, avoids the coupling.

Content
Framework: Includes page, component library, data component library, data component factory four parts. The page is responsible for the overall appearance of the site and loading the component library, the component library provides the logical function, the Data component library provides the business data, the data component factory is responsible for generating the data object. These four parts can be summed up as two library two ties. The page is the link between the component library and the user, and the data component factory is the link of component library and data component.

1, page
The page is responsible for the overall appearance of the site and loads the widget library.
Page is the overall UI performance of the site, the main work is the picture production, page cutting, loading components, and to pass parameters to the component, and responsible for site navigation.
Division of Labor: Art and skilled HTML personnel development.

2. Component Library
This is the core of the framework, and we use the user control to easily and quickly complete these 3 points:
1, the extraction component, enhances the reuse.
2, interface change skin, easy to modify, the interface is changeable.
3, the script passes the parameter, avoids the coupling.
1. Extract artifacts to improve reuse.
The processing of a certain logic functions packaged into user control, which is easy, mainly how to reuse, generally we are mainly in the same project using user control, but only across the project to achieve reuse, in fact, Codebihand technology is an inheritance relationship, the user interface inherits from class library, So the user control's class library is referenced to the project, and the user control's ascx code is placed in the directory under the project, and it can be like using a user control in the same project.
In addition, if you need to debug, you can put the source code into the user control directory to track debugging.