Download Source Code
Each project in the solution represents a tier in the application. Having separate tiers allows you to isolate the changes without affecting other tiers. The diagram below shows you the flow of information among the tiers.
- UI tier
- View -- These are the xaml for showing the UI.
- ViewModel -- These are objects that are used to bind to the Views. These objects are not used to represent the business model. They are built to support the binding to the view. You will see that the objects in the ViewModel and the Business tier (which represents the business model) are structured differently.
- Service tier -- Serves the objects for others to consume. You can build other projects that uses this service.
- Business tier -- Designed to represent the business model.
- Data tier-- Maps the data in the database into objects and serves the objects to the Business tier.
Next we will see how the Data tier is designed to allow flexibility.
Future series of articles on sharepoint:
- sharepoint list -- the concepts of sharepoint list and how to effectively manage it
sharepoint version control -- the internals of sharepoint version control and how to administer and manage the versions
sharepoint permissions -- how to manage the permissions in a large enterprise sharepoint environment
sharepoint server farm -- how to set up a high availability sharepoint server farm
sharepoint document library -- the details on how to get your ways around the document library in sharepoint
sharepoint configuration -- the configurations needed for different sharepoint network scenarios
sharepoint css -- making the most out of customizing sharepoint frontend
sharepoint web services -- some of the most convienent ways to communicate with the internals of sharepoint