IIS6 and ASP.Net Development Server

hello newsgroup,

there seems to be a different behaviour between the IIS running on my w2k3
webserver and the ASP.Net Development Server with which one debugs his
websites on the local pc:

This is the scenario:
My aim is to make all request being handled by an asp.net application.
When I developed the web application with Visual Studio 2005 it worked
perfectly. If e.g. the URL http://localhost:12345/test/Home is requested the
Begin_Request procedure in the global.asax received the request and could
translate this link into e.g.
http://localhost:12345/test/Default.aspx?param=Home.
Now I transferred the application to my web server. If now
http://mydomain.tld/Home is requested the IIS returns a 404, because the
directory Home doesn't exist physically.

How can I make the IIS ignore this and let my ASP.NET application handle
everything?

It would be great if someone had a hint for me.

Thanks in advance,
Nico Ploner

Re: IIS6 and ASP.Net Development Server

On 13 Jul, 14:33, "Nico Ploner"
wrote:
> hello newsgroup,
>
> there seems to be a different behaviour between the IIS running on my w2k3
> webserver and the ASP.Net Development Server with which one debugs his
> websites on the local pc:
>
> This is the scenario:
> My aim is to make all request being handled by an asp.net application.
> When I developed the web application with Visual Studio 2005 it worked
> perfectly. If e.g. the URLhttp://localhost:12345/test/Homeis requested the
> Begin_Request procedure in the global.asax received the request and could
> translate this link into e.g.http://localhost:12345/test/Default.aspx?param=Home.
> Now I transferred the application to my web server. If nowhttp://mydomain.tld/Homeis requested the IIS returns a 404, because the
> directory Home doesn't exist physically.
>
> How can I make the IIS ignore this and let my ASP.NET application handle
> everything?
>
> It would be great if someone had a hint for me.
>
> Thanks in advance,
> Nico Ploner

Parent Paths?

Re: IIS6 and ASP.Net Development Server

Hi Grego,

thank you for your quick reply.
Enabeling parent paths didn't help.
The "Enable parent paths" option only allows .asp files to have inclusions
pointing to files that are "above" the page directory, doesn't it?
But there is no file that includes anything.

The only file existing is the Default.aspx. Each request should be handeled
by the global.asax and is internally rewritten to the Default.aspx with a
parameter.
But it doesn't seem as if the global.asax was reached at all.

Do you have another idea?

Best regards.
Nico

"grego" schrieb im Newsbeitrag
news:1184339363.251786.298720@57g2000hsv.googlegroups.com...
> On 13 Jul, 14:33, "Nico Ploner"
> wrote:
>> hello newsgroup,
>>
>> there seems to be a different behaviour between the IIS running on my
>> w2k3
>> webserver and the ASP.Net Development Server with which one debugs his
>> websites on the local pc:
>>
>> This is the scenario:
>> My aim is to make all request being handled by an asp.net application.
>> When I developed the web application with Visual Studio 2005 it worked
>> perfectly. If e.g. the URLhttp://localhost:12345/test/Homeis requested
>> the
>> Begin_Request procedure in the global.asax received the request and could
>> translate this link into
>> e.g.http://localhost:12345/test/Default.aspx?param=Home.
>> Now I transferred the application to my web server. If
>> nowhttp://mydomain.tld/Homeis requested the IIS returns a 404, because
>> the
>> directory Home doesn't exist physically.
>>
>> How can I make the IIS ignore this and let my ASP.NET application handle
>> everything?
>>
>> It would be great if someone had a hint for me.
>>
>> Thanks in advance,
>> Nico Ploner
>
> Parent Paths?
>

Re: IIS6 and ASP.Net Development Server

Hello,

You need to tell IIS that you want all requests to be handled by the
ASP.NET ISAPI. By default, only requests mapped to any of the configured
extensions will be handled by ASP.NET, thus making it possible for your
code to handle the request.

To do this on IIS 6 and using ASP.NET 2.0, create a wildcard mapping:
- Right click the website in IIS Manager.
- Click on the Home Directory tab.
- Click Configuration button.
- Click Insert button in the wildcard application section.
- Specify the path to the ASP.NET 2.0 ISAPI.

Now the request should be handled by ASP.NET, and with proper
configuration of ASP.NET, your code should get the request and be able to
handle it.

--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info


Nico Ploner wrote:

