I just finished reading through chapter 2 and started reading chapter 3. I have a few questions architecturally.

1. Why does the author not implement the insert(),update(), delete() methods of the ENTUserAccountData class using the default Datacontext class without passing the connection string as a parameter.

For example the author has 2 overloaded the insert() methods like
Insert(string connection string, parameter 1,.....)
Insert(DataContext, parameter1....)

Can is it a good practice to implement a third overload like so using the default DataContext.
Insert(parameter1,parameter2...)


2.
While implementing the Insert(),Update(),Delete() method, why can we not pass the Entity object as the parameter instead of passing scalar variables.

So apart from
Insert(DataContext, parameter1,parameter2....)

We could implement
Insert(DataContext, EntityObject)

I understand the author has chosen the design pattern of passing entity objects from the DAL to the BLL..and scalar values to the DAL from the BAL.
Why should we not pass entity objects back to the DAL from the BLL???


------------------------------
I hope that my questions make some sense...

This is a good question. Both options are perfectly viable. In fact, we've enhanced the framework at my work to implement your second point. We pass the entity objects back and forth instead of parameters.
My goal of the book was to give people a starting point so they can extend and enhance the framework themselves.

Good Luck