Is this where I report an IISExpress 8 bug?
Last post Dec 05, 2015 04:53 AM by lextm
Dec 03, 2015 11:08 PM|TheCatcher|LINK
If a user's "My Documents" folder is on a network share, that doesn't support Folder Watches, IISEpress 8 exits when it attempts to start up. The exit occurs when it unsuccessfully attempts to instantiate a folder watch on its Config folder.
This bug results in this error message being displayed (in red) at the command prompt when IISExpress 8 is executed...
Error: Cannot read configuration file.
It also causes VS2013 projects that depend on IISExpress to fail loading with the following error message box...
Title: Microsoft Visual Studio
Creation of the virtual directory http://localhost:<PORT>/ failed with the error: Filename: redirection.config
Error: Cannot red configuration file.
My current work around is to relocate the "My Documents" folders from the network folder to local folders. This work around also causes the files in the "My Documents" folders, of all the programmers that work on the IISExpress 8 projects, to no longer
be backed up when the server is backed up.
Please let me know if there is already a fix, or if it will be fixed, and when.
Dec 04, 2015 06:56 AM|lextm|LINK
IIS Express reuses some of IIS code base. In that case, it should never expect its configuration file to reside on a network share (never in full IIS case). So I personally think it is by design and with a valid workaround like you discovered, it is less
likely to be fixed in any way.
Dec 05, 2015 12:23 AM|TheCatcher|LINK
Unfortunately the valid work around I'm currently using is in violation of our corporate policies. And I'm pretty sure when it is discovered that I've relocated my entire group's My Documents folders locally, I will be forced to move them back. With any
luck, we will finish this GUI project before they discover what I've done.
I agree 100% that IISExpress never expected (or should expect) its configuration files to be on a network share. But since relocating the My Documents folder to a network share is a fairly common practice in larger security conscious corporations, it would
be nice if there was a setting to allow the IISExpress config folder (or the entire IISExpress folder tree) to be located someplace other than in the My Documents folder.
Dec 05, 2015 04:53 AM|lextm|LINK
Since the default user home folder might like your case be at a network drive, Microsoft does add a registry key to allow a change,
But still, it requires related permissions and a local folder in most cases. So if your firm does forbid any of such changes, you will have to fight for a policy exception for developers, or they will have to give up IIS Express.