Oct 20, 2014
This is an unusual situation.
My initial response would be to merge those databases and add a db identifier to each record.
(I realize that this is not an option)..
My next response would be to create 10 separate domain projects, although the data model is the same for each database.
(I realize that this is not an option - although you can always move the domain code to the main project and remove the domain projects)
The 10 domain projects will create the same objects in different namespaces for each table.
All this is strange and is unnecessary code duplication because the databases are the same.
When using only 1 domain project, I was thinking that all the Repository methods perhaps can be customized to accept a connection string (name) for each request.. This may be possible, but requires a good understanding of the underlying Core.cs and Repository.cs files (the good news is that you have all the source code).
There is no doubt that something can be done, but at this point I am not certain what the most optimal solution is.
It all requires some experimentation. Hope this gets you going.