Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Try adding metadata resource information to your connection string. </p> <p>Assuming your Entity Data Model is called "TerminalDataEntities.edmx" there are three files generated in the obj\Debug\edmxResourcesToEmbed Folder of your project. </p> <ul> <li>TerminalDataEntities.csdl</li> <li>TerminalDataEntities.ssdl</li> <li>TerminalDataEntities.msl</li> </ul> <p>To add these resources to your connection string, you need to change the format of the add-Tags connectionString-Value.</p> <p>The metadata:</p> <pre><code>metadata=res://*/TerminalDataEntities.csdl|res://*/TerminalDataEntities.ssdl|res://*/TerminalDataEntities.msl; </code></pre> <p>The provider:</p> <pre><code>provider=System.Data.SqlClient; </code></pre> <p>and the provider connection string:</p> <pre><code>provider connection string=&amp;quot;Data Source=URIEL\SQLIT64;Initial Catalog=IFDB;Trusted_Connection=True;MultipleActiveResultSets=True&amp;quot; </code></pre> <p>Put it all together: (With Windows Identity)</p> <pre><code>&lt;add name="DbTerminalContext" connectionString="metadata=res://*/TerminalDataEntities.csdl|res://*/TerminalDataEntities.ssdl|res://*/TerminalDataEntities.msl;provider=System.Data.SqlClient;provider connection string=&amp;quot;Data Source=URIEL\SQLIT64;Initial Catalog=IFDB;Trusted_Connection=True;MultipleActiveResultSets=True;App=EntityFramework&amp;quot;" providerName="System.Data.EntityClient" /&gt; </code></pre> <p>(Without Windows Identity)</p> <pre><code>&lt;add name="DbTerminalContext" connectionString="metadata=res://*/TerminalDataEntities.csdl|res://*/TerminalDataEntities.ssdl|res://*/TerminalDataEntities.msl;provider=System.Data.SqlClient;provider connection string=&amp;quot;Data Source=URIEL\SQLIT64;Initial Catalog=IFDB;User Id=sa;Password=password;MultipleActiveResultSets=True;App=EntityFramework&amp;quot;" providerName="System.Data.EntityClient" /&gt; </code></pre> <p>Hope this works.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload