Errata

The text says 'Example 11-19 leverages the System.String.Format method...'

It is example 11-20 that uses this method.

Note from the Author or Editor:
correct. it's 11-20

In the New Page Class of the diagram, it reads "Instaniate Databridge" but should read "Instantiate Databridge."

Note from the Author or Editor:
typo...add a "t" if we ever reprint this book

Reading the Kindle version.

In the sentence...

If you don't fit into either group, MSDN defines it's DbCommandTree class as "an abstract class..."

"it's" should be "its", no apostrophe.

Note from the Author or Editor:
sure

The hyperlink to the MSDN documentation for the timestamp/rowversion definition seems to include the '):' at the end of the line. It should just be up to the '.aspx'.

Note from the Author or Editor:
this sounds familiar. maybe a duplicate.

Starting with the second sentence the author states:
"The ReservationDate was formatted using the Designer. I have demonstrated both ways ...".
The author never demonstrated formatting the ReservationDate through the designer.

Note from the Author or Editor:
replace "I have demonstrated" with "I used"

In Example 17-9, the line:

var customer = CustomerUpdate.Customer;

should read:

var customer = customerUpdate.Customer;

The error is on page 466 in the PDF edition.

Note from the Author or Editor:
change as per submission, thanks

Code in test method GetPaymentStatusTest() has some minor typos.

This line:

Reservation target = new Reservation.PaymentStatus();

should be replaced with:

Reservation target = new Reservation;

And also method PaymentStatus() in Reservation class doesn't exist but GetPaymentStatus() does.

Note from the Author or Editor:
please change to:

Reservation target=new Reservation();

(note for errata submitter...PaymentStatus is the enum in this case because it is declared inside of the Reservation class)

Make the following change (related to the updated figure 14-14).


Change:

"Set up the association"

To

"Set up a 1:1 association between Address and AddressExtra"

Typo: "For now, remember that the view comes into the model as an entity and if the view is not UPDATABALE..."

It should say "updatable"

Note from the Author or Editor:
fix typos: updatabale to updatable

The FunctionImportName should be "GetContactsbyState" rather than "ContactsbyState"

Note from the Author or Editor:
please change as per submission

Regarding the Customers table listed in Chapter 8 page 173; CustomerTypeID has been truncated to CustomerType, Notes and RowVersion are not included.

Note from the Author or Editor:
will email a new copy of figure 8-3.tif

The DisplayMemberPath and SelectedValuePath attributes refer to the properties of the list of lodgings to which you bound the ComboBox in code. SelectedValue gets the LodgingID from the currently selected trip in the ListBox.

Should be :

The DisplayMemberPath and SelectedValuePath attributes refer to the properties of the list of DESTINATIONS to which you bound the ComboBox in code. SelectedValue gets the DESTINATIONID from the currently selected trip in the ListBox.

Note from the Author or Editor:
yes do this but note that the all caps are not necessary. Destinations and DestinationId

In the VB version of example 4-28
add.Contact.FirstName
should be
a.Contact.FirstName

In the last sentence:

"I've debugged into the customers variable (a List<Customer>) in Page_Load"

the last word should be Form1_Load, not Page_Load

At the start of the paragraph the word When is repeated:
"As you saw in Chapter 6, whenWhen you query data ..."

This sentence is only partially correct: "If the update or delete stored procedure requests the rowversion as a parameter, you can force the original value to be used by checking the Use Original Value option".

The Use Original Value option is available for an update stored procedure, but not for a delete stored procedure

Note from the Author or Editor:
Change to:
If the update stored procedure requests the rowversion as a parameter, you can force the original value to be used by checking the Use Original Value option.

Typo - "Select the Asscoation between Contact and Address." should read "Select the Association between Contact and Address".

Note from the Author or Editor:
please fix as noted

..,which implements DbDataReader
should be inherits from DbDataReader

Note from the Author or Editor:
yes, please fix

