122

I want to change the port number on which my website runs while debugging from Visual Studio. I am using Visual Studio 2012, and I am using ASP.NET MVC 4 for my projects I want to change the port. Random port or fixed anyone will work just want to change the port.

Ashley Medway
  • 6,659
  • 7
  • 43
  • 63
Mohit
  • 1,989
  • 4
  • 20
  • 37

13 Answers13

138

To specify a port for a Web application project that uses IIS Express

  1. In Solution Explorer, right-click the name of the application and then select Properties. Click the Web tab.

  2. In the Servers section, under Use Local IIS Web server, in the Project URL box change the port number.

  3. To the right of the Project URL box, click Create Virtual Directory, and then click OK.

  4. In the File menu, click Save Selected Items.

  5. To verify the change, press CTRL+F5 to run the project. The new port number appears in the address bar of the browser.

From How to: Specify a Port for the Development Server (archive.org backup here).

dbc
  • 80,875
  • 15
  • 141
  • 235
hutchonoid
  • 31,459
  • 14
  • 91
  • 100
  • 19
    That doesn't work for Web Sites. Only for Web Application projects. – Supersharp Mar 01 '16 at 15:08
  • 3
    No Web tab here... You would think that in 2017, this would no longer be an issue.. That or at the very least we should be able to change ports without having to do magic – calcazar Jan 12 '17 at 16:38
  • Visual Studio 2015 not exist option (ASP.NET Empty Web Site) .. how to make? – KingRider May 18 '17 at 13:27
  • I had been doing all of this, except clicking the Create Virtual Directory button. Doing that made the different; now it works. But why is that necessary? – Rod Jun 01 '18 at 17:20
  • Well if you do this, you are no longer using IIS Express, but local IIS. So just go to Web tab in Project Properties and edit the port to whatever you need. – VladT Aug 03 '18 at 08:59
  • Why local IIS instead of IIS express? – fletchsod Feb 11 '20 at 15:43
76

Here's a more manual method that works both for Website projects and Web Application projects. (you can't change the project URL from within Visual Studio for Website projects.)

Web Application projects

  1. In Solution Explorer, right-click the project and click Unload Project.

  2. Navigate to the IIS Express ApplicationHost.config file. By default, this file is located in:

    %userprofile%\Documents\IISExpress\config

    In recent Visual Studio versions and Web Application projects, this file is in the solution folder under [Solution Dir]\.vs\config\applicationhost.config (note the .vs folder is a hidden item)

  3. Open the ApplicationHost.config file in a text editor. In the <sites> section, search for your site's name. In the <bindings> section of your site, you will see an element like this:

    <binding protocol="http" bindingInformation="*:56422:localhost" />

    Change the port number (56422 in the above example) to anything you want. e.g.:

    <binding protocol="http" bindingInformation="*:44444:localhost" />

    Bonus: You can even bind to a different host name and do cool things like:

    <binding protocol="http" bindingInformation="*:80:mysite.dev" />

    and then map mysite.dev to 127.0.0.1 in your hosts file, and then open your website from "http://mysite.dev"

  4. In Solution Explorer, right-click the the project and click Reload Project.

  5. In Solution Explorer, right-click the the project and select Properties.

    • Select the Web tab.

    • In the Servers section, under Use Local IIS Web server, in the Project URL box enter a URL to match the hostname and port you entered in the ApplicationHost.config file from before.

    • To the right of the Project URL box, click Create Virtual Directory. If you see a success message, then you've done the steps correctly.

    • In the File menu, click Save Selected Items.

Website projects

  1. In Solution Explorer, right-click the project name and then click Remove or Delete; don't worry, this removes the project from your solution, but does not delete the corresponding files on disk.

  2. Follow step 2 from above for Web Application projects.

  3. In Solution Explorer, right-click the solution, select Add, and then select Existing Web Site.... In the Add Existing Web Site dialog box, make sure that the Local IIS tab is selected. Under IIS Express Sites, select the site for which you have changed the port number, then click OK.

Now you can access your website from your new hostname/port.

