Entity Data Model Wizard fails with Jan 14th version entity

[SuperDave]

Looks like because the password is not included in the Entity Connection string using the Entity Data Model Wizard that it fails because it can't establish a connection.

VS 2010 X64 - MYSQL 5.5 dotConnect 5.50.79.0 - Win 7

[AndreyR]

If you choose not to persist the security info in your connection string then it's your responsibility to pass the password
to the connection string. Create the ObjectContext instance with a separate entity connection in your code
if you wish to have full control over it.

[SuperDave]

I can see you didn't bother to try the entity data model wizard. Why don't you try and they tell me where you can do this. Maybe you don't support the Wizard but you could just tell me that.

[AndreyR]

Set the connection string Persist Security Info to true. If it is set to false, EDM Wizard performs an attempt to
open the connection defined by the given connection string and fails because of the lack of password in it.
It is a limitation since EF v1.
As for saving the connection string in app.config, my recommendations are still valid.

[SuperDave]

user id=Catburt;password=******;host=192.150.5.100;database=poadoc;persist security info=True

Is the way it has been set.

Wizard still fails to connect.

[AndreyR]

Please try with the brand new connection with Persist Security Info==true.
If the error persists, please let me know the precise error message and the call stack..

[SuperDave]

I can only believe you don't know what the Entity Data Model Wizard or you wouldn't have posted the last message.

Why don't you try using it.

[SuperDave]

An Error occurred while connectiong to the database. The database might be unavailable. An exception of type System.Data,EntityCommandExecuationException occurred. The error message is :An error occurred wheil executing the command definition, see the inner exception for details the inner exception caught was of type Devart.data.MySQL.MySwlException with this error message: 'Select command denied to user ****@********** for table proc.

[AndreyR]

Thank you for the clarification. The problem is that the user you are connecting to the database with
does not have necessary privileges (namely, metadata quering). EDM Wizard needs this data, and we
don't have any opportunity to wrap the raised exception.
I can see two alternatives - either you grant more privileges to your user (maybe use a more prvileged user)
or use Entity Developer (the compatible with EF v4 version will be available soon).

[cjbiggs]

How soon with EF 4 support be available in the Entity Developer?

[AndreyR]

We plan to release the compatible with VS 2010 Beta 2 build of Entity Developer in a week or so.