Windows Azure Developer Task Four: Error mounting debugger in Windows Azure SDK 1.3
I installed the 1.3 version of the Windows Azure SDK. I tried to create an azure "Hello World" application.
I pressed "F5" and I got the following error:
I tried "press", and I didn't get the above exception without using the debugger, but in the browser I got the Service unavailable error.
I've found some discussion here about this particular anomaly: http://int.social.msdn.microsoft.com/Forums/en/windowsazuredevelopment/thread/ 45e01c3d-7c16-4ca7-999b-46cb20b38c1d
Alternative solution 1:
The first recommendation is to check for two "V4.0" folders under the "C:\Windows\Microsoft.NET\Framework64" folder. I checked, and I found that I had only one folder called "v4.0.30319", so this recommendation does not apply to the situation I have encountered.
Alternative Solution 2:
The second recommendation is to open a command prompt and then run the Aspnet_regiis.exe–r command. I tried again, "tragedy" again.
Alternative Solution 3:
The third suggestion is to change the target framework from v4.0 to v3.5. I did, and "tragedy" once again came to my head.
Alternative Solution 4:
The fourth recommendation is to remove the "Sites" node from the "Servicedefinition.csdef" file. Unfortunately, "tragedy" fell on my head again.
<Sites>
<site name= "Web" >
<Bindings>
<binding name= "Endpoint1" endpointname= "Endpoint1"/>
</Bindings>
</site>
</Sites>
Alternative Solution 5:
The fifth option is to test if a normal Web application with a target framework of 4.0 can be successfully published in IIS. I tried, and I could successfully publish the Web application in IIS. So my IIS is fine.
I completely despair, and then restarted the system, the miracle appeared, incredibly all normal, I did not see that debugger abnormal. I don't know what happened, but this is my experience in dealing with this popular anomaly.
Original name: Windows Azure for Developers Task4:error attaching the debugger in Windows Azure SDK 1.3 Author: Dhananjay Kumar