Thursday, December 27, 2012 3:07 PM
I've created a new project using the provided wizard but my breakpoints are disabled at runtime when starting the WebRole in the compute emulator. Are there any trouble shooting tips for this?
Wednesday, January 02, 2013 2:11 PMOwner
This usually happens when your source is out of date with the debuggee binary - for example, you've made a change in the code but didn't rebuild the project, or the binary you're debugging is different from the one you just built. I suggest looking at the debugger's Modules window and making sure you're loading the same DLLs that you built.
Artur Laksberg Visual C++ Team Microsoft
Wednesday, January 02, 2013 11:59 PM
Debugging with the WebRole used to work automatically with our Visual Studio wizard however we have regressed it at some point. Debugging has never automatically worked with the WorkerRole in our wizard.
To debug with the WorkerRole you need to attach to the WorkerRole process spawned (CasablancaHost110.exe) with 'Tools' -> 'Attach to Process...'
To debug with the WebRole you will need to attach to the IIS worker process instance. It will be called w3wp.exe.
Sorry about the pain here, but right now our main focus is on getting the client side libraries of Casablanca out open source and then a supported release. We won't likely be able to fix this for a little while. Let us know if you have other feedback or hit any issues.
Thursday, January 03, 2013 12:15 AM
I should have mentioned, but if you just do your debugging by pressing F5 you will be running locally using our CasablancaHost110.exe which will automatically have debugging and everything setup for you. You won't be running in Azure, but I recommend you do your first round of debugging outside of Azure if possible.