Re: .Net 2.0 website is running on a different port?

Hello TS,

As for the ASP.NET 2.0 web projects, you can create it through both IIS
hosted mode or TestServer(WebDev.WebServer.exe) mode. When using the
TestServer, it can only be accessed locally and VS IDE will assign the test
server instance a random local port by default, you can change this port.
If you want to develop the ASP.NET application in IIS directly, just simply
choose "http" when you create the web project and select the proper virtual
directory in IIS.

From your description, after you use "http"/IIS to create the web project
in VS 2005, you can not debug or even run(without debug) the application,
correct? If so, I think there may has some problem with the IIS server's
configuration. Have you checked the server to see whether the Application's
virtual directory has been configured to ASPNET 2.0 version and whether the
application pool(if use IIS6) is configured to the current service account(
BY default it is network service for IIS6, you can also change it to local
system for test). If you want to use F5 debugging in VS 2005, you need
make sure the website is configured as "Integrated windows" authentication.
In addition, as for the problem you met when running the web project in
IIS without debugging, would you provide us the detailed error message or
screenshot of the problem?

BTW, if you think use testserver ok, and just want to change it to listen
on 80 port, you can change the TEstServer's port in VS IDE by the following
steps:

*open website project(filesystem based) in VS 2005

*In solution explorer, select the web site project node

*In the property view/window, you will find there is a "Port number"
property and a "Use dynamic ports" property under "Develper Web Server"
category.

*Set "use dynamic ports" to false

*change the "Port number" to 80 as you want

Before start running, make sure you need to stop the IIS default site or
any other application or service which is already listening on the 80 TCP
port.

Hope this helps.


Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead



This posting is provided "AS IS" with no warranties, and confers no rights.

.

Relevant Pages

  • Re: Web application causes Web Access Failed message
    ... the VS.NET will use the 80 default port to connect the IIS default ... So please check it in the IIS. ... Checked this item in the settings. ... When I try to create the web project, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Cant change SSL (HTTPS) port from 443
    ... You have a stray SecureBinding -- either you configured a prior certificate, ... or you ran a tool that added the configuration (and didn't clean up ... You need to delete it and restart IIS. ... port 443 anyway. ...
    (microsoft.public.inetserver.iis.security)
  • Re: iis server problem
    ... Yes, it does indeed look like IIS is not running, or is configured to use ... machine that is blocking port 80. ... server>> is ... >>> the right configuration to find your web page. ...
    (microsoft.public.inetserver.iis)
  • Re: .Net 2.0 website is running on a different port?
    ... The server won't care if the app was running through a different port in development. ... As for the ASP.NET 2.0 web projects, you can create it through both IIS ... after you use "http"/IIS to create the web project ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: .Net 2.0 website is running on a different port?
    ... how do i move my website and solution from the test server to IIS so i can ... server instance a random local port by default, ... after you use "http"/IIS to create the web project ...
    (microsoft.public.dotnet.framework.aspnet)
Loading