Back to description
The project for this book is based on a real application for a real company. The names of the company and the application... more
The project for this book is based on a real application for a real company. The names of the company and the application have been changed for privacy reasons. The fictional company name will be Smart Design, and the name of their new application will be called SmartCA. Smart Design is a growing architectural, engineering, and interior design firm. One of its many service offerings is construction administration, which in its case consists mostly of document management, cost control, and project portfolio management.
... less
Since I have decided that the application architecture will use a layered approach, it is time to create the Visual Studio... more
Since I have decided that the application architecture will use a layered approach, it is time to create the Visual Studio solution to host these layers.
Since I have just built the application architecture, it is time to start implementing the functionality of the application... more
Since I have just built the application architecture, it is time to start implementing the functionality of the application. Actually, the application architecture is not fully developed yet; in fact, I will probably refactor parts of it based on the needs of the application as I go along. In last chapter’s example of a View and a ViewModel, I introduced what I will be talking about this chapter, the SmartCA’s concept of Projects. I intentionally did not show you the Project class because that is the focus of this chapter. I will also be talking about the concept of Contractors and how they relate to Projects.
Project
Last chapter I showed how both Companies and Contacts were part of the Project Aggregate. Since the focus was on the Project... more
Last chapter I showed how both Companies and Contacts were part of the Project Aggregate. Since the focus was on the Project Aggregate, not much was done with these two Entities. This chapter, I will dive in and take a deeper look at the Company and Contact Aggregates, and I will show how they relate to the Project Aggregate.
In the last chapter, I took a deep look at Companies and Contacts, mainly because they are building blocks to be used in... more
In the last chapter, I took a deep look at Companies and Contacts, mainly because they are building blocks to be used in other parts of the SmartCA domain model. In this chapter, I will show what Submittal Transmittals are and how they also depend on Contacts, Companies, and several other classes in the domain model.
In the last chapter, I dove into some of the important domain logic for the SmartCA application by covering Submittal Transmittals... more
In the last chapter, I dove into some of the important domain logic for the SmartCA application by covering Submittal Transmittals. In this chapter, I will continue that trend by introducing another important new concept to the domain, the Request for Information (RFI). As you will see, the RFI is similar to a Submittal Transmittal in that they share a lot of the same classes: this will also prompt some refactoring.
In the last chapter, I covered the ins and outs of the Request for Information (RFI) document. In this chapter, I will cover... more
In the last chapter, I covered the ins and outs of the Request for Information (RFI) document. In this chapter, I will cover another concept that is similar to an RFI but has a different intent. That concept is the Proposal Request.
In the last chapter, I covered Proposal Requests, which must precede Change Orders in the construction industry. In this... more
In the last chapter, I covered Proposal Requests, which must precede Change Orders in the construction industry. In this chapter, I am going to cover the actual Change Order itself.
In the last two chapters, I covered Proposal Requests and Change Orders, and in this chapter I will be showing you the last... more
In the last two chapters, I covered Proposal Requests and Change Orders, and in this chapter I will be showing you the last of the Change Order–related concepts, the Construction Change Directive.
In Chapter 1, Introducing the Project: The SmartCA Application, I stated that one of the requirements for the SmartCA application... more
In Chapter 1, Introducing the Project: The SmartCA Application, I stated that one of the requirements for the SmartCA application was that it must be offline capable. Now, when I say offline capable, the best example that comes to mind is Microsoft Outlook. In Microsoft Outlook versions 2003 and above, you can work connected to or disconnected from your email server and still have a good user experience. During this chapter, I would like you to keep in mind how Microsoft Outlook works in order to understand some of the design decisions presented later in the chapter.
In the last chapter, I talked about synchronizing data with the server and how important it was to be able to work offline... more
In the last chapter, I talked about synchronizing data with the server and how important it was to be able to work offline. In this chapter, I am going to discuss how to implement membership features, such as authentication, in an offline scenario.
Purchase Before purchasing this product, please be sure you have met all software and system requirements, and that you understand any limits placed upon its use.
Return Policy Wrox Chapters on Demand are non-returnable and non-refundable.
Reader Software Wrox Chapters on Demand are offered as PDFs, and they must be viewed using the Adobe Reader. If you do not have the Reader installed, it can be downloaded for free at Adobe.com.
Test Download As Wrox Chapters on Demand purchases are non-returnable, it is advisable that you test your system and software configurations with a free sample download before you place an order.
Usage Rights for a Wrox Chapter on Demand File Any Wrox Chapter on Demand product you purchase from this site will come with certain restrictions that allow Wiley to protect the copyrights of its products. After you purchase and download this title, you:
If you have any questions about these restrictions, you may contact Customer Care at (877) 762-2974 (8 a.m. - 5 p.m. EST, Monday - Friday). If you have any issues related to Technical Support, please contact us at 800-762-2974 (United States only) or 317-572-3994 (International) 8 a.m. - 8 p.m. EST, Monday - Friday).
Related Books
.NET Resources