BLINQ is a scaffolding tool, available from the ASP.NET Sandbox Platform.
In this post, I'll try to explain details about BLINQ, especially
- the idea
- architecture and code generation
- the webforms
- summary
Idea
With the command line tool BLINQ, you can generate a Web-Application on the basis of an exisiting database schema. The resulting application does allow managing the data: select, insert, update and deletes. The relations between the data are used for navigation purposes and for foreign-key lookups.
So the idea is not really idea, but powerful in combination with ASP.NET. Let's see....
BLINQ is an abbreviation for WeB Language INtegrated Query, according to the naming pattern BLOG (WeB LOG). LINQ, the upcomming technology for universal, next generation data access is responsible to query and save the data thru objects. More details about LINQ, you will find on Scott's Blog and inside the official Linq Project Page.
Architecture and Code Generation
(Click the image to enlarge)
Step 1:
BLINQ needs database schema metadata (what a surprise :-). With the LINQ May CTP, the command line tool SQLMetal is installed, which is internal used by BLINQ to generate the necessary information and general data access classes.
For example, you can call SQLMetal manually to get metadata as xml:
sqlmetal.exe /server:.\sql2k5 /database:northwind /xml:northwind.xml
The resulting file looks like this (this is just the fragment for the northwind category table):
An other way to call SQLMetal:
sqlmetal.exe /server:.\sql2k5 /database:northwind /xml:northwind.cs
The result is a complete data access via LINQ (here's an other fragment):
Step 2:
After generating the general data access thru SQLMetal, BLINQ does generate more specific methods to query and update the backend. These methods are located inside the file StaticMethods.cs. If you call BLINQ with the parameter /pageDataSource, this methods are generated direct into the code-beside files.
Step 3:
The last step: BLINQ does generate WebForms, according the meta informations. For each table inside the database, BLINQ does generate three forms:
- TableName.aspx
A list of all records (GridView) including sorting, paging, navigation, editing and deletes. - NewTableName.aspx
A single record view (DetailView) to add new data. - TableNameDetail.aspx
A single record view (DetailView) to edit the data.
As an other example, the northwind tables "Customers" and "Orders" (parent-child relation) are visualized here:
The resulting forms and navigation here (technical view):
WebForms
Here you can see Order Detail WebForm, generated by Blinq:
- Layout is styled via MasterPage and Theme
- Navigation does use Menu Control and SiteMap
- Breadcrump thru the SiteMapPath Control
- List with the GridView Control
- Single Record with the DetailView Control
- Business Object are accessed thru ObjectDataSource
- Page methods thru the new PageDataSource
This fact is great and brings the advantage, that we can use your existing skills and knowledge of ASP.NET to customize the generated forms. By just changing the theme a bit and by changing the Employee Dropdown Fields DisplayValue, you can get the following customized result:
Summary
The first BLINQ Preview is available since June 06.
Naturally, there are several features missing in the current version, e.g. :
- No validation inside Grid- and DetailView (e.g. required fields, validator according data type)
- No editors (e.g. for DateTime fields)
- No Ajax Support
- No Designer Support
- Limited templating
- "Just" SQLServer 2000, -2005, -2005 Express Support
Polita Paulus, THE BLINQ Developer, is an active poster at the BLINQ Forum. She is responsible for the GridView, DataView and FormView ASP.NET as well.
BLINQ is useful for
- prototyping
- web-based data-table administration
- as a starting point for more complex application
- learning ASP.NET 2.0
The combination "robust and complex Web Framework (= ASP.NET)" with "Code Generation" is powerful. I looking forward to the next release.
