R
Ronald S. Cook
So I have a table "Employee" and wish to have a business class "Employee".
This was possible before LINQ. But now that I am generating a .dbml for the
LINQ DataContext, it "takes over" those names for its classes.
I'd hate to have to name my business classes "EmployeeClass" or some other
non-ideal convention.
Any thoughts?
Thanks,
Ron
This was possible before LINQ. But now that I am generating a .dbml for the
LINQ DataContext, it "takes over" those names for its classes.
I'd hate to have to name my business classes "EmployeeClass" or some other
non-ideal convention.
Any thoughts?
Thanks,
Ron