Table Splitting

var em = new NorthwindIBEntities();
        
//Make a customer
var customer = em.CreateEntity<Customer>();
customer.EntityAspect.AddToManager();

//Generate a new Guid as the Id
customer.CustomerID = Guid.NewGuid();

//Sanity check
DebugFns.Assert(customer.CustomerID != Guid.Empty);

//Make an address
var customerAddress = em.CreateEntity<CustomerAddress>();
customerAddress.EntityAspect.AddToManager();

//Sanity check - the ID is still set
DebugFns.Assert(customer.CustomerID != Guid.Empty);
        
//Assign the address
customer.CustomerAddress = customerAddress;

//Fails!  The 'blank' Id from the CustomerAddress entity seems to have overwritten the 'real' ID on the Customer
DebugFns.Assert(customer.CustomerID != Guid.Empty);

//Make a customer
var customer = em.CreateEntity<Customer>();
customer.EntityAspect.AddToManager();

//Generate a new Guid as the Id
customer.CustomerID = Guid.NewGuid();

//Sanity check
DebugFns.Assert(customer.CustomerID != Guid.Empty);

//Make an address
var customerAddress = em.CreateEntity<CustomerAddress>();
customerAddress.EntityAspect.AddToManager();

//Sanity check - the ID is still set
DebugFns.Assert(customer.CustomerID != Guid.Empty);

//HACK: Copy over the ID manually
customerAddress.CustomerID = customer.CustomerID;
        
//Assign the address
customer.CustomerAddress = customerAddress;

//Passes now
DebugFns.Assert(customer.CustomerID != Guid.Empty);

//Delete the customer
customer.EntityAspect.Delete();

//Both entities should now be detached (since they never got saved, they become detached instead of 'Deleted')
DebugFns.Assert(customer.EntityAspect.EntityState == EntityState.Detached);
        
//Fails: The CustomerAddress is still in an Added state
DebugFns.Assert(customerAddress.EntityAspect.EntityState == EntityState.Detached);

manager.GenerateId(myCustomer, Customer.PropertyMetadata.CustomerID)

Cannot call GenerateId on 'Customer.CustomerID'. GenerateId cannot be called on ForeignKey properties ( even if they are also part of a PrimaryKey).  Call GenerateId instead on the 'source' primary key

//Make a customer
var customer = em.CreateEntity<Customer>();
customer.EntityAspect.AddToManager();

//Generate a new Guid as the Id
customer.CustomerID = Guid.NewGuid();

//Sanity check
DebugFns.Assert(customer.CustomerID != Guid.Empty);

//Make an address
var customerAddress = em.CreateEntity<CustomerAddress>();
customerAddress.EntityAspect.AddToManager();

//Need to AcceptChanges before doing the delete otherwise the entity will just get detached
customer.EntityAspect.AcceptChanges();

//Delete the customer.
customer.EntityAspect.Delete();

//The customer still has its ID even though it is deleted
DebugFns.Assert(customer.CustomerID != Guid.Empty);

//Assign the address
customer.CustomerAddress = customerAddress;

//Since I reversed the Referential Constraint, the Customer.CustomerID property didn't get cleared
DebugFns.Assert(customer.CustomerID != Guid.Empty);

//Fails!  The CustomerAddress.CustomerID is still empty....even though it got assigned to the navigation property!
DebugFns.Assert(customerAddress.CustomerID != Guid.Empty);

entityManager.Customers.Single(c => c.CustomID == someId).EntitAspect.Delete();
entityManager.SaveChanges();

//Loop through any deleted Customer entities to fix them up
foreach(var customer in EntityManager.FindEntities<Customer>(EntityState.Deleted)
{
   //If the CustomerAddress wasn't loaded, we need to make a placeholder one to make EF happy
   if(customer.CustomerAddress == null)
   {
       //Make the placeholder and assign it to the navigation property.
       customer.CustomerAddress = EntityManager.CreateEntity<CustomerAddress>()

       //Before deleting this entity, we need to accept the changes...otherwise it will become detached
       customer.CustomerAddres.EntityAspect.AcceptChanges();
       
       //Now delete it
       customer.CustomerAddress.EntityAspect.Delete();
    }
}

       [TestMethod]
        public void TestDeletedEntityNavigations()
        {
            var em = new EntityManager();

            //Make the Customer and CustomerAddress - hard-coding the same key
            var customer = new Customer {CustomerID = 123};
            var customerAddress = new CustomerAddress {CustomerID = 123};

            //Add both entities to the entity manager
            em.AttachEntities(new Entity[] {customer, customerAddress});

            //Since they have the same PK, DevForce automatically updated the navigation properties so
            //  these two tests will pass.
            Assert.AreEqual(customer, customerAddress.Customer, "customerAddress.Customer is wrong");
            Assert.AreEqual(customerAddress, customer.CustomerAddress, "customer.CustomerAddress is wrong");

            //Now delete the two entities (in practice, we only need to delete the customer and that will
            //  cascade to the CustomerAddress as well - but we'll be explicit here for demonstration purposes)
            customer.EntityAspect.Delete();
            customerAddress.EntityAspect.Delete();

            //I'd still expect (and want) the navigation properties to still work.  This first check will work...
            Assert.AreEqual(customer, customerAddress.Customer, "customerAddress.Customer is wrong");

            //But then this one will fail.  customer.CustomerAddress is pointing to a NullEntity
            Assert.AreEqual(customerAddress, customer.CustomerAddress, "customer.CustomerAddress is wrong");
        }