Home/ Questions/Q 8426285
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-10T04:30:15+00:00

I know this is a common issue faced by beginners in EF and there

  • 0

I know this is a common issue faced by beginners in EF and there have been multiple questions and answers on the same here, but still I have not been able to still resolve the issue.

I am using EF 4.1 and MVC 3 and have generated the EF model from the DB in a separate library. I have copied the connection string from the app.config in the supporting library to the web.config of my application. I am also instantiating the object context by passing the web.config connection string.

string connectionString = System.Configuration.ConfigurationManager.ConnectionStrings["MasterDataContainer"].ConnectionString;

context = new MasterDataContainer(connectionString);

The connection string in web.config is as below

<connectionStrings>    
    <add name="MasterDataContainer" connectionString="metadata=res://*/MasterData.csdl|res://*/MasterData.ssdl|res://*/MasterData.msl;provider=System.Data.SqlClient;provider connection string=&quot;Data Source=.;Initial Catalog=MasterData;Integrated Security=True;MultipleActiveResultSets=True;Application Name=EntityFramework&quot;" providerName="System.Data.EntityClient" />
</connectionStrings>

I am getting the error “Keyword not supported : data source”.
Any help on this is appreciated.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You don’t need the EntityConnectionStringBuilder since you already have an EF connection string. i.e. just

    string connectionString = System.Configuration.ConfigurationManager.ConnectionStrings["MasterDataContainer"].ConnectionString;
context = new MasterDataContainer(connectionString);

    EntityConnectionStringBuilder can be used to build up an EF connection from e.g. a vanilla .NET one.

    Edit
    It looks like you’ve encountered this problem here. The workaround is to escape the load the connection string and then replace the &quot; with "'"

    What might be easier altogether is to use the name=ConnStringName overload of ObjectContext / DbContext. In your case, this would be

    context = new MasterDataContainer("name=MasterDataContainer");

    Note also if you view the source of the generated Context (probably MasterDataContainer.Context.cs) that the default constructor should have the EntityContainerName property hardcoded into it, so you might not need to provide a connectionstring at all to the constructor, provided that you keep the same EntityContainerName.

    http://msdn.microsoft.com/en-us/library/bb739017.aspx

    • 0