The Auto-Generated Code of TableAdapterManager class in VS2008 and VS2010 are different. In vs2008, the UpdateInsertedRows method of TableAdapterManager is correct.
The parent TableAdapter's update method is called before the childTableAdapter's update method. So we can insert a new row to the parent table and a new row to the child table(with a primary key in parent table) correctly. However, in vs2010, the order is kind of reversed. We will get a exception saying that "The INSERT statement conflicted with the FOREIGN KEY constraint ..." when calling tableAdapterManager.UpdateAll method. With the same settings, the behaviours in vs 2008 and vs2010 are different.
You can refer to this thread for some details.