Home/ Questions/Q 4078708
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T17:42:30+00:00

Thanks to the published ASP.NET MVC conventions, I’m looking much more closely at the

  • 0

Thanks to the published ASP.NET MVC conventions, I’m looking much more closely at the idea of universal conventions over configuration for my projects (versus ‘home-rolled’ conventions, or grabbing from a variety of conventions).

However, I’m not seeing much, if anything, about the preferred location of ASHX files in, for example, ASP.NET MVC projects (as well as Web forms projects).

Is there a recommended directory structure for these? Perhaps there’s a published specification with a much larger directory structure accounted for?

My personal convention has been to place these within a top-level Handlers directory, but I honestly haven’t personally seen any other projects that really do this.

I suppose, depending upon what it does (for example, generating an image), that one could argue this might go into the Content directory, but it seems this directory is generally used for static files.

(Aside: One could argue that ASHX files are not needed in MVC projects, but based on questions posted here, it appears ASHX files still have their place in MVC projects.)

EDIT: Ignore MVC projects, since I’m suggesting that as one example. How about Web Forms, then?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    My personal convention is to not create handlers as ASHX files, but as classes delivering form IHttpHandler interface. I keep them in separate .dll file and register through web.config.

    On the other hand all the scenarios described in question you have linked are easy to achieve within ASP.NET MVC Framework, without additional handlers.

    • 0