Devart Forums

Hello,

I noticed some strange changes in Entity Developer.
Changed the algorithm for constructing the foreign keys and relationships between objects.

Algorithm 1:

Read Only = False
Update Check = Always

Algorithm 2:

Read Only = True
Update Check = Never

In older versions, about a year ago, was algorithm 1.
I had some problems with the model and you in the next hotfix fixed the problem and switched to the algorithm 2.

And in the latest version appeared again behavior algorithm 1.

Why?
How is that better?
And why did all foreign keys are not changed automatically Entity Developer the first algorithm, only newly created?

Thanks.

We have asked for an additional information by e-mail.

I sent you a video demonstration by mail.

Thank you for the additional information. We have changed this behavior. Starting from the next public build of LinqConnect, the foreign keys will be added to the entity classes with the following settings:
Read Only = False
Update Check = Never
JIC: this is related to scenarios when adding associations with the "Add foreign key properties to the child class" check box selected.

We will inform you when new build is available for download.

Please display a warning when detects not correct property.
Waiting for a new fixed version.

We will add warnings for such scenarios in Entity Developer and post here when new build is available for download.

Like as already released four versions. Or I missed or not yet ready?
Advice please, how are you doing with this feature?
Thanks.

MariiaI wrote:Starting from the next public build of LinqConnect, the foreign keys will be added to the entity classes with the following settings:
Read Only = False
Update Check = Never
JIC: this is related to scenarios when adding associations with the "Add foreign key properties to the child class" check box selected.

Please try the latest build of LinqConnect 4.4.499. New build can be downloaded from http://www.devart.com/linqconnect/download.html (trial version) or from Registered Users' Area (for users with active subscription only).

MariiaI wrote:We will add warnings for such scenarios in Entity Developer and post here when new build is available for download.

I'm about this.
Warnings are displayed?

Warnings for such scenarios will be displayed starting from the next build of LinqConnect/Entity Developer, which will be released in several weeks. We will inform you when it is available for download.

New build of LinqConnect 4.4.509 is available!
It can be downloaded from http://www.devart.com/linqconnect/download.html (trial version) or from Registered Users' Area (for users with active subscription only).
For more information, please refer to http://forums.devart.com/viewtopic.php?f=31&t=29688.

Thanks. Now show warnings.
But have any incorrect information.
Please see video:
Video_2014-06-02_144153.wmv (1.9 МБ)
http://rghost.ru/56086146

Thank you for the response. We will correct it to the next build of LinqConnect.

New build of LinqConnect 4.4.519 is available!
It can be downloaded from http://www.devart.com/linqconnect/download.html (trial version) or from Registered Users' Area (for users with active subscription only).
For more information, please refer to http://forums.devart.com/viewtopic.php?f=31&t=29782.