I want to prevent my developers from accidentally creating a base entity class and bypass the custom validation and saving logic we will be adding to our entities. Is there a way to make the base classes in a two class scenario abstract?

Hi benjam, I can see two options here:

A. If you have some Business Classes, you could enforce the use of subclasses by demanding them from methods:

public void DoSometihng(MyCustomerEntity customerToUse)

B. Use the "General preset" (not "Two Classes"). This way you could write your business logic at partial classes and the programmers have only one class to instantiate.

Why did you choose "two classes" scenario over "one class"?