I am trying to start developing some modules for a new site and have setup a DNNdev.me site using 7.4 on my Windows 8.1 system.  It works fine and I can use Visual Studio just fine with it until I put the system to sleep or restart it.

The only thing displayed is a screen that states DNN error with a button that says "Return to site." 

There is nothing remarkable in the IIS log; it appears that the site binding is working properly.  There are 14 PAGE_LOAD_EXCEPTION entries in the EventLog table for the site but I am not able to make any sense of these beyond that.

Hopefully I am just missing something obvious.  I would appreciate any pointers about how to get my development site to actually work for more than once in a row. 

Thanks for any advice or pointers!

Thank you, Sebastian. I don't believe there is latency at that level in that I have other DNN sites on the system and they all operate happily. It is only the development site at DNNdev.me that exhibits this one-time-only operation.

My guess is there is some loss or latency at the IIS and binding issues but I fail to see any evidence of it. I was not sure I had the bindings correct but given that they work on the initial install and execution of Visual Studio it would seem they were right.

The IIS bindings SEEM to be working in that I can see the connections in the IIS logs and the fact that I am seeing the PAGE_LOAD_EXCEPTION entries in the EventLog. The Exception table entries for theses says "The file '/DesktopModules/DDRMenu/Menu.ascx' does not exist." The file does exist and the top level is the home directory of the dnndev.me site in IIS.

This made me think there might be some permission issues but all the files in the directory tree are owned by the IIS account. In an attempt to bypass any sort of permission I add all users to have complete access but the error persists. I then made one of the administrator accounts the account for the site.

Still no joy.

I doubt the Hosts entry will change the behavior but can try that. Does that entry just go to the loopback IP of 127.0.0.1 or is there something to cause this to point to the actual folder used?