How to Query Icollections of Entity Framework Code First Data - asp.net-mvc

Question

I'm following this post here
his code looks like so
from p in ctx.Persons
where p.ID == personId
select new PersonInfo
{
Name = p.FirstName + " " + p.LastName,
BornIn = p.BornInCity.Name,
LivesIn = p.LivesInCity.Name,
Gender = p.Sex.Name,
CarsOwnedCount = p.Cars.Count(),
}
Now when he is using p.LivesInCity.Name ( My Assumption is that he has 2 different ViewModels Classes and 1 of them has an IEnumerable or some sort of collection of City names?)
Question
How can he access p.LivesInCity.Name but when i Try p.Countys.[CountyColectionForSections].[SectionProperty] I get See Image Below
here is how i setup my ViewModels
Table 1
public string Client { get; set; }
public virtual ICollection<dbProspect> Prospects { get; set; }
Table 2
public int Prospect { get; set; }
public virtual ICollection<dbCounty> Countys { get; set; }
public virtual ICollection<UserProfiles> UserProfiles { get; set; }
Table 3...
Table 3 Would have a collection of another table, and table 4 would have another colection and so on Basically a Table Hierarchy about 15 deep.
here is how i try and access them
var x = from c in db.Client
select new ViewModelExcelReport
{
client = c.ClientName,
cntyCounty = p.Countys. //Here is where i would like to say p.Countys.[CountyProperty]
sctSection = p.Countys.[CountyColectionForSections].[SectionProperty]
}

Answer 1

You could do the following if you expect only one County per Client and I'm guessing at the relation between the entities:
var x = from c in db.Client
from p in c.Prospects
from ct in p.Countys
select new ViewModelExcelReport
{
client = c.ClientName,
cntyCounty = ct.County,
sctSection = ct.Section
};

Answer 2

The first example works because he's only referencing a single instance of an entity (LivesIn of type City), and then referencing a single primitive value within (Name property is just a string).
I see you're trying to project a new type by referencing an IEnumerable (Countys), but you never actually enumerate/iterate/materialize an instance.
p.Countys.[CountyProperty] will never exist, because you have a reference to a collection and you must get a reference to a single object first. You can do that by using Countys.Single() or SingleOrDefault() but I doubt that's what you want. I think what you want is to traverse the model in the opposite direction. From the "Many" side to the "One" side. Something like this:
var x = from c in db.County
select new ViewModelExcelReport
{
County = c.Name,
CountyProperty = c.AnyProperty,
Section = c.Section.Name,
Prospect = c.Prospect.Name,
Client = c.Prospect.Client.Name
}