Disable Ping Timeout in IIS Express? - iis-express

There are a million and one google hits explaining how to disable the ping timeout in IIS (which annoyingly interrupts debugging), which all give this information:
https://msdn.microsoft.com/en-us/library/bb763108.aspx
But how do we do this on IIS Express?
(There does not seem to be a configuration interface for IIS Express)

IIS Express does not honor application pool settings except ASP.NET version. So even if you change this setting in config file it won't take effect. That's probably why nobody talks about it.
Meanwhile, if you want a configuration interface similar to IIS Manager, here comes Jexus Manager,
http://jexusmanager.com

you need to modify the applicationHost.config for your instance of IIS Express.
Clicking on the IISExpress Icon will help you find the config file. For my personal dev/test I use
If you are using the Azure Compute Emulator, the applicationHost.config will change with each local deployment. For that you will need to modify C:\Program Files\IIS Express\config\templates\PersonalWebServer\applicationHost.config.
That file will be copied on each deployment.
Good luck.

Related

Launching localhost on IISExpress: The remote device or resource won't accept the connection

I tried using IISExpress to launch my web projects in Visual Studio 2015. I have both a RESTful service project and a front end website. Neither one will launch and after drilling into the diagnostics in Internet Explorer I find the error message
The remote device or resource won't accept the connection.
I have tried resetting Internet Explorer and there is no proxy server that might be interfering with the connection.
A) Check to make sure that IISExpress is running. First, start your project in Visual Studio, then click the Start button and search for 'Resource Monitor'. Expand the 'Network' section and look for IISExpress. You could also use Ctrl-Alt-Delete and choose Task Manager to see whether IISExpress is running. If it's not there then there is a problem with IISExpress and it's not even running. In this case you can work around the issue by configuring the web project to run in IIS.
Make sure IIS is set up on the machine
How to enable IIS on Windows
Configure Visual Studio to use IIS to run the web project
Use Local IIS as a Web Server in Visual Studio
B) Check the version compatability of IISExpress with Visual Studio. IISExpress 10 does not work with VS 2017, for instance.
C) There are any number of reasons why IISExpress night not be starting
IISExpress Troubleshooting on Stackoverflow

Can you prevent Visual Studio 2013 from starting all web sites in a solution when using IIS Express?

Is it possible to configure IIS Express to not run all the web sites in a given solution? I have a solution with 4 web sites and I only want IIS Express to run 2 of them when I hit Start (F5) in Visual Studio 2013. I have the solution set to only start 2 of them, the other 2 are set to None.
I went into the IIS Express config file and created a new app pool with autoStart="false" and assigned this new app pool to the sites that I do not want to run. I also set the serverAutoStart attribute to false in the site tags, that I don't want to run. These changes didn't make any difference. The IIS Express tray interface still shows all 4 sites as running. (Yes, I shut down Visual Studio and made sure all the iisexpress processes were dead, before restarting.)
Yes you can,
By default all sites has a property called "Always start when debugging" set to True
setting this property to false will allow starting only the specific site you choose to debug.
Try using the Disable Always Start When Debugging VS add-in tool.

How do I debug my server side code in an SSL environment?

I'm writing a Silverlight application and I'm wanting to debug my custom UserNamePasswordValidator. Since the validator requires SSL (for good reason), I cannot figure out how to debug it. I can't seem to use SSL against the ASP.NET Developement Server associated with Visual Studio 2010. Since it is server sided, I can't attach Visual Studio's debugger to the process. How on earth do I debug this thing?
Thanks.
Suggest trying IIS Express, which can utilize SSL and/or localtest.me (which has ssl cert for download).
You can attach the VS debugger to IIS. Select Debug, Attach to Process, check Show all processes, attach to w3wp.exe. (VS must be running elevated.)
If you want to look at the HTTP communication between your app and the server, Fiddler will allow you to do that. Read the docs about HTTPS decryption to get started.
Yes, IIS Express can be configured to be the default web server for a web project in VS 2010 SP1. It is on the Web tab of the site project's Properties page, under Servers:
Right-click project, select Properties. Select Web tab. Select 'Use Local IIS Web Server' Check Jason Shaver's blog for details on updating applicationhost.config (in User\Documents\IISExpress\config):
I had to change the Project Url field on that Properties tab to the value identified in applicationhost.config in order for Debug/F5 to run in SSL.
Just started playing with this, so I don't know if you can set this VS-wide instead of project by project.

