c#,json,azure,asp.net-web-api,windows-azure-queues
You could simply serialize your object using Json.Net by doing something like: var serializedData = JsonConvert.SerializeObject(message); var msg = new CloudQueueMessage(serializedData); queue.AddMessage(msg); ...
azure,azure-webjobs,windows-azure-queues
From your question, I understand you have 2 queues and each queue needs to be used to process different tasks/jobs. You can follow these approaches 1) Deploy 2 Web jobs, each wait on different queues and trigger corresponding job whenever a message appears on respective queue. The config code you...
c#,azure,windows-azure-queues,azure-eventhub,lambda-architecture
This falls into the category of question whose answer will be much more obvious once the source for EventProcessorHost is made available, which I've been told is going to happen. The short answer is that you don't need to use a queue; however, I would keep the time it takes...
lucene,lucene.net,windows-azure-queues
The IndexWriter is thread-safe, it's safe to call from different threads. It's okay to never call optimize. (You could write a custom merge policy if the default doesn't work for you.) You will flush all documents to disk by calling commit. There's no need to dispose of your writer....
azure,windows-azure-storage,windows-azure-queues
When Azure Queue messages re-appear, they don't necessarily get sent to the end of the queue. They just reappear, and at that point, no real guarantee of order. It doesn't even get moved from its current position; it's just visible again. Azure storage queues aren't set up for guaranteed order....
asp.net-mvc,razor,polling,windows-azure-queues
Azure has two types of queues - Azure Queue and Service Bus Queue. Although in theory you can access them from client side (I assume JavaScript) because CORS has been introduced some time ago (Not sure about CORS support for ServiceBusQueue), this might not be the best option. Problems you...
c#,azure-webjobs,windows-azure-queues
The SDK should already handle that. As you stated, the message will be leased (or become invisible) for 30 seconds by default. If the job takes longer than that, then the lease will be renewed. The message will not become available to another instance of the function unless the host...
windows-azure-storage,azure-media-services,windows-azure-queues
Just run verification test ShouldReceiveNotificationsForCompeletedJob from https://github.com/Azure/azure-sdk-for-media-services/blob/dev/test/net/Scenario/JobTests.cs which verifies notifications workflow. Test is passing in US WEST data center. Please note that job notifications through azure storage queue are not designed to be real time and as you can see there is few minutes delay between messages appears in queue....
c#,azure,azure-worker-roles,azure-webjobs,windows-azure-queues
Finally I find a simple solution. Before running my job of several hours, I launch a task KeepHiddenMessageAsync that update the message with the timeout. Before the end of the timeout a new update of the message is done. If an problem occur then the timeout of the message will...
.net,exception,windows-azure-queues
I'm guessing here, that receiveAndDelete means "Won't continue until a message has been received", so basically your program is waiting to receive a message from the queue. Are you sure there is any messages in your testqueue? You can't always trust the azure portal in this regard, so try adding...