ASP.net on ISS

  • Thread starter Thread starter Stefan Richter
  • Start date Start date
S

Stefan Richter

Hi, installed IIS 5.0,
but it won't display any asp files, nor does it work with Visual Studio.

Here's a detailed description of what I did so far:

I installed the IIS 5.0 after the installation of Visual Studio.Net:
Common Files
Documentation
Frontpage 2000 Extensions
Internet Information Services Snap In
Internet Services Manager(HTML)
World Wide Web Server
( I only left out SMTP Service)

( Do I maybe need IIS 6.0 ?)

I reinserted the Visual Studio.Net Cds and added all necessary ASP
components.
According to IISRESET /STATUS the server is running:
Status for World Wide Web Publishing Service ( W3SVC ) : Running
I wrote a little asp page "index.asp":
<%
response.write "Hi"
%>
and put it into Inetpub/wwwroot/index.asp

However, when entering http://localhost/ into my browser, it only displays
the "page not found" error.

Besides from what I did so far, I have no idea what I have to do.
( E.g.: Which settings have I got to do in IIS Manager???)
Have I got to add a new folder to Inetpub\wwwroot\ with the same name as my
project?
Cause in Visual Studio it wants to start a project in
http://localhost/WebApplication1

When I try that, it says:
"Visual Studio has detected that the specified web server is not running
ASP.Net version 1.1.
You will be unable to run ASP.Net Web applications or services."

I thought running
Windows\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -r
would solve this, but unfortunately it did not.

Any ideas?

Thx,

Stefan
 
If you install IIS after .NET, you have to run aspnet_regiis /i from the
Framework directory (version you are using). It is under the Windows root
(either Windows or WINNT in most installs).

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************
Think Outside the Box!
************************************************
 
This is in the message from Richter George


I thought running
Windows\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -r
would solve this, but unfortunately it did not.
 
Back
Top