New answers tagged projects-and-solutions
I would go with x.DataAccess.Interface and have your implementations as x.DataAccess.Oracle, x.DataAccess.EF or whatever.
The naming pattern also depends on your other projects. Depending on the contents of your implementation projects it could be something like this: X.DataAccessLayer X.DataAccessLayer.Sql X.DataAccessLayer.Oracle PS: I would drop 'Layer' as well, unless you have a mix of independent libraries and actual layers.
Use whatever name you can think of that correctly describes the contents and does not feel too long. Personally, X.DataAccessLayerInterfaces feels too long for me, so I would probably opt for X.DataAccessInterfaces, but otherwise there is nothing wrong with it.
Certainly -- why would visual studio's fundamental unit be a solution if this weren't the case?
Top 50 recent answers are included