-
Book Overview & Buying
-
Table Of Contents
Mastering LOB Development for Silverlight 5: A Case Study in Action
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.
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...
Change the font size
Change margin width
Change background colour