Projects tagged ‘access’, ‘code’, and ‘generation’

AutoProc (The Stored Procedure Generator) is a (simple to use and compatible across multiple editions) set of stored procedures which generates getter and setter procedures for complex Sql Server ... [More] 2000/2005/2008 (Express/Workgroup/Standard/Enterprise/Developer) tables. [Less]

No designers No massive unreadable code files Having been frustrated with clunky designers and unmanageable code generation in commercial .NET O/R mappers, I have decided to give up on them. My ... [More] vision for this project is a simple code file generation class library driven by an administration GUI as a separate Winform application. It will use an easy to understand factory pattern. Files will be kept very small and easy to manage, and best of all, there will be no designer and impossible to read five thousand line long xml or C# code files. The idea of this project is simple. In one click, take a database and generate a simple, maintainable data access layer that just works. All default CRUD operations will be generated using LINQ. There will be no possibility of designer files becoming corrupt and wiping out your O/R Mappings while you try to find that one character in that 5000 line long XML configuration to fix it. Simple is better, but if developers need more flexibility, a series of extension classes will be available to build on top of the core data access layer. I never want a developer to have to touch the core for any reason. It will be a one click operation to build a data access layer for a small application, but it will have the ability to be customized for complex applications as well. I plan to port the functionality as a visual studio plug-in down the road. [Less]

Framework for RAD against relational database (and xml), using a sophisticated, easy-to-use OO model (3-tier). Supports multiple database platforms. Uses generics and partial classes. Supports ADO ... [More] transactions (doesnt require MSDTC). Includes a winforms Class Generatator for auto [Less]

Based on Enterprise Library 3.1, DAEE enables developers to access databases faster and safer. DAEE supports multiple database sources including ACCESS/ SQLSERVER2000/ SQLSERVER2005/ ODBC/ ORACLE/ ... [More] EXCEL etc. You can configure connection strings in WEB.CONFIG/ APP.CONFIG through Microsoft Enterprise Library Configuration Tool. DAEE have many other features, including the following ones: 1. Enabling operations crossing multiple databases at the same time. 2. Supporting executions of multiple operations with a transaction. 3. Supporting pagination of single table operation, skip of specific records (only SQLSERVER2005 is available now). 4. High security level, preventing from SQL Injection Attack. 5. Other features. System Requirements * Supported Operating Systems: Windows Server 2003; Windows Vista; Windows XP Note: If you already have the Enterprise Library 3.0 installed, you must uninstall it before installing the Enterprise Library 3.1. However, you can install the Enterprise Library 3.0 or the Enterprise Library 3.1 when 2.0 is already installed. * Microsoft .NET Framework 2.0 or 3.0. You need .NET Framework 3.0 for the Application Block Software Factory and the WCF adapters for the Validation Application Block and Exception Handling Application Block * Microsoft Visual Studio 2005 development system (any of the following editions): o Microsoft Visual Studio 2005 Standard Edition o Microsoft Visual Studio 2005 Professional Edition o Microsoft Visual Studio 2005 Team Edition for Software Developers o Microsoft Visual Studio 2005 Team Edition for Software Testers o Microsoft Visual Studio 2005 Team Edition for Software Architects o Microsoft Visual Studio 2005 Team Suite * To use the Application Block Software Factory and the Strong-Naming Guidance Package, you need the Guidance Automation Extensions (GAX). To modify these guidance packages, you also need the Guidance [Less]

Generate your CRUD Stored procedures. Write your own custom stored procedrues. Now, generate generate a complete data access layer that is Data Bindable.

Given an Entity Data Model XML (EDMX), this utility generates valid IDataReaders across all entity types, allowing Linq to Entities (L2E) to be used in legacy systems that require this interface to be ... [More] implemented. The generated IDataReaders are strongly-typed and performant. [Less]