Databases
StackOverflow2013
Postsdbo
POEF Code First - The Provider did not return a ProviderManifestToken string
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POEF Code First - The Provider did not return a ProviderManifestToken string
    primarykey
    data
    text
    <p>I'm trying to get a very simply EF Code First example running but ran into the above problem. I've followed the advice here ( <a href="https://stackoverflow.com/questions/4741499/how-to-configure-providermanifesttoken-for-ef-code-first">How to configure ProviderManifestToken for EF Code First</a> ) but to no avail. I finally managed to get EF to create my database and tables by passing the actual connection string to the DBContext instead of the connection string name I had defined.</p> <p>Here is how I defined by connection string initially in app.config</p> <pre><code>&lt;connectionStrings&gt; &lt;add name="ProductContext" connectionString="integrated security=SSPI; data source=MYMACHINE; persist security info=False; initial catalog=Product" providerName="System.Data.SqlClient" /&gt; &lt;/connectionStrings&gt; </code></pre> <p>The name "ProductContext" matches the class ProductContext and the database Product does not exist. </p> <p>Following the advice on a previous thread I passed the connection string name to ProductContext and the base DBContext cstor. This did not work either.</p> <p>Finally, I passed the connection string above instead and everything worked, the db was created and the tables. </p> <p>I'm using SQL Server 2008 and EF 4.1. Any ideas as to what I'm doing wrong?</p> <p>Thanks,</p> <p>Ken</p> <p><strong>Update</strong></p> <p>The application is a WPF application, not a web application. I get the same exception after I remove the connectionstring from <em>app.config</em>:</p> <blockquote> <p>"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)"</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USLance
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POEF Code First - The Provider did not return a ProviderManifestToken string
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POEF Code First - The Provider did not return a ProviderManifestToken string
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIs the connection string in the *app.config* of the project you are running or is it in a library project?
      singulars
      1. POEF Code First - The Provider did not return a ProviderManifestToken string
      1. USSlauma
    2. COit's in the app.config of the main project not the library. How do a get around that?
      singulars
      1. POEF Code First - The Provider did not return a ProviderManifestToken string
      1. USLance
    3. COTried adding an app.config to the library project and also tried sharing the main projects app.config but neither approach worked.
      singulars
      1. POEF Code First - The Provider did not return a ProviderManifestToken string
      1. USLance
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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