6

I have an asp.net website running under .net v4. I have upgraded from Entity Framework v5 to v6.02 and all worked fine running locally on IIS express and .net4 using the EntityFramework v4 dll provided by nuget.

I publish to my hosting company and get the error below. Upgrading to .net4.5 might help, but this is not an option on my provider at the moment.

Any suggestions?

System.Data.MetadataException: Schema specified is not valid. Errors: BkkpsModel.csdl(2,9) : warning 0005: Could not find schema information for the attribute 'Namespace'. BkkpsModel.csdl(2,32) : warning 0005: Could not find schema information for the attribute 'Alias'. BkkpsModel.csdl(2,98) : error 0005: The 'http://schemas.microsoft.com/ado/2009/02/edm/annotation:UseStrongSpatialTypes' attribute is not declared. BkkpsModel.csdl(2,2) : error 0010: The element Schema in namespace http://schemas.microsoft.com/ado/2009/11/edm was unexpected for the root element. The expected Schema in one of the following namespaces: http://schemas.microsoft.com/ado/2006/04/edm, http://schemas.microsoft.com/ado/2007/05/edm, http://schemas.microsoft.com/ado/2008/09/edm.
simon831
  • 5,166
  • 7
  • 33
  • 50

3 Answers3

16

You created an EDMX file with Entity Framework 6 but you using it with Entity Framework 5. Entity Framework 6 uses EDMX file with version 3.0 but Entity Framework 5 does not support it.

You must repair your EDMX file from version 3.0 to version 2.0

The easiest way to do that is open EDMX in Visual Studio 2012 project with Entity Framework 5 or older. The entity data model designer show error: unable to display file. The file references an XML namespace that is inconsistent with the target framework of the project. Than click the modify link and the designer automaticly repair your EDMX file.

OR:
1. open your EDMX file as XML Editor
2. change the following elements:

from:
<edmx:Edmx Version="3.0" xmlns:edmx="http://schemas.microsoft.com/ado/2009/11/edmx">
to:
<edmx:Edmx Version="2.0" xmlns:edmx="http://schemas.microsoft.com/ado/2008/10/edmx">

from:
xmlns="http://schemas.microsoft.com/ado/2009/11/edm/ssdl"
to:
xmlns="http://schemas.microsoft.com/ado/2009/02/edm/ssdl"

from:
xmlns="http://schemas.microsoft.com/ado/2009/11/edm"
to:
xmlns="http://schemas.microsoft.com/ado/2008/09/edm"

from:
<Mapping Space="C-S" xmlns="http://schemas.microsoft.com/ado/2009/11/mapping/cs">
to:
<Mapping Space="C-S" xmlns="http://schemas.microsoft.com/ado/2008/09/mapping/cs">

... for all inconsistent xmlns
Cyrus
  • 2,261
  • 2
  • 22
  • 37
  • 7
    This happened to me but I ended up having to upgrade my EDMX to v3, so following these steps in reverse helped me to do that. Thanks! – Derreck Dean Mar 31 '15 at 18:00
  • 1
    all this time I assumed that the "modify" link would just open the XML for modification. I had no idea it would actually try to repair the xml namespaces. I think I've done it manually a dozen times or so... >_ – Dave Cousineau Jun 15 '17 at 23:30
1

Another way of achieving what Cyrus said (downgrading from edmx v3 to ednx v2) is in the answer for another question:

EDMX .NET 4.5 to 4.0?

Community
  • 1
  • 1
MajorInc
  • 342
  • 3
  • 12
0

In my case, I rebuilt the Solution and the edmx compiled, changed a bunch of DLLs and PDBs and I was able to open the EDMX just fine. Hope that helps.

Vishwa

vishwa
  • 1