Why not use two classes? Note this does not mean you need to have two tables. PersonName
can be a component of Person
I believe. You would have two mapping classes for this.
class PersonName{
public string FirstName{get; set;}
public string LastName{get; set;}
}
class Person{
public PersonName Name{get; set;}
public string Age{get; set;}
public string Sex{get; set;}
public string Las{get; set;}
}