NHibernate is a mature, open source object-relational mapper for the .NET framework. NHibernate is a port of Hibernate Core for Java to the .NET Framework. It handles persisting plain .NET objects to and from an underlying relational database. NHibernate supports transparent persistence, your object classes don't have to follow a restrictive programming model. Persistent classes do not need to implement any interface or inherit from a special base class. This makes it possible to design the business logic using plain .NET (CLR) objects and object-oriented idiom. Full Text Search. Cluster-scoped caching with Microsoft Velocity & Memcached. Business validation rules. ReSharper plugin. Castle Active Record. S#arp Architecture. And many more... 
 <UL><li>Natural programming model - NHibernate supports natural OO idiom; inheritance, polymorphism, composition and the .NET collections framework, including generic collections.</li></ul><ul style="text-align: justify;"><li>Native .NET - NHibernate API uses .NET conventions and idioms</li></ul><ul style="text-align: justify;"><li>Support for fine-grained object models - a rich variety of mappings for collections and dependent objects</li></ul><ul style="text-align: justify;"><li>No build-time bytecode enhancement - there's no extra code generation or bytecode processing steps in your build procedure</li></ul><ul style="text-align: justify;"><li>The query options - NHibernate addresses both sides of the problem; not only how to get objects into the database, but also how to get them out again</li></ul><ul style="text-align: justify;"><li>Custom SQL - specify the exact SQL that NHibernate should use to persist your objects. Stored procedures are supported on Microsoft SQL Server.</li></ul><ul style="text-align: justify;"><li>Support for "conversations" - NHibernate supports long-lived persistence contexts, detach/reattach of objects, and takes care of optimistic locking automatically</li></ul><ul style="text-align: justify;"></ul>

NHibernate is a mature, open source object-relational mapper for the .NET framework. NHibernate is a port of Hibernate Core for Java to the .NET Framework. It handles persisting plain .NET objects to and from an underlying relational database.

NHibernate - object-relational mapper for .NET

nHydrate is an object-relational mapping (ORM) solution for the Microsoft .NET platform providing a framework for a relational database to be mapped to .NET objects. It is designed to alleviate the software developers experience writing persistence domains. The model controls database generation, LINQ syntax, API, DAL, etc. The tool is entirely sited within Visual Studio.NET and all model maintenance and generation is handled directly from the environment. There are no XML files or other complex configuration scenarios to navigate like almost all other ORM tools. The VS.NET plugin GUI editor provides an interface to interact with a model and use it. Its features include: 
 <UL>
	<LI>Model Driven Architecture (MDA)</LI>
	<LI>Powerful code generation framework</LI>
	<LI>Visual Studio Integration</LI>
	<LI>Dependency Walking</LI>
	<LI>Persistence of 'dirty' (changed) data only</LI>
	<LI>Server-side paging</LI>
	<LI>In-memory filtering and sorting using LINQ</LI>
	<LI>Auditing Support</LI>
	<LI>Validation support</LI>
	<LI>Callbacks and Notifications</LI>
	<LI>Advanced lazy loading/load on demand</LI>
	<LI>Load objects with LINQ syntax</LI>
	<LI>Support for aggregate functionality</LI>
	<LI>Concurrency Control Mechanism</LI>
	<LI>Dynamic SQL Support</LI>
 </UL>

nHydrate is an object-relational mapping (ORM) solution for the Microsoft .NET platform providing a framework for a relational database to be mapped to .NET objects. It is designed to alleviate the software developers experience writing persistence domains. The model controls database generation, LINQ syntax, API, DAL, etc.

nHydrate - Conceive, Model, Generate

SubSonic is A Super High-fidelity Batman Utility Belt that works up your Data Access (using Linq in 3.0), throws in some much-needed utility functions, and generally speeds along your dev cycle. You can code your objects the way you like (with some minor convention tweaks) and the SimpleRepository will save them for you. It will also create your database on the fly if you want, altering the schema as you change your object. If you like having to do as little as possible with your data access, ActiveRecord makes this very, very simple. You don't need to create a lot of extra objects or know how the guts of anything work. It's as simple as asking for a new object and calling a Save() method.

