Reduce your ADO.NET code to the minimum

SqlNetFramework introduction

SqlNetFramework simplifies the development of ADO.NET database applications. Applications using the SqlNetFramework can reduce operations such as reading data for displaying, creating a dataset for in-memory management, and executing a SQL text-inline SQL/stored procedure command to just a single line of .NET code. SqlNetFramework lets you build ASP.NET and WinForms database applications using any CLR compliant language, such as C# or VB.NET. Applications developed with SqlNetFramework can run on desktops and web servers. SqlNetFramework is an alternative to the Microsoft Data Access Application Block (MS DAAB) for applications that want to boost developer productivity by reducing the quantity of .NET code that they need to write to create a ADO.NET database application to the minimum.

SqlNetFramework video - View a brief demostration about how easy is to develop ADO.NET database applications using the SqlNetFramework.

Download SqlNetFrameworkStartingVideo.wmv (8min - 2MB)

Who needs SqlNetFramework?

Developers building an ADO.NET database application for the .NET framework. SqlNetFramework was designed to boost developer productivity by reducing the quantity of .NET code needed to create a ADO.NET database application to the minimum.

SqlNetFramework benefits

SqlNetFramework reduces more code than the Microsoft Data Access Application Block. If you have develop ADO.NET database applications using the Microsoft Data Access Application Block you will find that the SqlNetFramework is easier to use than the MS DAAB and it reduces more lines of dot net code than the MS DAAB. The SqlNetFramework is an alternative to the MS DAAB (show me code sample).
No more hard coded/embedded SQL in your ASPX web forms. The SqlDataSource control is a very easy to use control but it is not used by many developers because it adds SQL code directly in the markup of ASPX web forms and it doesn't promote SQL reutilization. The SqlStoreDataSource control solves this problem because the SqlStoreDataSource control doesn’t add SQL code in the markup of ASPX web forms and is as easy to use as the SqlDataSource control. The SqlStoreDataSource control is an alternative to the SqlDataSource control (show me code sample).
Reduce ADO.NET code to the minimum. You can execute a SQL text-inline SQL/stored procedure command with just a single line of code if your SQL text-inline SQL/stored procedure command doesn’t require parameters (show me code sample).
Isolate your SQL code from your application code (No hard code SQL). When developing ADO.NET database applications using the SqlNetFramework you will never see hard code SQL in your application code. The SQL code is isolated in an independent storage (e.g. XML, database). It allows you minimize changes in the application code because of database changes. For example, if you were using a XML file to store your SQL code and you would need to migrate your database server from Microsoft SQL Server to Oracle you would need to change the SQL code in the XML with the new Oracle syntax; otherwise, if your SQL code would be hard coded in your application code you would need to make changes in all the files that would contain SQL code. Currently with the Microsoft Data Access Application Block your need to hard-code your SQL code in your data access layer (show me code sample).
Write portable SQL code across multiple .NET applications. The SqlNetFramework allows you to create a database of SQL code by isolating your SQL code in an independent storage (e.g. XML, database). It allows you reuse your SQL code in any application type (e.g. WebForms, WinForms) supported by the SqlNetFramework by only attaching your SQL code database to your application and calling the SqlNetFramework API to execute your SQL code (show me code sample).
Write generic ADO.NET code - data provider independent. When you are developing ADO.NET database applications you need to add specific-type references corresponding to the database with which you are working with (e.g. SqlCommand, OracleCommand, OleDbCommand, etc). When using the SqlNetFramework to develop ADO.NET database applications you will only make reference to the SqlNetFramework namespace and classes, no references to a specific data provider are needed. It allows you to write ADO.NET database applications that can be easily portable from database vendor because they are independent from the data provider that you are using. You will never need to use a specific parameter name format (e.g. @ParameterName, :ParameterName) when passing the parameter values used to execute a SQL text-inline SQL/stored procedure, you only need to specify the parameter name without a specific database format (e.g. ParameterName). Currently with the Microsoft Data Access Application Block you need to specify the parameter names with the format defined by the data provider that you were using (show me code sample).
Easy to use. If you have already use the Microsoft Data Access Application Block you know that in order to execute a database operation you only need to call the methods in the Database class. In the same way to execute a database operation using the SqlNetFramework you only need to call the methods in the DbManager class.
GUI SqlEditor application. SqlNetFramework allows you to create your SQL statements and its parameters, if any, using our SqlEditor application at design-time. You don’t need to create code (hard-code) for each parameter as you do now with the Microsoft Data Access Application Block (show me snapshot).
XCopy deployment. Deploy the SqlNetFramework is as easy as just copy the SqlNetFramework assemblies to your application binary directory.
Partially trusted shared hosting is no problem. Most of the web hosting grants you a medium trust security level to run your ASP.NET web applications. The SqlNetFramework can run with a medium trust security level.
Royalty-free distribution. You as developer need to buy a license to develop your ADO.NET database applications but your customers don't need to buy a license.