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...

Concept of App Domain in .Net

Creating Application Domains: Application domain is just like process, provides separate memory space, and isolates from other code. But it’s quite light weight. It also provides the following advantages: 1-       Reliability : If a domain crashes, it can be unloaded. Hence doesn’t affect the other assemblies. 2-       Efficiency : Loading all assemblies in one domain can be cumbersome and can make the process heavy but Appdomains are efficient in this manner. Important properties of AppDomain: ApplicationIdentity , ApplicationTrust , BaseDirectory , CurrentDomain , DomainManager , DomainDirectory , Evidence , FriendlyName , ID , RelativeSearchPath , SetupInformation , ShadowCopyFiles . Important methods of AppDomain: ApplyPolicy , CreateCOMInstanceFrom , CreateDomain , CreateInstance (Assembly). To create an AppDomain: AppDomain adomain = AppDomain.CreateDomain(“D”); To execute an assembly:...

ASP.NET Working With Data-Bound Web Server Controls

Suppose we have: List<Car> vCars = new List<Car>(); There are three types of databound controls: Simple databound controls(List, AdRotater), Composite data bound controls(GridView, DetailsView, FormView that inherit from CompositeDataBoundControl), and Hierarchal data bound controls (TreeView, Menu).   DataBoundControl has a DataBind method that can be used when data is ready. It calls DataBind for child controls as well. Page.DataBind() will call DataBind for all child controls. Using DataSource Objects:                                       BaseDataBound control exposes DataSource property that accepts objects that implement IEnumerable , IListSource , IDataSource , or IHierarchalDataSource . DataSourceID accepts ID of SqlDataSource . If both specified Data...