At Coder Camps, I have been taught a pattern that they call the Adapter/Interface pattern, but really this is called the Repository pattern in most of the rest of the programming world. When I built my personal project at the end of my camp experience, I decided to play around with the repository pattern a bit more, and stray from the same fileanames and folders we were taught to use.
Repository Pattern
Instead of calling my interfaces using the name Adapter, I used the word Repository and named my files to match. ProgrammingBootcamps.com.Data/IBootcampedioRepository.cs and BootcampedioRepository. The interface defines empty method signatures:
Now inside ProgrammingBootcamps.com.Data/IBootcampedioRepository.cs I place the code that actually does the heavy lifting in .Net using Entity framework to interact with the context. The context is the object that deals with pulling rows of data into DbSets for retreival, manipulation, and saving back to the database.
I seperated several of my calls from the methods so that I could call them seperately and catch errors if they failed.