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
continue developing thru IIS and so my website can be accessed from other
computers?

thanks

"Steven Cheng[MSFT]" <stcheng@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:TskR1jiAHHA.3912@xxxxxxxxxxxxxxxxxxxxxxxx
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: Can I run an Internet web server from a Win2K computer?
    ... You can deffinately run an internet website from IIS on Windows 2000 Pro., ... Be aware though, that there can be no more than 10 simultaneous connections, but for your homegrown website, I would think that this is not a problem. ... You will have to set up your broadband router to forward incoming HTTP connections on port 80 to the computer hosting the website ... I'm trying to use the web server that comes with Windows 2000 ...
    (microsoft.public.win2000.general)
  • Re: Virtual Server 2005 R2 SP1 will not install
    ... I have noticed that the Website Port box on the Configure Components page is ... I was trying to find the latest version of IIS ... The OS I am trying to install Virtual Server 2005 on is Windows ...
    (microsoft.public.windows.server.general)
  • Re: Creating a server based web on a local server
    ... don't forget that your ISP might block port 80 so nobody outside will be ... in website property in MMC. ... > do is create a web site on the server so can make full use of the front ... IIS ...
    (microsoft.public.frontpage.client)
  • IIS on SBS 2003 behind COX Cable...
    ... I'm testing the external website functionality of SBS 2003 for my small ... I know that COX blocks port 80, ... It seems like IIS doesn't ... NetGear Router assigned port forwarding for HTTP requests of ports 80 to 83 ...
    (microsoft.public.inetserver.iis)