Dec 11, 2013 at 10:43 AM
Edited Dec 11, 2013 at 10:44 AM
I am trying to use Effort in a database first approach, where a single catalog contains multiple schema's which have been split into multiple metadata files. (Dal.A
) I am using the CSV export to fill my initial database because I need a lot of existing configuration data.
So, I have a connection string which is build up as follows:
<add name="MyEntities" connectionString="metadata:res://*/Dal.A.csdl|res://*/Dal.A.ssdl|res://*/Dal.A.msl|res://*/B.csdl|res://*/B.ssdl|res://*/B.msl ... // Rest of stuff here
When creating the context however, only the first EntityContainer
is used to create a schema. This means that, as long as I'm testing the objects within the Dal.A schema everything works fine, but when I touch an object in the B schema, everything
I started looking into the Effort source code and came upon the following. When a new
is created, the following code is executed:
EntityContainer entityContainer =
So it's effectively taking the first EntityContainer
in the collection, where I have 2, therefore creating only one schema.
Does Effort support multiple EntityContainers, should I do something special in my setup or is there a workaround for this?