Saeb Amini
  • 19,545
  • 8
  • 69
  • 71
  • 1
    Awesome, exactly what was needed. Had to fish around for a working port, but this did the trick, thank you. – hobwell Nov 20 '14 at 17:36
  • 1
    Thanks Saeb. This works perfectly. Just a point to note... I am using source control and after adding my Website project back I had to go to File > Source Control > Advanced > Change Source Control and rebind my project to my source control server. This just meant selecting the project in the list and clicking on the 'Bind' button next to 'Refresh'. Thanks for the excellent answer. – Dirk Strauss Oct 28 '15 at 08:02
  • 2
    Great answer - Instead of "right-click the project name and then click Remove or Delete", you can select "unload project instead", then again edit your applicationhost.config, mine was at "\.vs\config\applicationhost.config" (note the .vs folder is a hidden item, so select the option to show hidden files in you file explorer ) – Paul Gorbas Apr 19 '16 at 14:23
  • 2
    @PaulGorbas glad it helped you. Note that you can't "unload" _websites_, that only works for web applications. – Saeb Amini Apr 19 '16 at 14:27
  • 3
    How to make this work for a custom SSL port? For any port except 60233, I get "This page can’t be displayed" in Internet Explorer, and similar messages in other web browsers. Where in Windows 7 does one designate SSL ports? – MiloDC Dec 28 '16 at 06:46
  • Thanks! Though %systemdrive%\Users\\Documents isn't necessarily correct - it's the path to your 'My Documents' folder, which I've got on a different drive to my users folder. And there doesn't appear to be a variable set to that in Windows. – Ian Grainger Apr 25 '17 at 09:01
  • @IanGrainger the path above is: %userprofile%\Documents\IISExpress\config - this is different from what you mention - I just tested and it put me in the right place. – qxotk May 07 '18 at 14:44
  • This fix worked for me, but I had to mess around quite a bit to get iisexpress to run, as I was getting errors within vs2017. This page shows how to run iisexpress from command line, which was helpful for me: https://docs.microsoft.com/en-us/iis/extensions/using-iis-express/running-iis-express-from-the-command-line – qxotk May 07 '18 at 14:49
  • NOTE: In order for "Add Existing Website" to work in vs2017 - you should have a version of at least 15.6.5 - as there were some earlier versions where add existing website was not working at all. – qxotk May 07 '18 at 14:51
24

.Net Core

For those who got here looking for this configuration in .Net core this resides in the Properties\lauchSettings.json. Just edit the port in the property "applicationUrl".

The file should look something like this:

{
  "iisSettings": {
    "windowsAuthentication": false,
    "anonymousAuthentication": true,
    "iisExpress": {
      "applicationUrl": "http://localhost:53950/", //Here
      "sslPort": 0
    }
  },
  "profiles": {
    "IIS Express": {
      "commandName": "IISExpress",
      "launchBrowser": true,
      "launchUrl": "index.html",
      "environmentVariables": {
        "Hosting:Environment": "Development"
      },
    }
  }
}

Or you can use the GUI by double clicking in the "Properties" of your project.

Note: I had to reopen VS to make it work.

Richard Garside
  • 82,523
  • 9
  • 75
  • 82
fabriciorissetto
  • 8,005
  • 4
  • 58
  • 69
  • 1
    Brilliant answer. Restarting VS worked for me. Apparently BitDefender's `ProductAgentService.exe` service uses port 50151 which conflicted with IIS Express' default port. – silkfire Aug 11 '17 at 20:25
  • 7
    SSL ports are restricted to 44300-44399. Could be good to know. – FatAlbert Feb 12 '20 at 09:24
17

Right click on your MVC Project. Go to Properties. Go to the Web tab.
Change the port number in the Project Url. Example. localhost:50645
Changing the bold number, 50645, to anything else will change the port the site runs under.
Press the Create Virtual Directory button to complete the process.

See also: http://msdn.microsoft.com/en-us/library/ms178109.ASPX

Image shows the web tab of an MVC Project enter image description here

Ashley Medway
  • 6,659
  • 7
  • 43
  • 63
10

If you just want to change the port because it is already in use. Follow the following steps.

In Visual studio

  1. Right-click on Project Node and Unload Project
  2. Right-click on Project Node and Edit .csproj file.
  3. Search for the following tags and remove them
<DevelopmentServerPort>62140</DevelopmentServerPort>
<DevelopmentServerVPath></DevelopmentServerVPath>
<IISUrl>http://localhost:62116/</IISUrl>
  1. press Ctrl + S to save the document
  2. Right-click on Project Node and load Project

It will work by selecting another port randomly.

For further information. please click

Henrique Zacchi
  • 1,124
  • 12
  • 17
Charlie
  • 4,262
  • 1
  • 28
  • 50
2

Another fix for those who have IIS Installed:

Create a path on the IIS Server, and allocate your website/app there.

Go to propieties of the solution of the explorer, then in front of using the iisexpress from visual studio, make that vs uses your personal own IIS.

Solution Proprieties

Bhargav Rao
  • 41,091
  • 27
  • 112
  • 129
Alex
  • 21
  • 1
2

You can first start IIS express from command line and give it a port with /port:port-number see other options.

John Henckel
  • 7,448
  • 2
  • 55
  • 68
2

If we are talking about a WebSite, not web app, my issue was that the actual .sln folder was somewhere else than the website, and I had not noticed. Look for the .sln path and then for the .vs (hidden) folder there.

Sentinel
  • 3,351
  • 27
  • 38
0

