http://forums.iis.net/search/SearchResults.aspx?o=DateDescending&tag=Wildcard+Application+Mapping&orTags=0Search results matching tag 'Wildcard Application Mapping'en-USCommunityServer 2007 SP1 (Build: 20510.895)http://forums.iis.net/p/1152081/1880783.aspx#1880783Tue, 30 Sep 2008 17:42:37 GMT50bcf3b4-f6fe-4638-adff-0c150e922e99:1880783ovalsquarepublishing--1<p>I&#39;ve looked throughout these forums, but there doesn&#39;t seem to be any answers: <br /></p><p>While I&#39;d love to get rid of requiring FrontPage Extensions on a heavy traffic site I host, the client requires it to administrate the site. Having just implemented Wildcard Application Mapping in IIS 6 on this site in order to provide integrated Forms Authentication security between ASP and ASP.NET resources, this breaks FrontPage extensions. Everything works like a charm, including encrypting and caching roles that are now available even to ASP, except for the loss of FrontPage. Specifically, you cannot even login to FrontPage administration (incorrect credentials).<br /><br />Has anyone gotten FrontPage to work with Wildcard Application Mapping routing through the ASP.NET 2.0 aspnet_isapi.dll?<br />&nbsp;</p>