Going over the PhoneBook tutorial takes a couple of
days, because it is constructive. The tutorial is an
instruction of how to build the PhoneBook web application.
This walk-through is analytical. It explains how the
PhoneBook web application is built – in the hope that
it serves impatient people better.
As explained in the overview FIXME, the PhoneBook's
domain is very simple and easy to understand for
everybody who has ever used a paper phonebook.
- Person-s have one address - a Location - and
zero or more PhoneNumber-s - Person-s can share an address, but not a PhoneNumber
The words in italics are domain object classes
here, and together they constitute the domain of the
PhoneBook application:
LocationPersonPhoneNumber
As explained in PhoneBook project structure, three
sub-projects constitute the PhoneBook solution in
Visual Studio:
PhoneBook.Domain– the domain project with all
the domain's data and business logicPhoneBook.Sample– the sample project for
exercising the objects (or demonstrating their use)PhoneBook.Web– the web project (foundation
was laid byuigen.exe
PhoneBook.Web is the most elaborate project and
requires most of the work. uigen.exe derives a
bare-bones (but functional) web application from the
domain. What you are seeing in this project is the
"embellished" version. Such polishing and customizing
of a generated web app requires extra work.
PhoneBook.Domain -- learn to declare domain object classes
PhoneBook.Sample -- learn what makes domain object classes tick
PhoneBook.Web -- learn how to embellish the web application