Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Microsoft Azure: Enterprise Application Development

You're reading from   Microsoft Azure: Enterprise Application Development Straight talking advice on how to design and build enterprise applications for the cloud

Arrow left icon
Product type Paperback
Published in Dec 2010
Publisher Packt
ISBN-13 9781849680981
Length 248 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Toc

Table of Contents (23) Chapters Close

Microsoft Azure: Enterprise Application Development
Credits
About the Authors
Acknowledgement
Acknowledgement
About the Reviewer
1. Preface
1. Introduction to Cloud Computing FREE CHAPTER 2. The Nickel Tour of Azure 3. Setting Up for Development 4. Designing our Sample Application 5. Introduction to SQL Azure 6. Azure Blob Storage 7. Azure Table Storage 8. Queue Storage 9. Web Role 10. Web Services and Azure 11. Worker Roles 12. Local Application for Updates 13. Azure AppFabric 14. Azure Monitoring and Diagnostics 15. Deploying to Windows Azure Index

Brief overview of the application


Our application has two purposes. The first purpose is to show the current status of an order. This is handled by selecting an order from the listbox and clicking a link to update a label with the selected order's status. This is done using our WCF web services by passing the OrderHeaderID to the web service and accepting the order status produced as output. The application will then update the label with the returned string.

The second purpose is to be able to update status for an order by selecting the order from the listbox, selecting the new order status for the order, and clicking a button to update the order. When the button is clicked, the OrderHeaderID for the selected order and the OrderStatusID for the selected status is sent via the web service and added to the queue for processing by our worker role.

How do our listboxes get populated? This is the third piece of our puzzle, and the answer to this, as you must have guessed based on previous chapters...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime