Where is the metadata?

sakkaku · Post by **sakkaku** » Wed 23 Sep 2009 15:40

I am trying to figure out how to setup the connectionstring to get this thing off the ground.

I get the error: The specified metadata path is not valid. A valid path must be either an existing directory, an existing file with extension '.csdl', '.ssdl', or '.msl', or a URI that identifies an embedded resource.[/code]

I don't seem to have the metadata, just .cs, .edml.view and .edps files generated from the DevArt entity model tool thingy. I have read through the help but there doesn't seem to be anything that covers this.

sakkaku · Post by **sakkaku** » Wed 23 Sep 2009 18:06

Found out it was creating an app.config w/ connection strings in them. Moved those into web.config and...

Unable to load the specified metadata resource.

There has to be something I am doing wrong.

- Right clicked the folder, selected Data -> Devart Entity Model
- Connected to the database in the tool that launches, drag over tables I want, etc
- Moved connectionString from app.config to web.config
- Wrote a basic ef query, seems to load in the connection string now and fails to find any metadata.

Is there anything else I need to be doing? I worked a little with EF and SQL Server and didn't have any issues getting the connection up and running.

Environment: VS 2008, Oracle 11g, dotConnect Oracle

AndreyR · Post by **AndreyR** » Thu 24 Sep 2009 07:00

Thank you for the report, we have already found this problem.
I will let you know as soon as it is fixed.

Discovery · Post by **Discovery** » Thu 24 Sep 2009 15:34

I think I have the same problem.
Just downloaded the trial version today and I get the following error:

'Unable to load the specified metadata resource'

in the bit of code below:

----
public GalleryEntities() :
base@"name=Discovery.GalleryManagerConnectionString", "GalleryEntities")
----

My App.Config has the following connectionstring

----

----

Would be nice to know if this is the same problem and when there might be a fix for it.

Thanks

AndreyR · Post by **AndreyR** » Fri 25 Sep 2009 12:21

Yes, it is the same problem. It is associated with placing the model not to the root folder of the project.
As a temporary workaround, move the model to the root project folder.

AndreyR · Post by **AndreyR** » Mon 02 Nov 2009 08:46

This problem is fixed in the latest Beta build of Entity Developer.

Wupaz · Post by **Wupaz** » Tue 24 Nov 2009 15:53

I use 2.20.43 (trial) and I have the same problem ?!?

And the model is int the root ...

Or I do something wrong ?

AndreyR · Post by **AndreyR** » Wed 25 Nov 2009 12:24

This problem was already discussed here:
http://www.devart.com/forums/viewtopic.php?p=50708