Book Image

Mastering LOB Development for Silverlight 5: A Case Study in Action

Book Image

Mastering LOB Development for Silverlight 5: A Case Study in Action

Overview of this book

Microsoft Silverlight is fully established as a powerful tool for creating and delivering Rich Internet Applications and media experiences on the Web. This book will help you dive straight into utilizing Silverlight 5, which now more than ever is a top choice in the Enterprise for building Business Applications. "Mastering LOB Development for Silverlight 5: A Case Study in Action" focuses on the development of a complete Silverlight 5 LOB application, helping you to take advantage of the powerful features available along with expert advice. Fully focused on LOB development, this expert guide takes you from the beginning of designing and implementing a Silverlight 5 LOB application, all the way through to completion. Accompanied by a gradually built upon case study, you will learn about data access via RIA and Web services, architecture with MEF and MVVM applied to LOB development, testing and error control, and much more.With "Mastering LOB Development for Silverlight 5: A Case Study in Action" in hand, you will be fully equipped to expertly develop your own Silverlight Line of Business application, without dwelling on the basics of Enterprise Silverlight development.
Table of Contents (19 chapters)
Mastering LOB Development for Silverlight 5: A Case Study in Action
Credits
Foreword
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Patterns


When developing business applications, it is normal to face considerable pressure to meet tight deadlines, as well as ever-changing functionalities. Our typical first reaction is to begin coding without having a pre-established design or plan. Although this approach normally bears fruit, it leads to the following situations:

  • Something that should have been a "disposable" prototype is gradually provided with more and more functionality and ends up being the final application

  • As the system grows, it gets more difficult to test the application, because the modules are coupled and they cannot be tested separately

  • We find everything mixed and a simple change in the UI forces us to modify code in the business logic or data

All these reasons justify a greater investment of time in the design of the application architecture.

Note

When is it worth using the "Code-Behind" approach?

When we are just developing some proof of concept or a quick prototype and we know that its code won't be reused for...