I'd the same issue on a WCF project on VS2017. When I debug, it gives errors like not able to get meta data, but it turns out the port was used by other process. I got some idea from here, and finally figure out where the port was kept. There are 2 places: 1. C:...to your solution folder....vs\config\applicationhost.config. Inside, you can find the site that you debug. Under , remove the that has port issue. 2. C:...to your project folder...\, you will see a file with ProjectName.csproj.user. Remove this file.

So, close the solution, remove the and the user file mentioned above, then reopen the solution, VS will find another suitable port for the site.

Huky
  • 11
  • 1
0

I'm using VS 2019.

if your solution has more than one project / class libraries etc, then you may not see the Web tab when clicking on Solution explorer properties.

Clicking on the MVC project and then checking properties will reveal the web tab where you can change the port.

Shaakir
  • 394
  • 4
  • 12
0

For old Website projects you will need to modify port in solution file, find section similar to below and change "VWDPort" property

Project("{E24C65DC-7377-472B-9ABA-BC803B73C61A}") = "My Website", "My Website\", "{871AF49A-F0D6-4B10-A80D-652E2411EEF3}"
    ProjectSection(WebsiteProperties) = preProject
        SccProjectName = "<Project Location In Database>"
        SccAuxPath = "<Source Control Database>"
        SccLocalPath = "<Local Binding Root of Project>"
        SccProvider = "Mercurial Source Control Package"
        TargetFrameworkMoniker = ".NETFramework,Version%3Dv4.7.2"
        ProjectReferences = "{41176de9-0c21-4da1-8532-4453c9cbe289}|My.CommonLibrary.dll;{f1fda4e5-0233-458e-97b8-381bdb38a777}|My.Ajax.dll;{e756176c-9cd1-4dac-9b2d-9162b7554c70}|My.WEB.API.Domain.dll;{7A94A6C8-595B-43CF-9516-48FF4D8B8292}|My.WEB.API.Common.dll;{790654F2-7339-472C-9A79-9E36837571A0}|My.Api.dll;{25aa245b-89d9-4d0c-808d-e1817eded876}|My.WEB.API.DAL.dll;{cc43d973-6848-4842-aa13-7751e655966d}|My.WEB.API.BLL.dll;{41591398-b5a7-4207-9972-5bcd693a9552}|My.FacialRecognition.dll;"
        Debug.AspNetCompiler.VirtualPath = "/My Website"
        Debug.AspNetCompiler.PhysicalPath = "My Website\"
        Debug.AspNetCompiler.TargetPath = "PrecompiledWeb\My Website\"
        Debug.AspNetCompiler.Updateable = "true"
        Debug.AspNetCompiler.ForceOverwrite = "true"
        Debug.AspNetCompiler.FixedNames = "false"
        Debug.AspNetCompiler.Debug = "True"
        Release.AspNetCompiler.VirtualPath = "/My Website"
        Release.AspNetCompiler.PhysicalPath = "My Website\"
        Release.AspNetCompiler.TargetPath = "PrecompiledWeb\My Website\"
        Release.AspNetCompiler.Updateable = "true"
        Release.AspNetCompiler.ForceOverwrite = "true"
        Release.AspNetCompiler.FixedNames = "false"
        Release.AspNetCompiler.Debug = "False"
        VWDPort = "3883"
        SlnRelativePath = "My Website\"
    EndProjectSection
    ProjectSection(ProjectDependencies) = postProject
        {C3A75E14-1354-47CA-8FD6-0CADB80F1652} = {C3A75E14-1354-47CA-8FD6-0CADB80F1652}
    EndProjectSection
EndProject
Yegor Androsov
  • 3,222
  • 1
  • 17
  • 28
-2

Edit .sln file using an editor like notepad.

Replace All Ports With New Port.

aDDin
  • 33
  • 3
  • This is a valid solution if you are using the old style Web Site Project (i.e. for ASP Classic files) in VS2019. You must edit the solution file because there are no other property pages. My project looks like this in the sln file. Project("{E24C65DC-7377-472B-9ABA-BC803B73C61A}") = "MyWebSitePrj", "http://localhost:50194", "{BC30BA4B-1D1D-48D0-B1E8-86CBD64611B5}" – Brad Irby May 30 '20 at 17:01
-6

Deploy your application in the IIS with the default port. Try to debug it using visual studio. It's a good practice. If you use visual studio, it will keep changing the port number most of the time. So better deploy the application in the IIS first and Open the same in visual studio and Debug it.

darkenergy
  • 93
  • 11
Wiki
  • 96
  • 1
  • 8
  • 2
    Dear Mark, I don't think you had read the question carefully! – Mohit Nov 10 '14 at 07:42
  • 4
    Additionally, it is not a good practice to develop directly against IIS. This MSDN article explains when you should use IISExpress, IIS, or an External Server when developing. https://msdn.microsoft.com/en-us/library/58wxa9w5(v=vs.120).aspx – Itanex Nov 10 '15 at 23:18