Entity Framework - Unable to load the specified me

Question

I realise that this has been asked a number of times but I just can't seem to get the bottom of my issue. I'm getting the following error stack:

When I reflect out my dll I can see the following

Reading http://blogs.teamb.com/craigstuntz/2010/08/13/38628/ it suggests I'd expect to see the csdl, msl and ssdl files here, but they're not. They do exist here obj\Debug\edmxResourcesToEmbed though.

Never-the-less I tried to explicitly tell the web.config where to look by doing this:

...connectionString="metadata=res://DllName.dll/PaymentModel.csdl|res://DllName.dll/PaymentModel.ssdl|res://DllName.dll/PaymentModel.msl;provider=System.Data.SqlClient;provider ... />

Which just throws an error saying it cannot find the dll:

Unable to resolve assembly 'DllName.dll'.

Very similar to this unresolved SO question Unable to resolve assembly Model.dll

The final thing I tried was to change the metadata line to:

...connectionString="metadata=res://*/;provider=System.Data.SqlClient;provider ... />

This threw a message about sql ce which I'm not using - is there a way to get round this??

Is there anything else I can try? Or can anyone see where I'm going wrong? Some extra detais:

• Using EF 6 EDMX set to "Embedded Resource"

• Copy to output directory:"Do not copy"

• Metadata artifact processing: "Embed in output assembly"

Finally on this - if I set the EDMX from Embedded Resource to EntityDeploy then this will work locally but not build on the build server as it throws the exact same error as this SO question:

Could not find the Conceptual Schema node to embed as a resource for input file

But the fix doesn't seem to help and I can't install .NET 4.5 on the server unfortunately.

Answer 1

Solution :
1) Open .edmx file from visual studio.
2) Click anywhere.
3) Should see edmx property window.
4) Change Namespace to the correct folder name.
5) 1: https://i.stack.imgur.com/6sZvo.png (select image for more details ).

Answer 2

So I've got to the bottom of this, partly I think this was my fault. I'll put solutions to each issue I encountered below in case it helps anyone else.

Unable to load the specified metadata resource issue

This was caused by me setting the 'Metadata Artifact Processing' setting on the edmx model from "EntityDeploy" to "Embedded Resouce".

So this meant it just embedded the whole edmx file file into the dll and didn't generate the ssdl, msl and csdl files instead.

I guess you have to set this to EntityDeploy for this to work and generate these files correctly. Makes perfect sense and our bad over here.

Unable to resolve assembly 'DllName.dll'

This was resolved by Andrew in the comments above, thanks for the pointer on that.

Could not find the Conceptual Schema node to embed as a resource for input file

The key to this whole issue really is this, our build server is currently on Windows 2003, so can't have .NET 4.5 installed, locally we were using EF 6.1 running under .NET 4.0 on VS2013.

However for some reason it looks like we need to have .NET 4.5 installed on our build server to get this to build even though we're not using any of the 4.5 features and targetting the .NET 4 framework.

Downgrading to EF to 4.3 solved this issue for us in the short term. Not ideal but it worked.

Answer 3

I hit this issue and it has bit me many, many, many times and I always forget how I fix it.

All I had to do is set the default.aspx as the start page.

Obviously this won't help everyone but in my case I have gone down the road of checking my config, connection string...

Hope this help someone, or at least the next time I google it I will find my fix. :)

Answer 4

Change the metaData

connectionString="metadata=res://*/Entities.csdl|res://*/Entities.ssdl|res://*/Entities.msl;

To

connectionString="metadata=res://*/;

The above change will fix the issue

Answer 5

Also, be aware when moving the edmx file from say a web application to a data layer, (web.config - connection / app.config - connection) that you change the connectionstring in the data layer AND the webservice layer. (else one uses two different connection strings, and this causes such a problem)

Answer 6

The connection string "metadata=res" should be same as Edmx name. eg

metadata=res://*/EmployeeModel.csdl 

this EDMX name should be EmployeeModel