Building a solution from the start to be able to switch database can be a very smart move. In some cases it could be argued that too much software is built for re-usability and with layers of abstraction that are never actually used for anything. But in some cases it makes a lot of sense to make sure that you build your solution in a way that would afford you a good number of options going forward.
Entity Framework can be both a blessing and a curse - especially EF database first. For startups and small clean sheet projects it really works wonders. You can get so much done in very little time. But once you have to work within the constraints of corporate structure and corporate security, then you quickly run … Continue reading Override SaveChanges – EF database first – set properties