Asp.Net Code Jet

CREATED RELEASE: Asynchronous Page in ASP.NET 2.0 (Apr 09, 2008)

Wed, 09 Apr 2008 08:10:40 GMT

There are few cases in current web applications, where it involves long running operations. For instance, a system admin uploads 1 gig of data in the system, which will be processed by the system for 30-40 minutes to be splitted and putted properly in the database system, as well as notifying other system user regarding the availability if data.

In the traditional approach of web application, the user has to wait for the whole time until the whole process needs to be completed. The modern age of web application includes a technique where the user doesn't required to be wait to complete the whole process with the current page, where as they can move on other page (or even can close the browser) or if they resides on that page the system will show a simple progress bar , which stops when the data processing (or the long running operation) completes. The corresponding technique that implies this usability feature is using an asynchronous model.

Before the asp.net 2.0 ages, creating an asynchronous model was very complex and time consuming along with several over-heads. ASP.NET 2.0 comes with a new nice feature, where we can declare and use a page easily in asynchronous style. Besides the easy implementation model, ASP.NET asynchronous page utilizes ASP.NET threads efficiently. While calling a long running database query or web service, at the moment the request reaches at the asynchronous point, the corresponding asynchronous operation starts without keeping the current ASP.NET allocated, and thus lets the thread to be returned back to the thread pool. As soon as the asynchronous process completes, another ASP.NET thread get allocated and continues accordingly. This model really improves the utilization of ASP.NET thread pool and thus improves the scalability of the corresponding web applications.

To make a web page asynchronous, we just have to put a property in the page directive as follows:

<%@ Page Async="true" ...

There are two different implementation model for ASP.NET 2.0 asynchronous pages, with respect to database and web-service call.

Implementation model for database

The implementation model for database query requires a "PageAsyncTask" class to be set with few event handler methods such as "Begin Event Handler", "End Event Handler", "Timeout Event Handler" etc. This task should be registered as an Asynchronous tasks to continue and complete the asynchronous scenario properly.

Implementation model for web service

