What is Nbear

Nbear is a software development Framework class library based on. Net 2.0, c#2.0 Open all source code. Nbear's design goal is to make the most of the effort to reduce the developer's workload and maximize development efficiency, while balancing performance and scalability.

Open source protocol: BSD.

The origin of the name Nbear

N represents. Net, and it also means that no;bear can be translated into bears and tolerated.

Although the bear is the kind of looking silly, but the attack is "agile", so. Net Bear represents nbear is a rapid development framework based on. NET2.0, for Agile development.

The development of most of our projects requires too much unnecessary duplication and cumbersome configuration of the bear. such as data persistence, object pooling, URL redirection in web development, input validation, client script, and so on, Nbear provides you with a number of flexible tools and components to simplify the use of many common components , in order to simplify cumbersome configuration (especially for nhibernate such as the cumbersome configuration file format of such ORM components, high learning curve, and maintenance updates when nightmare requirements change), Nbear provides you with a 0 configuration of data access (persisted) interfaces and rechargeable components.

Therefore, Nbear also represents no bear, fully utilized. Net2.0 many new technologies generic, Emit, HttpModule and so on, nbear let us not (NO) endure (bear) this kind of cumbersome shackles, greatly improve our software development efficiency, demand changes in response to efficiency, you will notice that, While the amount of code you need to beat is getting smaller and less, Nbear will also bring you many elegant and efficient development experiences.

What kind of program is nbear suitable to develop?

The core of nbear includes a generic, strongly typed data persistence interface, a set of interface-entity definition components, high-performance Xml/json serialization support, a service factory, distributed service queues, and Web Components, so:

1. Nbear is most suitable for developing all kinds of web programs which are based on ASP.net 2.0 and have higher performance requirements. The combination of JSON serialization and XML serialization will make it easier and more efficient to interact with your server and client data; The Nbear.web component provides a number of components that accelerate web development and will enable you to base your standard ASP. NET way of development efficiency greatly improved; At the same time, Easy-to-use, performance-focused, generic persistence support will allow you to focus more on business development without the performance problems and cumbersome configuration needs of the traditional ORM Persistence framework (nbear requires little configuration and performance comparable to Daab).

2. High-performance XML and JSON serialization support and flexible and efficient persistence support also enable nbear to facilitate the development of various types of distributed applications based on Remote Data interchange (Web Service, remoting, etc.).

3. Built-in service factories based on IOC containers and distributed service queues enable your programs to have good scalability, can be completely transparent to set a common framework of the program as a distributed program, not even need to modify the consumer side or the service implementation segment of any code, based on the Service factory system is a natural SOA architecture , which allows your system to be consolidated with minimal cost and other SOA architectures.

4. For desktop applications, Nbear is also a little learning curve (how many people will carefully study the Hibernate reference manual for a small calendar program?) ), a practical and efficient data persistence scheme.

Feature List

· O/R mapping eliminates the need for configuration files, making full use of naming conventions

• Interface entity class definition, simple and clear, easy to describe system

• Provides entity class generation tools to exempt handwriting entities from work

• Dynamic entity class factory, Run-time dynamic emit and cache entity class interface implementation class

• High Performance entity class XML and JSON serialization

• Extensible, persistent database source support based on provider mode

• Support for multiple database sources

• Strong-type entity persistence based on paradigm and data access interface

• Container-based distributed service factories, transparent distributed service invocation and distribution

• Distributed service queues based on. Net Remoting

• Extended asp.net MasterPage, Pae, UserControl base class

• Ajax support based on user controls

· URL Rewrite support

• Common UI Controls