Axd format files, whether in asp.net or now asp.net mvc applications, are insus.net more preferred to use.
Because we can virtual a file that does not exist in the application. In fact, this format of the file is also handler, it has implemented the IHttpHandler interface. So you can create a axd to replace the ashx file.
Below insus.net in the asp.net MVC application, give a simple example, create, configure, and apply.
In the handlers directory, create a CS class, tentatively called it Axd.cs. This class name conforms to the C # class naming convention only.
The most important place in this class is to implement Interface IHttpHandler. Axd is created, but it cannot be used directly, it is also configured in Web.config:
Under the System.webserver node under the Handlers sub node,
Add to:
<add name= "Axdhandler" verb= "Post,get,head" path= "I.axd" type= "Insus.NET.Handlers.Axd"/>
Mark 1, specify a name.
Mark 2, this is the key place, this foreign name will be accessed when the user can see a filename. But you can define the same as the class name you created above, and there's no problem. But insus.net habit, or instead of a name that is not the same as the class name. Tag 3, which is the full name of the class, including namespaces.