C# Code First Vs. SQL Database first when using a business logic layer

Question

I am firmly in the camp of being a database first developer. I believe there are pro's and cons' to each approach. However when creating a code first approach should the newly created classes have default values set?

E.g.

public DateTime DateCreated {get; set;} = DateTime.Now;

If so what is the need for an existing business logic layer when the above property is not being referenced anywhere in the controller or business layer methods.

Another point is the mere fact that if code first migrations are enabled on commented out code the column is dropped!

Data is precious.

Stefano Buzzoni · Accepted Answer · 2022-07-27 08:25:35Z

0

Business logic layer works as a medium from presentation layer and data access layer, so if a request in the business layer points to your property it gets fetched by data layer and returned

answered Jul 27, 2022 at 8:25

Stefano Buzzoni

941 silver badge12 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Zain Nabi Over a year ago

,Exactly so. Why manipulate the code first classes if the property is not being used? It should be in the business logic layer

Stefano Buzzoni Over a year ago

I don't really know to be honest, I never used code first approach. You should try to post the question on software engineering section, maybe they can give you more infos

Collectives™ on Stack Overflow

C# Code First Vs. SQL Database first when using a business logic layer

1 Answer 1

2 Comments

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Related