SubSonic is A Super High-fidelity Batman Utility Belt that works up your Data Access (using Linq in 3.0), throws in some much-needed utility functions, and generally speeds along your dev cycle.

SubSonic - Data access for .NET

Fluent, XML-less, compile safe, automated, convention-based mappings for NHibernate. Fluent NHibernate offers an alternative to NHibernate's standard XML mapping files. Rather than writing XML documents, you write mappings in strongly typed C# code. This allows for easy refactoring, improved readability and more concise code. Why replace HBM.XML? While the separation of code and XML is nice, it can lead to several undesirable situations.<ul><li> Due to XML not being evaluated by the compiler, you can rename properties in your classes that aren't updated in your mappings; in this situation, you wouldn't find out about the breakage until the mappings are parsed at runtime.
</li><li> XML is verbose; NHibernate has gradually reduced the mandatory XML elements, but you still can't escape the verbosity of XML.
</li><li> Repetitive mappings - NHibernate HBM mappings can become quite verbose if you find yourself specifying the same rules over again. For example if you need to ensure all <code>string</code> properties mustn't be nullable and should have a length of 1000, and all <code>int</code>s must have a default value of -1.
</li></ul>
How does Fluent NHibernate counter these issues? It does so by moving your mappings into actual code, so they're compiled along with the rest of your application; rename refactorings will alter your mappings just like they should, and the compiler will fail on any typos. As for the repetition, Fluent NHibernate has a conventional configuration system, where you can specify patterns for overriding naming conventions and many other things; you set how things should be named once, then Fluent NHibernate does the rest.
 Its feature includes:

 <ul>
	 <li> Auto mappings - where mappings are inferred from the design of your entities</li>
	 <li> Persistence specification testing - round-trip testing for your entities, without ever having to write a line of CRUD</li>
	 <li> Full application configuration with our Fluent configuration API</li>
	 <li> Database configuration - fluently configure your database in code</li>
 </ul>

Fluent, XML-less, compile safe, automated, convention-based mappings for NHibernate. Fluent NHibernate offers an alternative to NHibernate's standard XML mapping files. Rather than writing XML documents, you write mappings in strongly typed C# code. This allows for easy refactoring, improved readability and more concise code. 

Fluent NHibernate - Fluent mapping for model

Business Logic Toolkit is a set of components to simplify .NET application development. BLToolkit is provided as source code that you can use "as is" or customize for your applications. It is written in C# and compatible with .NET Framework 3.5 and 4.0. Source code location: <A HREF="http://code.google.com/p/bl-toolkit/" target="_blank">http://code.google.com/p/bl-toolkit/</A>

Business Logic Toolkit is a set of components to simplify .NET application development. BLToolkit is provided as source code that you can use "as is" or customize for your applications. It is written in C# and compatible with .NET Framework 3.5 and 4.0.

BL-Toolkit - Business Logic Toolkit for .NET

