azure-worker-roles

There are a million links like this one http://blogs.msdn.com/b/cie/archive/2014/01/24/windows-azure-remote-debugging.aspx , which more or less would seem to take care of the remote debugging setup. I have done this many times in VS 2013 Update 2, deployed, then attached to debugger and it simply does not work. Well, the debugger seems to attach, but I continually get the message when I hover over a break point informing me that 'The breakpoint will currently not be hit. No symbols have been loaded for this document' A while back I recall seeing a channel 9 presentation and they seemed to

I'm having a hard time understanding the RetryExponential class that is used in conjunction with QueueClients (and I assume SubscriptionClients as well). The properties are listed here , but I don't think my interpretation of their descriptions is correct. Here's my interpretation... var minBackoff = TimeSpan.FromMinutes(5); // wait 5 minutes for the first attempt? var maxBackoff = TimeSpan.FromMinutes(15); // all attempts must be done within 15 mins? var deltaBackoff = TimeSpan.FromSeconds(30); // the time between each attempt? var terminationTimeBuffer = TimeSpan.FromSeconds(90); // the

This may not be new, but I hope some one can put me on right track as its bit confusing during azure deployment. I'm in the process of planning for deployment on Azure. This is what I have A Public facing ASP.Net MVC app (web-role) + WCF Service (web-role) to be accessible only to this asp.net app + WCF Service (worker-role) again accessible to 1. over message-queue An Custom STS i.e. ASP.NET MVC app (web-role) acting as Id-Provider (for 1. which is a Relying Party) + WCF Service (web-role) to expose some of STS funcionality to RP's such as 1. SQL Azure: accessed by 1 and 2 Note: 1. will

I'm using the Worker Role machines (Medium -> 2 Cores with 3,5 GB of Ram) to do massive work, and I'm able to use 100% of the CPU (of both cores) and 85% of RAM. During this work, each takes around 20 minutes/ 40 minutes the Azure thinks the machine is unhealthy and stops all my work. In the Portal I see my worker instance are getting the message "Waiting for the status (Role cannot be reached by the host system). Can anyone know a work around that doesn't include: 1) Use a more power full Role with cores that I will not use 2) Try to reduce the CPU usage by my application (100% CPU usage is

As I understand Azure Worker roles run by the help of Host application called WaWorkerHost.exe and there is another application called WaHostBootstrapper.exe which checks if WaWorkerHost.exe is running and if not it will run the WaWorkerHost.exe . How often does this 'worker role status check' occurs? How can I quickly restart the Worker role myself? I can either reboot the machine worker role is running and wait for few minutes or chose the following traditional method: Taskkill /im /f WaWorkerHost.exe and wait for few minutes for the WaHostBootstrapper.exe to kick in but this very

I've setup a new worker role and setup a couple of new config transforms for it via SlowCheetah. When I build the project with one of the new configs selected, I do in fact see that configs folder get created underneath the \bin folder as you would expect (for ex. \bin\Production). When I package a cloud service for deployment using one of the new configs, my web projects get their configs transformed appropriately but my worker role (which is just a library) does not even though I see underneath the \bin folder an updated \bin\production. It would appear the azure packaging tooling is