IIS6 Wildcard Mappings and FrontPage Extensions

I was just setting up a new blog site to start working on a global admin console for .Text (adding, editing, deleting blogs, sending bulk e-mails to blog owners, configuring blog groups, etc) when I came across a problem. Though I had set up FrontPage Extensions on that virtual web, VS.NET could not connect to it. When I RDC'd into the desktop to try to access the site's FPSE page, I got an ASP.NET error page, telling me that the FPSE DLL was not found.

It turns out, you can't use a wildcard mapping and manage your FrontPage Extensions at the same time. This makes sense, because the ASP.NET process would be intercepting all requests. I'm not sure how you would get around this yet, but for now, I just shut off the mapping. If anyone can come up with a handler mapping that I can add to the web.config file that will allow both to co-exist, that would be swell. I don't really have the desire to look into it, so I'm just going to add and remove the mapping as needed.

2 Comments

  • Welcome to the club, Robert. I can add and remove that wildcard mapping in my sleep with the number of times I load up .text in VS.NET. If anyone can come up with a fix, you're the guy. Post us if you find out anything. Otherwise, like you said, it's no big deal adding and removing the wildcard extension mapping. Thx!

  • Having this exact problem, experimenting with remapping .dll before the wildcard, not sure if it will work, but probably worth a try, if anyone figures this out, please mail me...

    paul@epages.net

Comments have been disabled for this content.