Spring.NET Framework

Spring .NET Framework

Sprint.NET is an application framework focussed on helping build enterprise .NET apps. It provides a wide range of functionality such as Dependency Injection, Aspect Oriented Programming (AOP), data access abstractions, and ASP.NET integration.

Enterprise applications typically are composed of a number of a variety of physical tiers and within each tier functionality is often split into functional layers. The business service layer, uses objects in the data access layer to fulfill a usecase.

The .NET platform provides a wealth of functionality for architecting and building applications, ranging all the way from the very basic building blocks of primitive types and classes, to rich full-featured application servers and web frameworks.

Design patterns such as Factory, Abstract Factory, Builder, Decorator, and Service Locator have widespread recognition and acceptance within the software development.

The IoC component of the Sprint framework addresses the enterprise concern of taking the classes, objects, and services that are to compose an application, by providing a formalized means of composing these various disparate components into a fully working application ready for use.

The Spring.Core library is the most fundamental part of the framework, and provides Dependency Injection functionality. Most of the libraries in the Spring.NET distribution depend upon and extend the functionality provided by this core library.

The Spring.Aop library provides Aspect Oriented Programming(AOP) support to business objects. The Spring.AOP library complements the IoC container in the Spring.Core library to provide a rock-solid foundation for building enterprise applications and applying services to business objects declaratively.

The Spring.Web library extends ASP.NET by adding a variety of features such as Dependency Injection for ASP.NET pages, Bidirectional data binding, Master pages for ASP.NET 1.1 and improved localization support.

The Spring.Services library lets you expose any "normal" object as an enterprise (COM+) service or remoting object. .NET webservices get additional configuration flexibility with support for dependency injection and overriding of attribute metadata.

The Spring.Data library provides a Data Access Layer abstraction that can be used across a variety of data acess providers, from ADO.NET to various ORM providers. It also contains a ADO.NET abstraction layer that removes the need for tedious coding and declarative transaction management for ADO.NET

The Spring.ORM library provides integration layers for popular object relational mapping libraries. This provides functionality such as support for declarative transaction management.

Wanna know more...? documentation