Programming Entity Framework - Cdn.oreilly.com

Figure 13-4. The two templates added by the ADO.NET POCO Entity
Generator and their generated classes
The POCO template creates fairly simple classes with all of their properties marked as
virtual, forcing them to use the DynamicProxy classes at runtime. Additionally, it adds
code to ensure that any foreign keys stay in sync with their related navigation property.
And finally, there is code in there to maintain two-way relationship fix-ups similar to
what you saw earlier in the chapter, although they use a class called
FixUpCollection which you’ll find in BreakAway.cs.
Example 13-11 shows the complete listing for the generated Payment class. Notice the
code in ReservationID which keeps the Reservation property in sync with the
ReservationID foreign key. Additionally, you can see the fix-up code that adds or
removes the Payment to the Reservation.Payments collection as necessary.
Example 13-11. The Payment POCO class generated using the POCO T4 template
//------------------------------------------------------------------------------
//
// This code was generated from a template.
//
// Changes to this file may cause incorrect behavior and will be lost if
// the code is regenerated.
//
//------------------------------------------------------------------------------
using System;
using System.Collections;
using System.Collections.Generic;