Projects

glue

What is Glue?Glue is a simple framework for creating clean, elegant applications on .NET or mono. Glue consists of a number of libraries to provide you with the basic infrastructure for your application: logging, configuration, plus sane and simple data access. For web applications, you can ... [More] either go the ASP.NET way or choose Glue-Web to create a nice and easy web application the MVC (model-view-controller) way. See http://www.glueproject.com / Glue is sponsored by Grondwerk.it Download the latest sources from http://glue.googlecode.com/files/Glue-src-1.2.1.zip Take a look at the documentation (a work in progress). [Less]

nettiers

Overview.netTiers is a set of open source code generation templates that simplify the tasks of creating customized application tiers for your Microsoft .NET applications in just a few minutes. .netTiers utilizes the power of the best code generation tool available today, CodeSmith. .netTiers ... [More] generated architecture is custom to your domain, uses familiar patterns, and follows the guidance of Microsoft's recommended patterns and practices. In fact, the .netTiers base architecture is built upon the Microsoft Enterprise Library Application Blocks. DownloadsYou may download a checked version of .netTiers by clicking on the downloads tab above. If you are interested in using a nightly build then please visit the nightly builds page. DocumentationAll documentation for .netTiers can be found here. If the documentation is out dated please update the wiki or create an issue and we will see that it is updated. System RequirementsVisual Studio 2005+ CodeSmith 3.2+ Microsoft SQL Server 2000+ (Other DB's with limited support depending on provider) Microsoft .NET 2.0+ Enterprise Library 2.0+ (Optional, Recommended) nUnit or Visual Studio Team System (Optional) [Less]

prawks

Prawks is a library that allows you to express parameterized SQL and stored procedures as managed code functions (in C# or Visual Basic) using Microsoft's .NET Framework. Like Platform Invoke (P/Invoke), Prawks allows one to call stored procedures and parameterized SQL in a database by defining ... [More] a compatible method definition and signature in managed code. Prawks does not rely on templates or scriptable code generators. Instead, it simply makes use of the innovative features of the Common Language Runtime (CLR) like metadata, reflection services, custom attributes and dynamic code emission to implement the boilerplate data access front. [Less]

csharpsqltools

A set of utilities for working with SQL Server in C#, including a full schema reader, some code generation stuff for a very complex data access layer, and unit testing tools. Also, there are few other misc utility classes for enumerating a list of sql servers on the network, creating connection strings, and also a Win Forms connect to db form.

dal4net

Capa de Abstracion de datos para .NET

simpledal

QuickDALSimpleDAL is a colection of interfaces, generic (template) classes for easy access to data stored databases, files, etc. Every time I have to design and implement any desktop and web application, I have to implements a short of classes for database operations. This is well known as Data ... [More] Access Layer (DAL). Because of this, the goal of simpleDAL is to facilitate generation of entity DB classes. The programmer will need define its classes, inheriting from simpleDAL specialization template class, only specifying the database table fields and then, the SimpleDAL framework will provide the rest of functions for reading and writing data from/to databases. BackgroundMy initial goal was divide into separate and independant layers the entire database access, like logic fields, data collection and database read/write, but, at the moment, I was not able to separate, because data and IO layers always go together. Data can be responsible for host data object and IO can be responsible for create sql sentences and read/write from/to database, but then , IO must know how to access to data object, a responsibility of data layer. StructureBecause of I propose a schema where we have four layers for programmer: Interface layerThree main interfaces defining basic access, data management and input/output. Template (generic) base layerWhich implements basic and commond methods with abstract (mustinherit) class. Specialization but yet template class layerConcrete data object and input/output. For example, EntitySQL which implements data object with Data.DataTable and IO throw SQL Server with sql sentences. Programmer layerConcrete classes defined by the programmer that inherits from one specialization template class. Then next image may help: (coming soon) [Less]