EntityDeveloper.exe version 2.20.30 stopped responding

Michael_Grønbæk · Post by **Michael_Grønbæk** » Thu 30 Jul 2009 13:38

Hi Devart,

When I try to use the feature - LINQ to SQL:

"Create from database..."

in EntityDeveloper version 2.20.30.0 it stops responding without any indication to what the error can be. The only thing to do is to kill the process.

With this version I am no longer able to create from database.

I have done so a great many times using the previous version - the one released before v5.25.37 (e.g. v5.20.33) without any problems.

I am running on both Windows Vista and Windows XP utilizing an Oracle 10.2 XE on both platforms. The content of the database has not changed.

I am running in direct mode and the EntityDeveloper succesfully verifies the connection to the database.

The features I am using are Oracle Packages (Stored Procedures and functions) and VIEWS that are mapped.

I get no indication in the Windows Eventlog about what went wrong.

Can you provide some hints to why this version of EntityDeveloper is not working for me.

Best regards
Michael

AndreyR · Post by **AndreyR** » Thu 30 Jul 2009 14:37

We have already found and fixed similar problem associated with the Direct connection mode.
Which mode do you use: Direct or OCI?

Michael_Grønbæk · Post by **Michael_Grønbæk** » Thu 30 Jul 2009 15:02

Hi,

In the Entity Developer Database reverse engineering wizard I click the Direct-optional flag - thus I guess this must be direct-mode.

I am not in any way calling into OCI by using an API.

Regards,
Michael

AndreyR wrote:We have already found and fixed similar problem associated with the Direct connection mode.
Which mode do you use: Direct or OCI?

AndreyR · Post by **AndreyR** » Thu 30 Jul 2009 15:26

That should be the cause of the problem.
The bug is fixed, the fix will be included in the nearest build.

Michael_Grønbæk · Post by **Michael_Grønbæk** » Thu 30 Jul 2009 15:45

Sounds great - as always - when is the next build?

//Michael

AndreyR wrote:That should be the cause of the problem.
The bug is fixed, the fix will be included in the nearest build.

AndreyR · Post by **AndreyR** » Mon 03 Aug 2009 10:59

We plan to release the new build in several days.