| Today was a recap of many of the central concepts you've covered throughout this book. The most important part of today's lesson was that you learned how to assemble the various parts of ASP.NET to build a complete application. Another important concept you examined today was using good design skills before even beginning development. This is an essential step that makes future development much easier. Initially, you took the requirements from BananaMobile, Inc. and transferred them into technology requirements. Just from the knowledge that the company wanted an e-commerce site, you knew you needed several database tables, a registered user base, several different business objects, and the ASP.NET pages to control it all. You laid out each of the three tiers of the application, starting with the database back end and ending with the business objects in the middle tier. This logical process allowed you to see what functionality was required, with a minimum of backtracking. Note This method, certainly, is not the best method all the time. Certain situations might demand other processes, but the method demonstrated today is good for general use.
Next you started developing the site. Again, you started with the database back end, and assembled all the tables and stored procedures required by your application. You already knew much of what needed to be accomplished from the design phase. When this tier was done, it was an easy process to build the business objects that interacted with the databases and executed stored procedures. Many of the business objects' method executed only stored procedures, although some required a few more advanced steps. Developing the ASP.NET pages was also an easy step because of what you had already built. The UI often takes the longest to build, but with the aid of templates, user controls, and server controls, it went by rather quickly. Much of the ASP.NET code you developed called on the business objects to do the grunt work, so coding these pages was easy. Finally, you looked at building a secure Web Service. Although the functionality inside the service was rather simple, the addition of SOAP headers and authentication methods made it more complex. Even so, the development of the service was not overly complex or difficult. Tomorrow, your last day in your adventures in ASP.NET, studies mobile forms. These are part of the Web forms framework, but allow your pages to be displayed on any Web-enabled mobile device, such as cell phones or PDAs. You have to build only one page, and it will work with all these devices. See you then! | 
