Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post May 18, 2012 09:38 AM by sachinasp.net
May 06, 2012 11:25 PM|LINK
Hello all. Having some issues here. I am trying to run in Debug mode for my Azure project. It gives me a permissions error. Ive already went to the folder and upped all the permissions for Network Service etc. The hosted service is already published to the
Azure. Is that why its giving me an error?
When I right click the project and run debug it works fine in local debug mode. But I guess I can't debug in the Azure emulator, which is the point of having an Azure emulator.
I feel as though I am fundamentally misunderstanding something here. Anyone have some thoughts? This worked fine yesterday, not sure what has changed.
May 06, 2012 11:58 PM|LINK
So I have done some further research and have found this...
Debugger Does Not Attach to Role to be Debugged!
This seems to be the issue I am having. Using the debugger, I fail to start my application in the Windows Azure Compute Emulator. The error I get says I dont have access to that file.
Resolution: Use CSrun with /launchDebugger parameter of the /run option. For more information on CSRun, see
CSRun Command-Line Tool.
You can also use Microsoft Visual Studio to debug your role instance.
I have no idea what they are talking about. This seems like an annoying task that I don't want to deal with everytime I want to debug my application in the Azure emulator.
Any help out there?
May 18, 2012 09:38 AM|LINK
Just do one thing, While running your application in visual studio go to Tools => Attach to Process.
Check the following checkboxes:
1) Show processes from all users
2) Show processes in all sessions
then check whether following processes are already attached or not:
a) iexplore.exe Script
b) w3wp.exe ProteousDebugEngine, Managed
c) WaIISHost.exe Managed
if not then attach them.
Also go to run => type inetmgr to open IIS manager.
Click on Basic Settings => Edit Site window will appear => Click on Test Settings => check things are ok or not => if not, click on connect as => give your administrator credentials=> click test settings.
Now It should work..