IIS Express Web Server - (Every) Port is in Use?

Today I installed VS2010 SP1 Beta, and IIS 7 Express, as I currently have IIS5 on my local development machine and thought I'd try IIS Express out.
I have gone into the properties window for my Web Application, checked the 'Use IIS Express' checkbox, created the Virtual Directory when it has prompted me, but then get the message "Unable to launch the IIS Express Web Server. Port x is in use".
I have tried changing the port number from the default value that was in there, to numerous other port numbers, but whatever value is there, I am always getting this message, and am therefore unable to use the IIS Express Web Server.
Does anyone know what the problem might be, and how to get around it?
If you are using ESET NOD32 Anti Virus, you need to change the setting of "Web access protection" => HTTP, HTTPS => Web browsers => red cross the check box of your devnev.exe (This is three state checkboxs, click the check box until red cross appeared)
I have just installed VS 2010 SP1, using the above setting to tell NOD32 to leave 'IIS Express' alone.
Reference: http://weblogs.asp.net/anasghanem/archive/2009/02/01/nod32-antivirus-is-blocking-visual-studio-built-in-development-server.aspx
What version OS are you using?
Are you able to start IIS Express from command line? Could you try the following and post the error message you are seeing.
Remove IISExpress directory located under 'My documents' folder
Go to IIS Express installation folder '%programfiles%\IIS Express' (on 64-bit machine '%programfiles(x86)\IIS Express') and try to start iisexpress.exe from command line (without passing any arguments)
I had a similar problem. It seems that if IIS Express is already running a particular site and then you try to run a project that uses that site through Visual Studio it isn't able to attach the debugger. The solution was to close any running instances of IIS Express and WebMatrix and then try running the site through Visual Studio (F5).
I recommend installing WebMatrix as it's the simplest way of managing the sites and port numbers that you are using.
I have the same problem in the visual studio 2012.
I am creating a sharepoint app for the SharePoint 2013 and it happened after some days means it was working before then I got the error:
" Unable to Launch IIS web Server " "port 62308 in use.
To fix this I just went to the settings of the web project by right clicking on the project node in in right panel under the project solution tab. Change the port number and configure the virtual directory and it worked for me.
Hope it work for anyone else in case he/she has any problem.
1- Close Visual Studio.
2- Delete IIS Express folder in Documents or edit applicationhost.config:
<bindings>
<binding protocol="http" bindingInformation=":8080:localhost" />
</bindings>
3- Delete solution file.
4- Start Visual Studio and use open website.
5- Choose your website folder.
If any body still facing the same issue ... even after trying all the above steps
try the following simple steps...
1) close all other applications
2) Download TcpView application from
http://technet.microsoft.com/en-gb/sysinternals/bb897437.aspx
3) run the application, check the localport column and see who is using that specific port
and end that task
That will solve your problem ... :)
go to solution explorer, right click on the present Application then go to properties, now click on web scroll the mouse and change the port no. from project localhost:1257
NOW RUN IT...

Unable to use IIS7 with Visual Studio 2010, MVC2.0 and NET4

Here is my environment
Windows7, Visual Studio 2010, MVC2.0 and NET4
My default web site is configured to use ASP.NET v4.0 application pool.
Here is an easy way to reproduce my problem
Create a new MVC2 application
Open the properties Window
Go to the Web tab
Check "Use IIS Local Web Server"
Click on "Create Virtual Directory" button
I get this error message
To access local IIS Web Sites, you must install the following IIS components:
In addition, you must run visual Studio in the context of an Administrator account
For more information, press F1
Notice the blank line after "...the following IIS components:"
I am running VS2010 as administrator
Pressing F1 does not bring any help
I checked my Windows eventlog files and found that my metabase was corrupted
(I thought we get rid of this in IIS7 but it looks like it is still here...)
I used this Microsoft article to restore it from an old version and now everything is working
Hope this can help somebody else
Have you tried running VS as administrator?
Right click your VS shortcut and select "Run as Administrator"
I had the same error message, in my case with VS2008, Windows 7 + IIS7, when trying to add an existing web site to a solution. I think this is one of those error messages where what it states can be a big red herring, i.e. it doesn't necessarily have anything to do with running as an administrator or not having components installed.
In my case, the web site had an HTTP binding in which the hostname was set to "localhost". Once I cleared that, it worked fine. Don't ask me why I put "localhost" in there, it just seemed to make sense at the time.
My internet hunting also turned up this brief entry, which did not work for me.

Resources