Solution of ashx in IIS7 404

Iis7 is moved to this location, and a name attribute is added:

 

<Handlers>
<Remove name = "webservicehandlerfactory-integrated"/>
<Remove name = "scripthandlerfactory"/>
<Remove name = "scripthandlerfactoryapps tutorial ervices"/>
<Remove name = "scriptresource"/>
<Add name = "text" verb = "*" path = "text. ashx" type = "webapplication1.texthandler, webapplication1"/>
<Add name = "file" verb = "*" path = "file. ashx" type = "webapplication1.filehandler, webapplication1"/>
<Add name = "scripthandlerfactory" verb = "*" path = "*. asmx" precondition = "integratedmode"
Type = "system. web. script. services. scripthandlerfactory, system. web. extensions, version = 3.5.0.0, culture = neutral, publickeytoken = 31bf3856ad364e35"/>
<Add name = "scripthandlerfactoryappservices" verb = "*" path = "* _ appservice. axd" precondition = "integratedmode"
Type = "system. web. script. services. scripthandlerfactory, system. web. extensions, version = 3.5.0.0, culture = neutral, publickeytoken = 31bf3856ad364e35"/>
<Add name = "scriptresource" precondition = "integratedmode" verb = "get, head" path = "scriptresource. axd "type =" system. web. handlers. scriptresourcehandler, system. web. extensions, version = 3.5.0.0, culture = neutral, publickeytoken = 31bf3856ad364e35 "/>
</Handlers>

 

You can see that the bold part is added by yourself. If the VM fails to find a situation, it is estimated that the iis version is incorrect. Just change to another one. However, I found that both versions of iis are compatible with each other. This is good news.