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

JupiterMotorsERP local application


Adding our local application to the solution is very simple. Right-click on our solution, and choose Add | New Project....

Under the project type Windows, select Windows Forms Application. Name the project as JupiterMotorsERP and click OK.

This will create a Form1.vb file and an app.config file. The Form1.vb will be our form design and code, whereas the app.config will hold any settings we wound need for the application.

As the first step toward setting up our local application, we're going to build the design of our form. We need the following:

  • Two listboxes named lbOrdersNotComplete and lbOrderStatuses

  • A label named lCurrentStatus and another named lMessage

  • A link button called lnkUpdateCurrentStatus

  • A button called btnUpdateOrderStatus

Our sample application form now looks like the following screenshot:

It's going to be a little tough for us to code our Windows Forms application to use our web services, as we haven't yet told the project where we're...

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