Custom extension for ASP.NET handler

Discussion in 'ASP.NET 2.0' started by ksachdeva, Jun 12, 2007.

  1. In ASP.NET 2.0 you can provide a custom extension for your handler in the config file with out needing to add it in ASP.NET filter in IIS. This works fine for me on my computer during development using VS.NET 2005.

    When I put my site on discountasp.net server that handler is not recognized. I had to change the extension of handler to ashx and it worked.

    Any suggestions ?

    Regards
    Kapil
     
  2. Thats because ashx is already mapped in the asp.net filter .For any other custom extension,a mappin on the DASP server is required.

    Vikram

    DiscountASP.NET
    www.DiscountASP.NET
     
  3. Bruce

    Bruce DiscountASP.NET Staff

    you are probably using the VS.NET development server which will automatically map all extension to ASP.NET. For IIS, you have to explicitly tell the server which extension should be handled by asp.net.


    You can create a support ticket and we will add the script mapping for you.


    Bruce

    DiscountASP.NET
    www.DiscountASP.NET
     
  4. That I understand, the point I am making is that in ASP.NET 2.0you could do this just in web.config and no need to map it to the asp.net filter.
     

Share This Page