Geeks With Blogs

CloudCasts Blog Webcasts in the Cloud

The November 2011 release expands on the Service Bus brokered messaging content to provide more details of the features. Deadlettering and message expiration are covered, along with message deferral, duplicate message detection, message correlation and sessions.

Get it here.


Posted on Tuesday, November 8, 2011 9:26 PM Oslo , BizTalk , Azure , WCF/WF , VS2010 , AppFabic | Back to top

Comments on this post: The Developer's Guide to App Fabric November 2011

# re: The Developer's Guide to App Fabric November 2011
Requesting Gravatar...
Hi, I read your book and it is very helpful. I understand it is still work in progress and one topic which is most interesting to me is still missing. On page 94 you mention the three techniques used for receiving messages. There is no example yet for a transactional receive. The issue I am struggling with most moving to Azure is the transaction control. In a Windows Server environment you would just use a MSMQ and the database updates within one transaction, but SQL Azure does not support distributed transactions. So even if the queue supports transactions, a transaction enclosing both committable objects would not work.
How would you implement an "Exactly Once Delivery" scenario with transaction control that updates a SQL Azure table?

Left by Alex on Dec 31, 2011 7:47 PM

# re: The Developer's Guide to App Fabric November 2011
Requesting Gravatar...
First, thanks Alan for all the effort to provide this guide, I find it really useful.

As a feedback, on first walthrough for creating an application that send an receive a simple brokered message, as a newbie I'm, I found litle bit confusing getting all the credentials in the right place.

My problem was specifically with the AccountDetails' property Name, I eventually realized that is the Issuer from the Azure Management Portal bus property.

Left by Danfer Habed on Jan 06, 2012 3:48 PM

Your comment:
 (will show your gravatar)

Copyright © Alan Smith | Powered by: