Custom Http Handlers IIS7 and ASP.NET

Question

We have some HTTP handlers specified in our web.config. When we were running this site via a Web Site Project, all worked fine. But for some reason, after porting this over to a WAP project and pointing to the .NET 3.5 framework, the handlers are not working when I bring up the site in IIS 7 on our dev box. Do I need to do something special in IIS7 other than the specified custom handlers that already exist in my web.config?

When I look at the Handler Mappings section in IIS 7 for our site, I do see the 3 handlers listed with our custom extension. So it looks like it's picking up our handlers specified in our web.config. But I know that the handlers that were working in a non-wap website are not working in this WAP project and I don't know why.

For example, when one of our handlers tries to kick in when referenced I get:

Server Error in '/' Application. Parser Error Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Could not create type 'jaxHandler'.

Source Error:

Line 1:  
Line 2:  
Line 3:  using System;


Source File: /jaxHandler.ashx    Line: 1

Version Information: Microsoft .NET Framework Version:2.0.50727.3074; ASP.NET Version:2.0.50727.3074

furthermore, when I try to click on a hyperlink on our site that has .customextension on it the handler doesn't seem to pick it up.

So when I click on the hyperlink, I get:

HTTP Error 404.0 - Not Found
The resource you are looking for has been removed, had its name changed, or is temporarily unavailable. Detailed Error InformationModule IIS Web Core 
Notification MapRequestHandler 
Handler StaticFile 
Error Code 0x80070002 
Requested URL http://sss:80/somename.prod
Physical Path C:\www\sss\somename.prod 
Logon Method Anonymous 
Logon User Anonymous

(I have replaced the real text with 'somename' and our company name with 'sss') in the case above for privacy.

If I look in the Http Handlers section in IIS7, I do see that *.prod is registered. And here is how we have it set up in our web.config under the custom section:

<add name="sss" path="*.prod" verb="*" modules="IsapiModule" scriptProcessor="C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" resourceType="Unspecified" preCondition="bitness32"/>

Please elaborate. "It doesn't work" doesn't tell me much.

John Saunders
– John Saunders

2009-08-13 16:14:14 +00:00
Commented Aug 13, 2009 at 16:14 — John Saunders
– John Saunders, Commented Aug 13, 2009 at 16:14
ok, I added much more detail.

PositiveGuy
– PositiveGuy

2009-08-13 16:24:59 +00:00
Commented Aug 13, 2009 at 16:24 — PositiveGuy
– PositiveGuy, Commented Aug 13, 2009 at 16:24

Kevin Babcock · Accepted Answer · 2009-08-13 16:15:57Z

25

For ASP.NET applications running on IIS7, HttpHandlers should be mapped in the <system.webServer> section of your web.config. In IIS6, they were mapped in the <system.web> section.

<system.webServer>
    <handlers>
        <add name="HandlerName" 
             path="HandlerPath" verb="*" type="Handler.Type"
             resourceType="Unspecified" />
    </handlers>
</system.webServer>

answered Aug 13, 2009 at 16:15

Kevin Babcock

10.3k20 gold badges72 silver badges90 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

PositiveGuy Over a year ago

yes, we have ours mapped to webServer because this site is running already on our prod server in IIS7

John Saunders · Accepted Answer · 2009-08-13 16:24:16Z

0

What you need to do is build your code.

You need to copy all the C# code out into a .ashx.cs file. In fact, I recommend you create a new .ashx and copy the C# code into its .ashx.cs file.

Web sites build dynamically. Web Application Projects, like every other similar project type in Visual Studio, need to have code in source files, and to have that code build into an assembly.

answered Aug 13, 2009 at 16:24

John Saunders

162k26 gold badges252 silver badges403 bronze badges

14 Comments

PositiveGuy Over a year ago

the .ashx does not have a code behind. I see. Yea, because it was in a web site project. Gotcha

John Saunders Over a year ago

You've got it, but say "web site" - they're not projects.

PositiveGuy Over a year ago

Thank you. Because when I ran that Convert to Web Application over an .ashx id did not create a code-behind class or a .designer. Looks like no .designer is created but one would think that converting to a Web Application would at least create the code-behind file.

PositiveGuy Over a year ago

so I just figured that there was no code-behind for an .ashx even in a WAP which is not true.

John Saunders Over a year ago

@coffeeaddict: No, they're not projects. They differ from every other kind of project that Visual Studio creates. It was a horrible idea to implement web sites: we now have to ask which kind someone is using. Microsoft intended for us all to use web sites, so removed WAP in VS2005. At least then there would have been only one kind - no split in expertise and behavior. But with WAP added back in VS2005 SP1, we're left with a "mixed message", at best.

|

Collectives™ on Stack Overflow

Custom Http Handlers IIS7 and ASP.NET

2 Answers 2

1 Comment

14 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

14 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related