Skip to main content

Dynamically Generating Images using ASP.NET Handler




Dynamically Generating Images using ASP.NET Handler





IIS by default looks for images in files system. But sometime we need to produce those images dynamically. We can either pre-generate those images or configure IIS to forward request to our ASP.NET application.

Create a class that implements IHttpHandler. One can do synchronous or asynchronous(IHttpAsyncHandler) processing. Implement IsReuseable property and ProcessRequest(HttpContext) method.

IsResuseable true means IHttpHandlerFactory will put this IHttpHandler in pool for later use to improve the performance,

     public class GetNameImage : IHttpHandler
    {

        public void ProcessRequest (HttpContext context)
        {
            Bitmap vImg = new Bitmap(300, 150);
            Graphics g = Graphics.FromImage(vImg);
          
            g.SmoothingMode = SmoothingMode.AntiAlias;
            g.Clear(Color.White);
          
            g.DrawString("Mubbasher Mukhtar",
                new Font("Arial", 18),
               
System.Drawing.Brushes.Black, new PointF(5, 5));
              
            context.Response.ContentType = "image/png";
            vImg.Save(context.Response.OutputStream, ImageFormat.Png);

            g.Dispose();
            vimg.Dispose();
        }
   
         public bool IsReusable
         {
            get
            {
                return true;
            }
        }
    }



Configuring IIS to forward Image requests to Aspnet_Isapi.dll:
IIS manager click virtual directory or web site | Directory tab | Click Configuration | Mapping tab | click Add.




Configuring ASP.NET to process Image Requests:
Put the following configuration in web.config:


Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...

Using ADO.NET Transaction Object, Saving CLR Objects and SqlNotificationRequest

Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : A transaction can’t span multiple connections.   Local and distributed transaction ares supported in 1.x you have to Enterpeise seveices library to regiser multiple connections and then call EnlistDistributedTransaction. Distributed Transaction Coordinator is required for Distributed transaction that’s available on windows 2000 & +. In 2.X and later use TransactionScope object. Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : Dispoase of the transaction must be called to complete the transaction. Distributed Transaction : ...

Code Access Security in .Net

Namespace: System.Security What is Code Access Security? Code Access Security is a mechanism through which Developers and administrators can restrict code from accessing different resources , without caring about the users’ access level. You can also control resource that can’t be controlled through traditional RBS (Role Based Security), e.g. Web Requests and DNS requests etc. It can be only applied to Managed Applications. These restriction are applied not to the user instead to the Application, thus it does not require username or password. Evidence: It is the information that runtime gather about the assembly to determine which Code Groups the assembly belongs to. The following table shows the common types of evidence that a host can present to the runtime. Evidence Description Application directory The application's installation directory. Hash Cryptographic hash such as SHA1. Publisher Soft...