Microsoft Enterprise Library 3.1 for Web and Windows

While developing any application, We first frame the application architecture i.e dividing the application into different modules or sub projects. There are several predefined application architecture.
But the application architecture should be based on the type of application what we are developing.
Very common application architecture is
0. Data access layer
1. Business Logic
2. Web Service Layer
3. UI Layer
4. Common Layer

The main purpose of Data access layer is same for all application i.e doing CRUD ( Create, Read, Update, Delete) operations. This Enterprise Library will provide blocks to achieve this functionality.

The Enterprise Library is a collection of application blocks intended for use by developers who build complex, enterprise-level applications. These applications are typically deployed widely and have interdependencies with other application and systems.
The Enterprise Library 3.1 release contains the following application blocks:

1. Caching Application Block: Developers can use this application block to incorporate a local cache in their applications.
2. Cryptography Application Block: Developers can use this application block to incorporate hashing and symmetric encryption in their applications.
3. Data Access Application Block: Developers can use this application block to incorporate standard database functionality in their applications.
4. Exception Handling Application Block: Developers and policy makers can use this application block to create a consistent strategy for processing exceptions that occur throughout the architectural layers of enterprise applications.
5. Logging Application Block: Developers can use this application block to include standard logging functionality in their applications.
6. Security Application Block: Developers can use this application block to incorporate authorization and security caching functionality in their applications.
7. Validation Application Block: Developers can use this application block to create validation rules for business objects that can be used across different layers of their applications.
8. Policy Injection Application Block: Developers can use this application block to implement interception policies that can be used to streamline the implementation of common features, such as logging, caching, exception handling, and validation, across an application.

Mostly i used Security, Exception Handling, Data Access, Logging. In my future articles i will provide how to use these blocks on Web and Windows applications.

Thanks to My Parents, Teachers and Friends

మాతృదేవో భవ
పితృదేవో భవ
ఆచార్యదేవో భవ
అతిధిదేవో భవ
I am starting this blog by thanking my parents, teachers and friends.

Ajax Libraries

Ajax a commonly used word web technologies. Ajax's core based purly javascript web calls i.e A request will be made from the javascript using XMLHTTPRequest Object. But it involves a lot of javascript coding.
Developers are lazy (Me too) so try to get the things done ASAP with less work. So mainly concentrated on the Javascript libraries for Ajax. Some of the libraries which i want share are

Ajax .NET Professional: This is developed by Micharl Schwartz as a tool primarily used to simplify the data transport mechanism that enables a client javascript routine to communicate with a server program. The source code is available and the package is free.

DoJo: The DoJo toolkit is a client-side library for AJAX developement without ties to any server technology. DoJo has a type system for Javascript and a function for binding script to events from javascript objects or DHTML elements.

Prototype: Prototype script library does not target any server technology for integration. It has a type system for scripting in a more object-priented way along with some shortcut syntaxes for dealing with javascript arrays as well as accessing and manipulating HTML elements on the page.

Ajax.NET: This is an extension for the microsoft web technology ASP.NET 2.0 and integrated part of ASP.NET 3.0 or above.