Application Extension Mapping, not working?

Hello,

I think I followed the steps necessary to have a new file extension be
processed by the ASP.NET ISAPI DLL.

In the IIS Admin plugin, I went to Default Website Properties, Home
Directory, Configuration, Mappings, Add and set the executable path to
"c:\windows\microsoft.net\framework\v2.0.50727\aspnet_isapi. dll", the
extension to ".ppp", selected "All Verbs" and "Script Engine."

However, when I try pulling up http://localhost/test.ppp in my browser, I
see the ASPX tags in the source("<%Response.Write etc.%>).

If I run aspnet_compilier on the root project, it does not create an
assembly for this file.

What am I missing? Is there a KB article on this?

Thanks

Eric

Re: Application Extension Mapping, not working?

What you have done should work. Have you restarted IIS (shouldn't be
necessary, but can't hurt).

Cheers
Ken

"Eric" wrote in message
news:Oekyy9WvHHA.1340@TK2MSFTNGP02.phx.gbl...
> Hello,
>
> I think I followed the steps necessary to have a new file extension be
> processed by the ASP.NET ISAPI DLL.
>
> In the IIS Admin plugin, I went to Default Website Properties, Home
> Directory, Configuration, Mappings, Add and set the executable path to
> "c:\windows\microsoft.net\framework\v2.0.50727\aspnet_isapi. dll", the
> extension to ".ppp", selected "All Verbs" and "Script Engine."
>
> However, when I try pulling up http://localhost/test.ppp in my browser, I
> see the ASPX tags in the source("<%Response.Write etc.%>).
>
> If I run aspnet_compilier on the root project, it does not create an
> assembly for this file.
>
> What am I missing? Is there a KB article on this?
>
> Thanks
>
> Eric
>

Re: Application Extension Mapping, not working?

I edited machine.config, copying the *.aspx entries, and it started working
for 2.0.

It still won't work if I switch to the 1.1.4322 engine, even after editing
the machine.config file.

Any suggestions?

Thanks,

Eric


"Ken Schaefer" wrote in message
news:elWNGKXvHHA.3772@TK2MSFTNGP05.phx.gbl...
> What you have done should work. Have you restarted IIS (shouldn't be
> necessary, but can't hurt).
>
> Cheers
> Ken
>
> "Eric" wrote in message
> news:Oekyy9WvHHA.1340@TK2MSFTNGP02.phx.gbl...
>> Hello,
>>
>> I think I followed the steps necessary to have a new file extension be
>> processed by the ASP.NET ISAPI DLL.
>>
>> In the IIS Admin plugin, I went to Default Website Properties, Home
>> Directory, Configuration, Mappings, Add and set the executable path to
>> "c:\windows\microsoft.net\framework\v2.0.50727\aspnet_isapi. dll", the
>> extension to ".ppp", selected "All Verbs" and "Script Engine."
>>
>> However, when I try pulling up http://localhost/test.ppp in my browser, I
>> see the ASPX tags in the source("<%Response.Write etc.%>).
>>
>> If I run aspnet_compilier on the root project, it does not create an
>> assembly for this file.
>>
>> What am I missing? Is there a KB article on this?
>>
>> Thanks
>>
>> Eric
>>
>

Re: Application Extension Mapping, not working?

For ASPNET_ISAPI.DLL to handle a request, you need:
1. Execute Permissions in IIS to be either "Scripts" or "Scripts and
Executables"
2. Configure ASPNET_ISAPI.DLL to be the Application Mapping for the
extension
3. Configure a PageHandler to be the httpHandler inside of web.config/
machine.config for the extension

Why one does each step:
1. Make sure IIS executes .ppp requests instead of serve it as static
file
2. Make sure that IIS executes .ppp requests with ASPNET_ISAPI.DLL
3. Make sure that ASPNET_ISAPI.DLL chooses PageHandler to execute .ppp
requests

The easiest way is to copy all existing configuration for .aspx. After
you have done #1 and #2, the question is no longer an IIS-related
question. Details of ASP.Net behavior is best discussed in a forum
dedicated to ASP.Net.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Jul 3, 6:16 am, "Eric" wrote:
> I edited machine.config, copying the *.aspx entries, and it started working
> for 2.0.
>
> It still won't work if I switch to the 1.1.4322 engine, even after editing
> the machine.config file.
>
> Any suggestions?
>
> Thanks,
>
> Eric
>
> "Ken Schaefer" wrote in message
>
> news:elWNGKXvHHA.3772@TK2MSFTNGP05.phx.gbl...
>
>
>
> > What you have done should work. Have you restarted IIS (shouldn't be
> > necessary, but can't hurt).
>
> > Cheers
> > Ken
>
> > "Eric" wrote in message
> >news:Oekyy9WvHHA.1340@TK2MSFTNGP02.phx.gbl...
> >> Hello,
>
> >> I think I followed the steps necessary to have a new file extension be
> >> processed by the ASP.NET ISAPI DLL.
>
> >> In the IIS Admin plugin, I went to Default Website Properties, Home
> >> Directory, Configuration, Mappings, Add and set the executable path to
> >> "c:\windows\microsoft.net\framework\v2.0.50727\aspnet_isapi. dll", the
> >> extension to ".ppp", selected "All Verbs" and "Script Engine."
>
> >> However, when I try pulling uphttp://localhost/test.pppin my browser, I
> >> see the ASPX tags in the source("<%Response.Write etc.%>).
>
> >> If I run aspnet_compilier on the root project, it does not create an
> >> assembly for this file.
>
> >> What am I missing? Is there a KB article on this?
>
> >> Thanks
>
> >> Eric- Hide quoted text -
>
> - Show quoted text -

Re: Application Extension Mapping, not working?

I tried the copying of aspx settings for .NET 1.1.

I'll move the discussion to the asp.net forum. Thanks for pointing that
out.

Eric



"David Wang" wrote in message
news:1183490109.739968.10760@e9g2000prf.googlegroups.com...
> For ASPNET_ISAPI.DLL to handle a request, you need:
> 1. Execute Permissions in IIS to be either "Scripts" or "Scripts and
> Executables"
> 2. Configure ASPNET_ISAPI.DLL to be the Application Mapping for the
> extension
> 3. Configure a PageHandler to be the httpHandler inside of web.config/
> machine.config for the extension
>
> Why one does each step:
> 1. Make sure IIS executes .ppp requests instead of serve it as static
> file
> 2. Make sure that IIS executes .ppp requests with ASPNET_ISAPI.DLL
> 3. Make sure that ASPNET_ISAPI.DLL chooses PageHandler to execute .ppp
> requests
>
> The easiest way is to copy all existing configuration for .aspx. After
> you have done #1 and #2, the question is no longer an IIS-related
> question. Details of ASP.Net behavior is best discussed in a forum
> dedicated to ASP.Net.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>
>
>
>
> On Jul 3, 6:16 am, "Eric" wrote:
>> I edited machine.config, copying the *.aspx entries, and it started
>> working
>> for 2.0.
>>
>> It still won't work if I switch to the 1.1.4322 engine, even after
>> editing
>> the machine.config file.
>>
>> Any suggestions?
>>
>> Thanks,
>>
>> Eric
>>
>> "Ken Schaefer" wrote in message
>>
>> news:elWNGKXvHHA.3772@TK2MSFTNGP05.phx.gbl...
>>
>>
>>
>> > What you have done should work. Have you restarted IIS (shouldn't be
>> > necessary, but can't hurt).
>>
>> > Cheers
>> > Ken
>>
>> > "Eric" wrote in message
>> >news:Oekyy9WvHHA.1340@TK2MSFTNGP02.phx.gbl...
>> >> Hello,
>>
>> >> I think I followed the steps necessary to have a new file extension be
>> >> processed by the ASP.NET ISAPI DLL.
>>
>> >> In the IIS Admin plugin, I went to Default Website Properties, Home
>> >> Directory, Configuration, Mappings, Add and set the executable path to
>> >> "c:\windows\microsoft.net\framework\v2.0.50727\aspnet_isapi. dll", the
>> >> extension to ".ppp", selected "All Verbs" and "Script Engine."
>>
>> >> However, when I try pulling uphttp://localhost/test.pppin my browser,
>> >> I
>> >> see the ASPX tags in the source("<%Response.Write etc.%>).
>>
>> >> If I run aspnet_compilier on the root project, it does not create an
>> >> assembly for this file.
>>
>> >> What am I missing? Is there a KB article on this?
>>
>> >> Thanks
>>
>> >> Eric- Hide quoted text -
>>
>> - Show quoted text -
>