Third Party web controls and tight coupling
Disclaimer: I am not against third-party controls because I believe it’s for productivity
Third Party web controls and tight coupling
Disclaimer: I am not against third-party controls because I believe it’s for productivity
Third Party web controls and tight coupling
Disclaimer: I am not against third-party controls because I believe it’s for productivity
When does one hard-code actual data values into the code as opposed to using a DB?
A long-standing question for me has been: when do I store data (actual values) in a database table, and when do I store them right in the code?
Entity Framework and separating DAL from domain entities
If I have a normalized db, it’s unlikely to map 1 to 1 with my domain entities. So I customize my EF entities to fit the domain. But now my EF entities are essentially my domain entities and my DAL is baked into my business objects.
Entity Framework and separating DAL from domain entities
If I have a normalized db, it’s unlikely to map 1 to 1 with my domain entities. So I customize my EF entities to fit the domain. But now my EF entities are essentially my domain entities and my DAL is baked into my business objects.
Decoupling of Model and API (in an .net WEB API Project)
I currently have one separate project for my models, and one separate project for a API application that consumes this model. The intention of the separation is to avoid any outgoing dependencies from the core model to consumers like the API project, enabling me to have a nice layered structure of responsibility.
If MVC is “Separation of Concerns” then why was Razor Syntax introduced?
My question is related to MVC design pattern and Razor Syntax introduced by Microsoft.
If MVC is “Separation of Concerns” then why was Razor Syntax introduced?
My question is related to MVC design pattern and Razor Syntax introduced by Microsoft.
Separation of logic from presentation results in repetition of code
Here’s what I’ve been thinking.