>hello newsgroup,
>
>there seems to be a different behaviour between the IIS running on my w2k3
>webserver and the ASP.Net Development Server with which one debugs his
>websites on the local pc:
>
>This is the scenario:
>My aim is to make all request being handled by an asp.net application.
>When I developed the web application with Visual Studio 2005 it worked
>perfectly. If e.g. the URL http://localhost:12345/test/Home is requested
>the Begin_Request procedure in the global.asax received the request and
>could translate this link into e.g.
>http://localhost:12345/test/Default.aspx?param=Home.
>Now I transferred the application to my web server. If now
>http://mydomain.tld/Home is requested the IIS returns a 404, because the
>directory Home doesn't exist physically.
>
>How can I make the IIS ignore this and let my ASP.NET application handle
>everything?
>
>It would be great if someone had a hint for me.
>
>Thanks in advance,
>Nico Ploner

Re: IIS6 and ASP.Net Development Server

Hello Kristofer,

thank you for your reply.
This is exactly what i was looking for. It's working now.

Thanks again,
Nico

"Kristofer Gafvert" schrieb im Newsbeitrag
news:xn0f8ntaua25fyg005@news.microsoft.com...
> Hello,
>
> You need to tell IIS that you want all requests to be handled by the
> ASP.NET ISAPI. By default, only requests mapped to any of the configured
> extensions will be handled by ASP.NET, thus making it possible for your
> code to handle the request.
>
> To do this on IIS 6 and using ASP.NET 2.0, create a wildcard mapping:
> - Right click the website in IIS Manager.
> - Click on the Home Directory tab.
> - Click Configuration button.
> - Click Insert button in the wildcard application section.
> - Specify the path to the ASP.NET 2.0 ISAPI.
>
> Now the request should be handled by ASP.NET, and with proper
> configuration of ASP.NET, your code should get the request and be able to
> handle it.
>
> --
> Regards,
> Kristofer Gafvert
> http://www.gafvert.info/iis/ - IIS Related Info
>
>
> Nico Ploner wrote:
>
>>hello newsgroup,
>>
>>there seems to be a different behaviour between the IIS running on my w2k3
>>webserver and the ASP.Net Development Server with which one debugs his
>>websites on the local pc:
>>
>>This is the scenario:
>>My aim is to make all request being handled by an asp.net application.
>>When I developed the web application with Visual Studio 2005 it worked
>>perfectly. If e.g. the URL http://localhost:12345/test/Home is requested
>>the Begin_Request procedure in the global.asax received the request and
>>could translate this link into e.g.
>>http://localhost:12345/test/Default.aspx?param=Home.
>>Now I transferred the application to my web server. If now
>>http://mydomain.tld/Home is requested the IIS returns a 404, because the
>>directory Home doesn't exist physically.
>>
>>How can I make the IIS ignore this and let my ASP.NET application handle
>>everything?
>>
>>It would be great if someone had a hint for me.
>>
>>Thanks in advance,
>>Nico Ploner

Re: IIS6 and ASP.Net Development Server

Additional information for those who have the similar problem that I had:

It is important to uncheck the "verify if file exists" tick. Otherwise IIS
will still return a 404 error state.

Greetings,
Nico

"Kristofer Gafvert" schrieb im Newsbeitrag
news:xn0f8ntaua25fyg005@news.microsoft.com...
> Hello,
>
> You need to tell IIS that you want all requests to be handled by the
> ASP.NET ISAPI. By default, only requests mapped to any of the configured
> extensions will be handled by ASP.NET, thus making it possible for your
> code to handle the request.
>
> To do this on IIS 6 and using ASP.NET 2.0, create a wildcard mapping:
> - Right click the website in IIS Manager.
> - Click on the Home Directory tab.
> - Click Configuration button.
> - Click Insert button in the wildcard application section.
> - Specify the path to the ASP.NET 2.0 ISAPI.
>
> Now the request should be handled by ASP.NET, and with proper
> configuration of ASP.NET, your code should get the request and be able to
> handle it.
>
> --
> Regards,
> Kristofer Gafvert
> http://www.gafvert.info/iis/ - IIS Related Info
>
>
> Nico Ploner wrote:
>
>>hello newsgroup,
>>
>>there seems to be a different behaviour between the IIS running on my w2k3
>>webserver and the ASP.Net Development Server with which one debugs his
>>websites on the local pc:
>>
>>This is the scenario:
>>My aim is to make all request being handled by an asp.net application.
>>When I developed the web application with Visual Studio 2005 it worked
>>perfectly. If e.g. the URL http://localhost:12345/test/Home is requested
>>the Begin_Request procedure in the global.asax received the request and
>>could translate this link into e.g.
>>http://localhost:12345/test/Default.aspx?param=Home.
>>Now I transferred the application to my web server. If now
>>http://mydomain.tld/Home is requested the IIS returns a 404, because the
>>directory Home doesn't exist physically.
>>
>>How can I make the IIS ignore this and let my ASP.NET application handle
>>everything?
>>
>>It would be great if someone had a hint for me.
>>
>>Thanks in advance,
>>Nico Ploner