Date: Thu, 28 Mar 2024 12:42:58 +0000 (UTC) Message-ID: <891678519.1.1711629778491@5a19e4eb3f1b> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_0_1022550970.1711629778475" ------=_Part_0_1022550970.1711629778475 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Going over the PhoneBook tutorial takes a c= ouple of days, because it is "constructive". The tutorial is an instruction= of how to build the PhoneBook web appli= cation.
This walk-through is analytical. It explains how the PhoneBook web appli= cation is built =E2=80=93 in the hope that it serves impatient people bette= r.
As explained in the overview, the PhoneBook's domain is very simple and = easy to understand for everybody who has ever used a paper phonebook.
The words in italics are domain object classes here, and together they constitute the domain of the PhoneBook applicat= ion:
Location
Person
PhoneNumber
As explained in PhoneBook project structure,= three sub-projects constitute the PhoneBook solution in Visual St= udio:
PhoneBook.Domain
=E2=80=93 the domain project with all the=
domain's data and business logicPhoneBook.Sample
=E2=80=93 the sample project for exercisi=
ng the objects (or demonstrating their use)PhoneBook.Web
=E2=80=93 the web project (foundation was la=
id by uigen.exe
PhoneBook.Web
is the most elaborate project and requires mo=
st of the work. uigen.exe derives a bare-bones (but functional) w=
eb 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.<=
/p>
PhoneBook.Domain=
-- learn to declare domain object classes
PhoneBook.Domain -- relationships
PhoneBook.Sample -- learn what makes doma=
in object classes tick
PhoneBook.=
Web -- learn how to embellish the web application