In the 2nd last line of the 2nd Paragraph, the URL for EF design blog (http://blogs.msdn.com/efdesign) has been put instead of EF Team blog URL which is: http://blogs.msdn.com/b/adonet/
It should be reads as:
"I recommend following the Entity Framework team?s blog (http://blogs.msdn.com/b/adonet/) for..."

Note from the Author or Editor:
modify the sentence to read:

I recommend following the Entity Framework team?s design blog

(adding the word "design". Do not change the url.)

Where it reads:
"Speaker and Session both have identity names that fit the convention, so it is not necessary to use the HasKey property."
Like it mentioned earlier in this page, HasKey is a method and not a property so the above line should read as:
"Speaker and Session both have identity names that fit the convention, so it is not necessary to use the HasKey method."

Note from the Author or Editor:
yes change "property" to "method"

Where it reads:
"code first uses either declaritive attributes or a a fluent configuration on top of specific patterns to infer..."
First there is duplicate "a" in there just before "fluent" word. Also this "fluent configuration" phrase is kind of confusing. It sounds like a configuration thing (e.g. data annotations or a config file) while it refers to the Code First Fluent API. I would suggest to change it to "Fluent API" instead which is well known and also widely used by EF team.

Note from the Author or Editor:
please remove redundant "a"

cust.ReservationsToDelete

should be

customerUpdate.ReservationsToDelete

Note from the Author or Editor:
as suggested should be customerUpdate.ReservationsToDelete

Darn I thought we caught this already but I'm seeing it in 2nd printing so it might have been in another example :(

The last line of the code reads as:
con.Addresses.Add(address);
However, the contact variable has been declared in the first line as:
var contact = (from c in context...
So the last line should be read as:
contact.Addresses.Add(address);

Note from the Author or Editor:
please change last line of example 19-10 as suggested

contact.Addresses.Add(address);

4th line from the bottom of the page reads as:
"When you execute a query that returns addresses, the ContactID from the Addresses table is used to..."
According to the database schema on page 167, shouldn't that be "Address table" and not "Addresses table"?

Note from the Author or Editor:
okay change that to Address table

The 4th line of the 2nd Paragraph reads as:
"The pseudoentities hiding in the danglingForeignKeys property were created during the query..."

_danglingForeignKeys has been declared as follows on ObjectStateManager class:
private readonly Dictionary<EntityKey, HashSet<EntityEntry>> _danglingForeignKeys;
So it's a field and not a property, also the underscore on _danglingForeignKeys is missing, therefore, the above line should be read as:
"The pseudoentities hiding in the _danglingForeignKeys field were created during the query..."

Note from the Author or Editor:
okay change the word property to field and put the underscore in front of dnalgingForeignKeys

Fourth Line of the first Paragraph reads as:
"recommendation is to use the OnDelete action in the *database* as a reflection of its definition in the database."
Since OnDelete Action is referred to EF's EDM, it should be reads as:
"...recommendation is to use the OnDelete action in the *model* as a reflection of its definition in the database."

Note from the Author or Editor:
yes, please replace the first instance of database with model so that sentence reads:
The recommendation is to use the OnDelete action in the model as a reflection of its definition in the database.

The 3rd line of the last paragraph reads as:
"...The Customer inherits from Contact and maps to Customer and ContactDetails."
As per page 376 and also the source code for the chapter, Customer is mapped to Customer and ContactPersonalInfo and NOT to ContactDetails. So the above line should be read as:
"...The Customer inherits from Contact and maps to Customer and ContactPersonalInfo."

Note from the Author or Editor:
please fix sentence as suggested

context should be _context

Note from the Author or Editor:
1) pls make suggested change
2) same for code sample in middle of page 223. Add underscore in front of trips (we've got this one in a separate errata) and in front of context.
_trips=_context.Trips.Include("Activities")

The printed code snippet omits the leading underscore from the class variables (trips should be _trips and context should be _context).
Also the 'OrderBy' method is missing its Lambda; "it.Destination.Name" should be "t => t.Destination.Name"

Note from the Author or Editor:
Add undesscore to first trips as shown in the following code snippet:

_trips = context.Trips.Include("Activities")
.OrderBy("it.Destination.Name")
.ToList()

Ignore the 2nd suggestion. The code is using a query builder method, not a linq method so the contents of the OrderBy are correct.

Please add the parentheses to FullNameReverse as shown here:

from c in context.Contacts orderby c.FullNameReverse() select c

Just a little typo on the first code snippet where it reads as:
"ChangeObjectState(cust,System.Data.EntityState.Modified);"
"cust" needs to be change to "customer" since the code snippet starts with:
"switch (customer.State)"
so it should be changed to read as:
"ChangeObjectState(customer,System.Data.EntityState.Modified);"

Note from the Author or Editor:
crap - he's right. Change

"ChangeObjectState(cust,System....."

to
"ChangeObjectState(customer,System....."

The query inside GetCustomer(int customerId) method has a predicate that reads:
"where c.ContactID == custID"
Given that the method's parameter has been named "customerId", the above needs to be changed to read as:
"where c.ContactID == customerId"

Note from the Author or Editor:
please change " == custID" to " == customerId" as suggested.
thanks

Change:
"Use SELECT VALUE when projecting more than one type."

to

"Use SELECT when projecting more than one type. Do not include the VALUE keyword."

Change:
"When querying with SELECT, the ObjectQuery type must be a DbDataRecord."

to
"When querying with SELECT (without the VALUE keyword), the ObjectQuery type must be a DbDataRecord."

o typo: ExecuteCommand should be ExecuteStoreCommand

Note from the Author or Editor:
They should be ExecuteStoreCommand

o typo: all other examples of the UpcomingTripParticipant use a WHERE condition of LESS than or equal to 7; however, this snippet used GREATER than or equal to 7. Discovered this using LINQPad and results returned many more than expected.
o solution: change LESS than or equal to 7 to GREATER than or equal to 7

Note from the Author or Editor:
The fix to make is on p. 436 (I'm looking at the PDF). At the top of the page there are 5 lines of code. the third starts with "WHERE DATEDIFF" and towards the end says ">=7". Change that to "<=7"

o Our model imported three db views.
o typo: 'two' should be 'three'
o typo: '...you already have two definingQuery...'
o solution: two should be three.

Note from the Author or Editor:
Change the word two to the word three in the phrase "you already have two DefiningQuery elements."

o type: the 'f' in PaymentsforContact should be 'F'
o List<TripPayment> payments = context.PaymentsforContact(569).ToList();
o solution: List<TripPayment> payments = context.PaymentsForContact(569).ToList();

Note from the Author or Editor:
yes it's a capital F. :)

The code in Example 17-13 reads as:
List<CustomerService.Trip> results = proxy.GetUpcomingTrips();
However, according to the Figure 17-2 on the previous page, the namespace for the proxy classes is Chapter17ConsoleApp.BAGAServices so that it should be read as:
List<BAGAServices.Trip> results = proxy.GetUpcomingTrips();
I think the source of this error is the fact that the very same namespace is named CustomerService in the Chapter 17's source code and it reflects that. I think it's a good idea if both the book and the source code could be consistent in this manner which essentially requires to change the namespace either in the book or in the downloadable source code.

Note from the Author or Editor:
I'm sending an updated figure 17-2.
On page 469, under list item #1, there's a single line of code.
Change that to read:

using Chapter17ConsoleApp.CustomerService;

But, do not change the line of code suggested in the errata.

It reads as:
"In addition to the pattern for deleting from the collection, you'll notice that I don't use an index directly from the Reservations property. Instead, I identify the item position with custtoDelete.Reservations.ToArray()[i]. This is because EntityCollection does support indexing; therefore, you must first cast the EntityCollection to something that can be indexed."
This is applied to the previous edition where this code was implemented with a For loop which needs Reservation object to be selected by indexing. Now with having a foreach loop in place, this Paragraph does not apply anymore and should completely be removed.

Note from the Author or Editor:
please remove the entire paragraph in question.

The Predicate in the query inside RemoveTripsFromGraph method reads as: ".Where(r=> r.Trip != null && r.TripID == 0)"
TripID is Nullable on Reservation class which means even if TripID would be Null, "r.TripID == 0" will always returns false. This was correctly mentioned and implemented in the downloadable source code from the book website which also has this comment: "TripID is nullable in the model otherwise this would be == 0", therefore, the book's code should be changed to be read as:
".Where(r => r.Trip != null && r.TripID == null)
I think there is still one more issue exists and that is what if on the client side, they both populate Trip navigation property and TripID on Reservation object? For example, if we change TestCreateNewReservationforCustomer method to be look like this (from the book source code):
newRes.Trip = trips[8];
newRes.TripID = trips[8].TripID;
So then ".Where(r=> r.Trip != null && r.TripID == null)" would not find newRes and SavingChanges will throw an exception because the Trip object has not been removed. Wouldn't that be better if we just check for ".Where(r => r.Trip != null)"? Basically means that we will always remove Trip object from the Reservation regardless of the TripID which make sense because Trip object is not meant to be change when we add a new Customer or updating an existing one.

Note from the Author or Editor:
please make the first change from ==0 to == null

On the first bullet point in the sidebar where it reads:
"ObjectQuery to return objects without attaching th?m to the cache."
"them" is misspelled.

Note from the Author or Editor:
oh vey! how does this happen?

Please fix the font so that the word "them" does not have weird characters in it.

Just a little typo at the end of the page where it reads:
"PropertyChanging and PropertyChanged events, EntityObject, 251, 280"

Should be changed to:
"PropertyChanging and PropertyChanged events, EntityObject, 250, 280"

It's page 250 and not 251.

Note from the Author or Editor:

PropertyChanging and PropertyChanged events are on 274
PropertyChanging and PropertyChanged methods are on 271

On the 3rd line from the top it reads:
"...Be sure to reference the appropriate namespaces
at the top of your code files with *Include* for Visual Basic and using for C#..."

However, "Imports" Statement does import namespaces in Visual Basic.
So it should be read as:

"...Be sure to reference the appropriate namespaces
at the top of your code files with *Imports* for Visual Basic and using for C#..."

Note from the Author or Editor:
yes PLEASE replace "Include" with "Imports"

In the 2nd paragraph it reads:
Now imagine that you can write a LINQ query that looks like this:
from p in People.OfType<SalesPerson> select p

However, according to the EDM presented on page 4, Figure 1-2, the query has 2 problems:
1. There is no "People", the EntitySet name would be "Persons"
2. The brackets are missing on the OfType method.

So, it should be read as:
from p in Persons.OfType<SalesPerson>() select p

Note from the Author or Editor:
please add the open/close parens as follows. Do *not* make the suggested change to "Persons".

from p in People.OfType<SalesPerson>() select p

In example 18-7 - the SaveCustomer method - inside the using statement, the line of code that reads:
context.Contacts.Attach(cust);

The local variable name for Customer object is customer so the line should be read as:
context.Contacts.Attach(customer);

Note from the Author or Editor:
please make suggesting change (using "customer" instead of "cust")

On the 2nd Line of the 4th paragraph where it reads: "...using
the *Any* method, it looks at the names of each FieldMetaData item for that entry..."
According to the code later in the page (inside the foreach):
FieldMetadata modifiedField = fieldMetaData
.Where(f => f.FieldType.Name == "ModifiedDate")
.FirstOrDefault();
It uses the Where() method and not Any().
So, the line should be read as:
"...using the Where method, it looks at the names of each FieldMetaData item for that entry..."

Note from the Author or Editor:
Please change "Any" to "Where" in 2nd sentence of 4th paragraph

text "First, you'll need to add the method, BaseTypeName, shown in Example 18-3, into the custom methods section of the template where you inserted the MaxLengthValidation method in Chapter 11."

Chapter 11 is incorrect, it is Chapter 13, would be better to give the example or page number as well.

Note from the Author or Editor:
replace "in Chapter 11." with "in Example 13-12."

The first sentence states :

"the anonymous type that is returned has the properties FirstName and LastName, along with a collection of anonymous types with Street and City properties."

The name of the Street property (of the anonymous type) is incorrect. The property "Street1" was retrieved. The model in Figure 2-3 of page 24 shows that the Address entity has "Street1" and "Street2" properties, but a "Street" property. The first sentence should state :

... along with a collection of anonymous types with Street1 and City properties."

Note from the Author or Editor:
please change "Street" to "Street1" in referenced sentence.

This isn't truly a typo, but rather a suggestion for more explicit language.

The 3rd sentence states :

"Contact to Addresses is a one-to-many relationship and Addresses is a collection, not a single entity."

I think it would be more explicit to say :

"... and Addresses is a collection Of Entities , not a single entity."

Note from the Author or Editor:
change to...
" and Addresses is a collection of Address entities, not a single entity."

The index entry "navigation reference" lists only pg. 84. But pg. 42 introduces the term/concept "navigation reference" - in the 3rd paragraph, in its 2nd-to-last sentence.

Note from the Author or Editor:
Please add 42 to this item in the index

The first sentence states :

"If you are using SQL Server Developer or later, you can watch SQL Profiler"

The year/version of (Microsoft) SQL Server was left out. Did you mean 2000, 2005, 2008, or 2008 R2? Instead or "later", did you mean a higher(-level) version of SQL Server, such as Enterprise, etc. ?

Goodling for "SQL Profiler" shows that SQL Server 2000 had SQL Profiler.

Note from the Author or Editor:
modify paragraph:

"If you are using SQL Server (Developer or higher version), you can watch SQL Profiler. Visual Studio 2010 Ultimate's new IntelliTrace feature will expose the queries and updates to the database. However, IntelliTrace will not display parameter values. There are also third party tools such as EFProf from Hibernating Rhinos and the Query Profiler from Huagati."

Please retain EFProf link (www.efprof.com) and add link for "Query Profiler" ... http://huagati.com/L2SProfiler/

The first sentence states :

"The sidebar "Wrapping Your Head Around Lambdas" on page 62 includes a link to an article by Anders Hejlsberg."

The article referenced, at :

http://msdn.microsoft.com/en-us/magazine/cc163400.aspx

, is by Anson Horton, which is correctly stated in the sidebar on page 62.

Note from the Author or Editor:
please change Anders Hejlsberg to Anson Horton

Staring from page 67, the sentence reads :

"An IEnumerable allows you to enumerate or iterate
through each item in the collection as you did in the PRECEEDING code sample (i.e., in foreach),"

Examples 3-2 through 3-8 build upon Example 3-1 on page 50. The PRECEEDING code sample (excluding the declaration in Example 3-9, pg. 67) is Example 3-8 on pg. 65. Since you refer to the "foreach", perhaps you should explicitly say :

"... in Example 3-1 (i.e., in foreach)."

Note from the Author or Editor:
change sentence to read:

An IEnumerable allows you to enumerate or iterate through each item in the collection as you did in the foreach code block in Example 3-1."

The note begins :

"Notice that the entity has both a scalar property ...".

The model under discussion has three entities. It would be less ambiguous to say :

"Notice that the ADDRESS entity has both a scalar property ..."

Note from the Author or Editor:
this is in the note...change

Notice that the entity has both...

to

Notice that the Address entity has both ...

The last sentence of the 3rd paragraph says :

"K. Scott Alle-
nand Imar Spaanjaars, both ASP.NET gurus, ..."

The automatic syllable splitting across lines was confused by the absense of a space between "Allen" and "and". It should be :

"K. Scott Allen
and Imar Spaanjaars, both ASP.NET gurus, ..."

Note from the Author or Editor:
please be sure it's K.Scott Allen and Imar

The 2nd-to-last paragraph says "...although the Entity Framework runtime will recognize versions 2000, 2005, and 2008, NONE (my emphasis) of the design tools will NOT (my emphasis) work with SQL Server 2000."

I'm sure the error here ISN'T a double negative. Rather, (I believe) the intended statement is that "none of the design tools will work with SQL Server 2000."

Note from the Author or Editor:
although the Entity Framework runtime will recognize versions 2000, 2005, and 2008, the design tools will not work with SQL Server 2000.

The second selected item is written as:
a.LastName
It should be:
oa.LastName

Note from the Author or Editor:
yes, please make this fix in the 2nd line of example 4-19