The Castle ActiveRecord project is an implementation of the ActiveRecord pattern for .NET. The ActiveRecord pattern consists on instance properties representing a record in the database, instance methods acting on that specific record and static methods acting on all records. Castle ActiveRecord is built on top of NHibernate, but its attribute-based mapping free the developer of writing XML for database-to-object mapping, which is needed when using NHibernate directly. With Castle ActiveRecord you won't have to learn NHibernate mapping schema to have a working data access layer in minutes. For most cases you won't need to deal with ISession and ISessionFactory. Castle ActiveRecord was built on top of NHibernate. It offers: 
 <UL>
	<LI>Fast development (it handles the mapping and infers as much as it can so you don't have to dig into documentation or deal with tons of xml files every time something changes on your schema)</LI>
	<LI>Predefined common methods like Create, Update, Save, Delete</LI>
	<LI>Easy to implement method like Find, FindAll, FindByName. (Predefined if you use ActiveRecordBase)</LI>
	<LI>Session and transaction scopes that abstracts the ISession offering a more natural idiom</LI>
 </UL>

The Castle ActiveRecord project is an implementation of the ActiveRecord pattern for .NET. The ActiveRecord pattern consists on instance properties representing a record in the database, instance methods acting on that specific record and static methods acting on all records. Castle ActiveRecord is built on top of NHibernate, but its attribute-based mapping free the developer of writing XML for database-to-object mapping, which is needed when using NHibernate directly.

ActiveRecord - ActiveRecord pattern for .NET

ScalikeJDBC is a tidy SQL-based DB access library for Scala developers. This library naturally wraps JDBC APIs and provides you easy-to-use and very flexible APIs. What’s more, QueryDSL makes your code type-safe and reusable.

ScalikeJDBC - SQL-based DB access library for Scala developers

The main strength of Vici CoolStorage is the ease of use. Most ORM tools still require a lot of unneeded code to accomplish basic data persistence tasks, but Vici CoolStorage is designed to relieve the programmer from these tedious and error-prone tasks, making it very intuitive to use.
<ul>
	<li>Supports SQL Server 2000/2005, MySQL, SQLite, MS Access and VistaDB. Other custom providers can be added.</li>
	<li>Full support for MonoTouch (using SQLite)</li>
	<li>Session-less and context-free database access</li>
	<li>Any existing relational data model can be mapped to CoolStorage objects with minimal effort</li>
	<li>No code generator required. Mapping is done by creating simple classes.</li>
	<li>All relation types are supported: One-To-Many, Many-To-One and Many-To-Many</li>
	<li>Completely typed object model (no type casts required)</li>
	<li>Dirty tracking on the column level. Only changed fields are persisted to the database</li>
	<li>Full support for transactions, including ##TransactionScope##</li>
	<li>Nullable columns can be mapped to nullable fields or to a default value</li>
	<li>Delayed (lazy) loading of data to minimize database access. Configurable per field.</li>
	<li>Selective or automatic prefetching of all relation types for improved query performance</li>
	<li>Powerful and intuitive database-independent object query language</li>
	<li>Flexible event mechanism to intercept any event</li>
	<li>Identity (auto-increment) keys or sequences are supported for all database types</li>
	<li>Support for server and client generated Guid keys</li>
	<li>Objects can be mapped to different databases, even across object relations</li>
	<li>Paging of object collections (at server level)</li>
	<li>Extensive support for retrieving aggregate values on collections (count, sum, average, ...)</li>
	<li>Collections implement IBindingList so they can be used by controls (grids) as a data source</li>
	<li>Underlying database engine uses optimized and parameterized SQL queries. SQL injection is impossible</li>
	<li>Built specifically for .NET 2.0 and up, taking full advantage of generics and nullable types</li>
	<li>Raw SQL and/or stored procedures can be called on the underlying database without the need for a separate database connection</li>
	<li>Small footprint (less than 250 KB, including Vici Core)</li>
</ul>

The main strength of Vici CoolStorage is the ease of use. Most ORM tools still require a lot of unneeded code to accomplish basic data persistence tasks, but Vici CoolStorage is designed to relieve the programmer from these tedious and error-prone tasks, making it very intuitive to use.

Coolstorage - ORM library for .NET

The DatabaseObjects library is an open source tool for mapping relation database systems (MySQL, SQL Server, Microsoft Access) to an object-oriented structure. The library can simplify the development and maintenance of small and large systems by providing a mechanism to consolidate business logic, maintain data integrity, increasing productivity and minimise errors. The DatabaseObjects library contains a large set of powerful classes that interface to the underlying database system automatically generating the required SELECT, UPDATE, INSERT and DELETE commands. It also supports CREATE/ALTER TABLE, CREATE/ALTER INDEX, table joins, arithmetic expressions, aggregates, grouping, ordering, unions, support for all common data types and more. There are two versions of the library one for VB6 and .NET. Both versions support access to Microsoft Access, SQL Server, MySQL and Pervasive database systems.

The DatabaseObjects library is an open source tool for mapping relation database systems (MySQL, SQL Server, Microsoft Access) to an object-oriented structure. The library can simplify the development and maintenance of small and large systems by providing a mechanism to consolidate business logic, maintain data integrity, increasing productivity and minimise errors.

Database Objects - ORM in VB6

Discover open source projects across all platforms

Projects