The implementation model for web service call is much more simpler than the database query. Ii just includes creating an web service instance, followed by calling the MethodName"Async" (for instance, if the web method name is "HelloWorld" then its asynchronous method name is "HelloWorldAsync". Besides the calling the asynchronous method for a web service method, we can register it's complete event handler to perform some post completion tasks.

CREATED RELEASE: Simple C Sharp Delegate Sample (Apr 09, 2008)

Wed, 09 Apr 2008 08:04:07 GMT

New developers often ask me about C# delegate, as they got a bit confused about the basic concept and specially maximum of the reference contains and discussed from an advanced view. Well I think delegate is really simple, when you grab it's basic idea.

So what is delegate?

Basically it is similar like the old "C" age function pointer, where functions can be assigned like a variable and called in the run time based on dynamic conditions. C# delegate is the smarter version of function pointer which helps software architects a lot, specially while utilizing design patterns.

At first, a delegate is defined with a specific signature (return type, parameter type and order etc). To invoke a delegate object, one or more methods are required with the EXACT same signature. A delegate object is first created similar like a class object created. The delegate object will basically hold a reference of a function. The function will then can be called via the delegate object.

UPDATED WIKI: Home

joycsc — Wed, 09 Apr 2008 07:55:55 GMT

This is a resource home where software architect Mohammad Ashraful Alam provided few of his coding samples demonstrating best practices and solutions with regarding real world problems while developing web applications. All of the coding samples provided here are considering asp.net and sql server technology.

CREATED RELEASE: Performance Benchmark Framework (v1.0) (Apr 09, 2008)

Wed, 09 Apr 2008 07:52:54 GMT

Performance is a one of the basic requirements in the most of the current trend of web applications. While designing software architecture, there are several technologies kept available for the designers. Among these available options, some of techniques may includes multiple solutions, combining of those can create a case, where the basic performance output can't be determined based on the common sense and/or in depth knowledge on the corresponding topics. In short, based upon different options the software architect needs to determine the appropriate object model which fits best with the current application requirement.

Check: [url:http://geekswithblogs.net/joycsharp/archive/2007/11/22/117042.aspx] for details.

CREATED RELEASE: Role based security with cookie (v1.0) (Apr 09, 2008)

Wed, 09 Apr 2008 07:48:35 GMT

Authentication and authorization is the two basic part of the user-end security in asp.net web applications. After to successful authentication of a user, authorization takes the place according to which the authenticated user are allowed to access to the corresponding resources in the web application.

Role based security is very basic requirements in the current trend of web applications. Mostly there are two roles involved, which are registered user and the admin users. However in a web application a user can have multiple roles which can be authorized on page and page control level. Today we'll check a basic sample which includes page based authorizations for specific roles.

To implement the basic role based security, there are three points to be considered. In this example we are considering two different roles "member" and "admin". There are two separate folders named "member", which can be accessed by any logged in user, including admin users and "admin", where only the user who contains the "admin" role can access the child resources (page, images etc).

1. Defining the authorization regions in web.config

The following xml tags are required to be added under the "configuration" node of the web.config.

Defining security authorization for "member" users

<location path="member">
<system.web>
<authorization>
<deny users="?"/>
</authorization>
</system.web>
</location>

Defining security authorization for "admin" users

<location path="admin">
<system.web>
<authorization>
<allow roles="admin"/>
<deny users="*"/>
</authorization>
</system.web>
</location>

2. Authenticating the user

After the successful authentication, the following codes are required to establish the form based authentication for the corresponding user.

//Authenticating the user Identity.

System.Web.Security.FormsAuthentication.RedirectFromLoginPage("member1", this.CheckBox1.Checked);

3. Implementing the role based security

The "Application_AuthenticateRequest" event which was defined in the "Global.asax" file, will include the appropriate codes regarding the role info of the logged in user, which will be accesses each time for any web request in this web application. This can be done in either "cache" or "cookie" mechanism.

In this sample we have considered cookie based mechanism.

NOTE: This user sample doesn't include asp.net 2.0 membership and role provider.

UPDATED RELEASE: Role based security with caching (v1.0) (Apr 09, 2008)

Wed, 09 Apr 2008 07:45:32 GMT

Authentication and authorization is the two basic part of the user-end security in asp.net web applications. After to successful authentication of a user, authorization takes the place according to which the authenticated user are allowed to access to the corresponding resources in the web application.

Role based security is very basic requirements in the current trend of web applications. Mostly there are two roles involved, which are registered user and the admin users. However in a web application a user can have multiple roles which can be authorized on page and page control level. Today we'll check a basic sample which includes page based authorizations for specific roles.

To implement the basic role based security, there are three points to be considered. In this example we are considering two different roles "member" and "admin". There are two separate folders named "member", which can be accessed by any logged in user, including admin users and "admin", where only the user who contains the "admin" role can access the child resources (page, images etc).

1. Defining the authorization regions in web.config

The following xml tags are required to be added under the "configuration" node of the web.config.

Defining security authorization for "member" users

<location path="member">
<system.web>
<authorization>
<deny users="?"/>
</authorization>
</system.web>
</location>

Defining security authorization for "admin" users

<location path="admin">
<system.web>
<authorization>
<allow roles="admin"/>
<deny users="*"/>
</authorization>
</system.web>
</location>

2. Authenticating the user

After the successful authentication, the following codes are required to establish the form based authentication for the corresponding user.

//Authenticating the user Identity.

System.Web.Security.FormsAuthentication.RedirectFromLoginPage("member1", this.CheckBox1.Checked);

3. Implementing the role based security

The "Application_AuthenticateRequest" event which was defined in the "Global.asax" file, will include the appropriate codes regarding the role info of the logged in user, which will be accesses each time for any web request in this web application. This can be done in either "cache" or "cookie" mechanism.

In this sample we have considered cache based mechanism.

NOTE: This user sample doesn't include asp.net 2.0 membership and role provider.

UPDATED RELEASE: Role based security with caching (v1.0) (Apr 09, 2008)

Wed, 09 Apr 2008 07:43:24 GMT

Authentication and authorization is the two basic part of the user-end security in asp.net web applications. After to successful authentication of a user, authorization takes the place according to which the authenticated user are allowed to access to the corresponding resources in the web application.

Role based security is very basic requirements in the current trend of web applications. Mostly there are two roles involved, which are registered user and the admin users. However in a web application a user can have multiple roles which can be authorized on page and page control level. Today we'll check a basic sample which includes page based authorizations for specific roles.

To implement the basic role based security, there are three points to be considered. In this example we are considering two different roles "member" and "admin". There are two separate folders named "member", which can be accessed by any logged in user, including admin users and "admin", where only the user who contains the "admin" role can access the child resources (page, images etc).

1. Defining the authorization regions in web.config

The following xml tags are required to be added under the "configuration" node of the web.config.

Defining security authorization for "member" users

<location path="member">
<system.web>
<authorization>
<deny users="?"/>
</authorization>
</system.web>
</location>

Defining security authorization for "admin" users

<location path="admin">
<system.web>
<authorization>
<allow roles="admin"/>
<deny users="*"/>
</authorization>
</system.web>
</location>

2. Authenticating the user

After the successful authentication, the following codes are required to establish the form based authentication for the corresponding user.

//Authenticating the user Identity. System.Web.Security.FormsAuthentication.RedirectFromLoginPage("member1", this.CheckBox1.Checked);

3. Implementing the role based security

The "Application_AuthenticateRequest" event which was defined in the "Global.asax" file, will include the appropriate codes regarding the role info of the logged in user, which will be accesses each time for any web request in this web application. This can be done in either "cache" or "cookie" mechanism.

In this sample we have considered cache based mechanism.

NOTE: This user sample doesn't include asp.net 2.0 role provider.

CREATED RELEASE: Role based security with caching (v1.0) (Apr 09, 2008)

Wed, 09 Apr 2008 07:41:43 GMT

Authentication and authorization is the two basic part of the user-end security in asp.net web applications. After to successful authentication of a user, authorization takes the place according to which the authenticated user are allowed to access to the corresponding resources in the web application.

Role based security is very basic requirements in the current trend of web applications. Mostly there are two roles involved, which are registered user and the admin users. However in a web application a user can have multiple roles which can be authorized on page and page control level. Today we'll check a basic sample which includes page based authorizations for specific roles.

To implement the basic role based security, there are three points to be considered. In this example we are considering two different roles "member" and "admin". There are two separate folders named "member", which can be accessed by any logged in user, including admin users and "admin", where only the user who contains the "admin" role can access the child resources (page, images etc).

1. Defining the authorization regions in web.config

The following xml tags are required to be added under the "configuration" node of the web.config.

Defining security authorization for "member" users

<location path="member">
<system.web>
<authorization>
<deny users="?"/>
</authorization>
</system.web>
</location>
Defining security authorization for "admin" users

<location path="admin">
<system.web>
<authorization>
<allow roles="admin"/>
<deny users="*"/>
</authorization>
</system.web>
</location>
2. Authenticating the user

After the successful authentication, the following codes are required to establish the form based authentication for the corresponding user.

//Authenticating the user Identity. System.Web.Security.FormsAuthentication.RedirectFromLoginPage("member1", this.CheckBox1.Checked);3. Implementing the role based security

The "Application_AuthenticateRequest" event which was defined in the "Global.asax" file, will include the appropriate codes regarding the role info of the logged in user, which will be accesses each time for any web request in this web application. This can be done in either "cache" or "cookie" mechanism.

In this sample we have considered cache based mechanism.

NOTE: This user sample doesn't include asp.net 2.0 role provider.

CREATED RELEASE: A Client Script Helper Utility Class (v1.0) (Apr 09, 2008)

Wed, 09 Apr 2008 07:31:09 GMT

The "ClientScriptHelper" utility class will help you by not requiring you to remember the client side codes.

Using the "Add" method of "Attributes" property of ASP.NET web controls you can add client side functionalities (like showing message, print dialog, close browser, browser back, pop-up window etc) to your code. However, invoking the client side behaviors to the web controls, you have to remember the corresponding client script codes as well as each time you want to use that by adding the corresponding attribute. The "ClientScriptHelper" utility class will help you by not requiring you to remember the client side codes in this case.