C
craig.wagner
I took an application that we have that is part ASP, part ASP.NET, and
migrated it to VS 2005. The migration worked okay, it's trying to run
it where I am having some challenges.
When I open the application in VS 2005, I can open it one of two ways
(okay, there's actually more than two, but these are the two I've
used), either from the file system or using my local IIS server.
When I open it from the file system and try to run the application, it
uses the ASP.NET Development Server as its web server. The problem is
that the first page of the site is one of the classic ASP pages, and
the following message is generated.
This type of page is not served.
Description: The type of page you have requested is not served because
it has been explicitly forbidden. The extension '.asp' may be
incorrect. Please review the URL below and make sure that it is
spelled correctly.
Requested URL: /ReportsWeb/login.asp
When I open the site using the local IIS option, the site runs
correctly (as I would expect, I'm using IIS to serve up the app).
So I guess the question is, is there any way to configure the ASP.NET
Development Server to serve up ASP pages? Or in this situation am I
required to rely on IIS?
migrated it to VS 2005. The migration worked okay, it's trying to run
it where I am having some challenges.
When I open the application in VS 2005, I can open it one of two ways
(okay, there's actually more than two, but these are the two I've
used), either from the file system or using my local IIS server.
When I open it from the file system and try to run the application, it
uses the ASP.NET Development Server as its web server. The problem is
that the first page of the site is one of the classic ASP pages, and
the following message is generated.
This type of page is not served.
Description: The type of page you have requested is not served because
it has been explicitly forbidden. The extension '.asp' may be
incorrect. Please review the URL below and make sure that it is
spelled correctly.
Requested URL: /ReportsWeb/login.asp
When I open the site using the local IIS option, the site runs
correctly (as I would expect, I'm using IIS to serve up the app).
So I guess the question is, is there any way to configure the ASP.NET
Development Server to serve up ASP pages? Or in this situation am I
required to rely on IIS?