When you use the ASP.NET Development Server to run a file-system Web site, by default, the Web server is invoked on a randomly selected port for localhost. For example, if you are testing a page called Default.aspx, when you run the page using the built-in ASP.NET Development Server, the URL of the page might be the following:
http://localhost:3499/Default.aspx
You do have the option to control which port is used when using the built-in development server. The steps to specify the port to be used are slightly different depending on whether you are using a website project or a web application project.
To specify a port for the ASP.NET Development Server - WebSite / WebServices projects
- In Solution Explorer, click the name of the application.
- In the Properties pane, click the down-arrow beside Use dynamic ports and select False from the dropdown list.
This will enable editing of the Port number property. - In the Properties pane, click the text box beside Port number and type in a port number.
- Click outside of the Properties pane. This saves the property settings.
Each time you run a file-system Web site within Visual Web Developer, the ASP.NET Development Server will listen on the specified port.
To specify a port for the ASP.NET Development Server - Web Application project
Right click the Project in the Solution Explorer, and then select “Properties”
Click “Web” tab.
Check “Specific port” instead of “Auto-assign Port”.
If you want to debug with IIS, please follow the first and second steps above, and then check “Use IIS Web Server” instead of “Use Visual Studio Development Server”. Also, click the “Create Virtual Directory” button.
Note: Visual Web Developer cannot guarantee that the port you specify will be available when you run your file-system Web site. If the port is in use when you run a page, Visual Web Developer displays an error message.
The ASP.NET Wiki was started by Scott Hanselman in February of 2008. The idea is that folks spend a lot of time trolling the blogs, googlinglive-searching for answers to common "How To" questions. There's piles of fantastic community-created and MSFT-created content out there, but if it's not found by a search engine and the right combination of keywords, it's often lost.
The ASP.NET Wiki articles moved to CodeProject in October 2013 and will live on, loved, protected and updated by the community.