Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Entity SQLCE Can't find connection string in app.config file

Posted on 2011-09-22
10
Medium Priority
?
1,447 Views
Last Modified: 2013-12-25
I've been getting this error when I try and use my model container:

No connection string named 'PFModelContainer' could be found in the application config file.

I have my edmx file in a separate project. I checked the app.config file and my model was there, and I also put it in my main project app.config file. Still doesn't work. Here's the connection string:

    <connectionStrings>
        <add name="PFModelContainer" 
             connectionString="metadata=res://*/PFModel.csdl|res:
                               //*/PFModel.ssdl|res://*/PFModel.msl;
             provider=System.Data.SqlServerCe.3.5;
             provider connection string=&quot;
             Data Source=C:\Documents and Settings\Jon\My Documents\Visual
                         Studio 2010\Projects\SpreadsheetAddIn
                         \SpreadsheetAddIn\bin\Debug\PFData.sdf;
             Password=password&quot;" 
             providerName="System.Data.EntityClient" />
    </connectionStrings>

Open in new window


Here's how the context is called:

Private mdbContext As New PFModelContainer

Open in new window


Which goes to:

Partial Public Class PFModelContainer
    Inherits DbContext

    Public Sub New()
        MyBase.New("name=PFModelContainer")
    End Sub

Open in new window


I thought the answer would be similar to what happened to this guy. But unfortunately his solution doesn't work with mine.

I've noticed the error isn't caught until I hit this code. It occurs when I do the linq query on the third line.

Dim dbContext As New PFModelContainer
Dim dbAccount As IQueryable(Of Account)
dbAccount = From a In dbContext.Accounts
            Where (a.AccountName = "Hello")
            Select a

Open in new window

0
Comment
Question by:lilypad49
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 4
10 Comments
 
LVL 96

Expert Comment

by:Bob Learned
ID: 36587428
The connection string needs to be in the entry assembly project's app.config.
0
 

Author Comment

by:lilypad49
ID: 36587473
Yes, I've tried that and it still doesn't work, this is what I put:


<add name="PFModelContainer" 
     connectionString="metadata=res://*/PFModel.csdl|
                                res://*/PFModel.ssdl|
                                res://*/PFModel.msl;
     provider=System.Data.SqlServerCe.3.5;
     provider connection string=&quot;
       Data Source=C:\Documents and Settings\Jon\My Documents\Visual Studio 2010\Projects\SpreadsheetAddIn\PFDatabase\bin\Debug\PFData.sdf;
       Password=password&quot;" 
     providerName="System.Data.EntityClient" />

Open in new window


I also tried:

<add name="PFModelContainer" 
     connectionString="metadata=res://PFDatabase/PFModel.csdl|
                                res://PFDatabase/PFModel.ssdl|
                                res://PFDatabase/PFModel.msl;
                                [...Same...]

Open in new window


and

<add name="PFModelContainer" 
     connectionString="metadata=.\PFModel.csdl|
                                .\PFModel.ssdl|
                                .\PFModel.msl;
                                [...Same...]

Open in new window


and

<add name="PFModelContainer" 
     connectionString="metadata=~\PFModel.csdl|
                                ~\PFModel.ssdl|
                                ~\PFModel.msl;
                                [...Same...]

Open in new window


What am I missing? Should it be written differently?
0
 
LVL 96

Expert Comment

by:Bob Learned
ID: 36587497
You can use the System.Configuration.ConfigurationManager to try to get the connection string.  Also, you can construct a data context, by passing in the connection string, since there are overloaded constructors.
0
Interactive Way of Training for the AWS CSA Exam

An interactive way of learning that will help you visualize core concepts so that you can be more effective when taking your AWS certification exam.  Built for students by a student to help them understand the concepts that they are being taught.

 

Author Comment

by:lilypad49
ID: 36590079
I imported System.Configuration then did

dim con as Configuration
dim con as Configuration.ConfigurationSettings

But VB didn't like it, ConfigurationManager didn't even pop up. I'm using VB.NET Express, so I don't know if that is part of the problem.

I'll try and do the construct with data context.
0
 
LVL 96

Expert Comment

by:Bob Learned
ID: 36590099
That would be something like this:

Import System.Configuration

...

Dim connectionString As String = ConfigurationManager.ConnectionStrings("MyDatabase").ConnectionString
Dim context As New MyDataContext(connectionString)

Open in new window


where "MyDatabase" in the connection string.
0
 

Author Comment

by:lilypad49
ID: 36590445
OK, I finally got a connection string working using

Using conn As EntityConnection = New EntityConnection(entityBuilder.ToString)

Open in new window


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

but when I try do use

Dim context As New MyDataContext(connectionString)

Open in new window


it gives me the error:


Too many arguments to 'Public Sub New()'.

Am I supposed to create the overloaded constructors myself or am I missing something.

TheLearnedOne: Thanks for your patience with me!
0
 
LVL 96

Accepted Solution

by:
Bob Learned earned 2000 total points
ID: 36590514
I was thinking Entity Framework, but it looks like you are using a different platform for your data context.
0
 

Author Comment

by:lilypad49
ID: 36590623
I am using Entity Framework v. 4.1. To grab the context I use:

I was using

ADO.NET DbContext Generator

was I supposed to be using

ADO.NET EntityObject Generator

?

What's the difference between the two?
0
 

Author Comment

by:lilypad49
ID: 36590690
OK, I looked up the difference, I guess EntityObject is the old way of doing things and DbContext is the new "preferred" way of doing things.

So, apparently inside of the dbcontext mybase.new can either be the name of the context or the connection string, unfortunately they didn't put in an overrideable statement (someone must have missed it), so I did it manually. It works now!

Thanks so much for your help oh learned one! I just wonder why it wasn't working properly, I would think they would just make it plug and chug, I wonder what I'm doing wrong :\ .
0
 

Author Closing Comment

by:lilypad49
ID: 36590697
Thanks once again for your help! It would be nice to find out what was going wrong with Microsoft (or me)!
0

Featured Post

Learn by Doing. Anytime. Anywhere.

Do you like to learn by doing?
Our labs and exercises give you the chance to do just that: Learn by performing actions on real environments.

Hands-on, scenario-based labs give you experience on real environments provided by us so you don't have to worry about breaking anything.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If you need to start windows update installation remotely or as a scheduled task you will find this very helpful.
Ever wondered why sometimes your SQL Server is slow or unresponsive with connections spiking up but by the time you go in, all is well? The following article will show you how to install and configure a SQL job that will send you email alerts includ…
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.
Via a live example, show how to setup several different housekeeping processes for a SQL Server.

670 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question