LinqConnect Professional Version 4.1.151 - any big problem

[AKRRKA]

Use LinqConnect Professional Version 4.1.151 (20-Dec-2012). And have any big problem.
For easy I will tell based on the example included in the official installation package LinqConnect (CRM_Demo from c:\Program Files (x86)\Devart\dotConnect\Linq\Samples\ and from http://www.devart.com/linqconnect/docs/CrmDemo.html).

Used Database - MySQL, Oracle, SQLite.
Problems by priority (max = 100, min = 1)

Pri:100 - If generate database from model, for table Orders result:

Code: Select all

CREATE TABLE crm_demo.Orders (
   OrderID INT(9) NOT NULL,
   CompanyID INT(9) NULL,
...
   PRIMARY KEY (OrderID),
   CONSTRAINT FK_Orders_Companies FOREIGN KEY (CompanyID) REFERENCES crm_demo.Companies (CompanyID),
   CONSTRAINT FK_Orders_Companies FOREIGN KEY (ShipCompanyID) REFERENCES crm_demo.Companies (CompanyID),
   CONSTRAINT FK_Orders_Person_Contacts FOREIGN KEY (ContactID) REFERENCES crm_demo.Person_Contacts (ContactID)
)

as you see, two CONSTRAINT with one name FK_Orders_Companies, this is error! By sample mus be like this:

Code: Select all

...
   CONSTRAINT FK_Orders_Companies_CompanyID FOREIGN KEY (CompanyID) REFERENCES crm_demo.Companies (CompanyID),
   CONSTRAINT FK_Orders_Companies_ShipCompanyID FOREIGN KEY (ShipCompanyID) REFERENCES crm_demo.Companies (CompanyID),
...

Pri:70 - If chenge name for class "Order" to "OrderTable", property Entity Set don`t chenge and name remains old value as "Orders", but must be "OrderTables".

Pri:20 - If chenge name for class "Order" to "OrderTable", Navigation Properties in classes Person_Contact, Company and Order_Detail don change name to new "OrderTables".

Very much I ask to fix the problem as soon as possible, it does not allow us to release the product in time.
Maximum priority issue is very important.

PS: My developer license number is CRUni-00787 and CRSqlED-00467.

[MariiaI]

Thank you for the report. We have reproduced these issues. We will inform you as soon as they are fixed.

[AKRRKA]

I test LinqConnect Professional Version 4.1.169 (17-Jan-2013)
Problem with Pri:100 and Pri:70 was resolved (Thanks!).

PS: Problem with Pri:20 don`t resolve.

[MariiaI]

Yes, the first and second issues, related to the error when generating database script with the same names for some constraints and not renaming the EntitySet property after the entity class name has been changed, are fixed in LinqConnect 4.1.169.

The new build can be downloaded from http://www.devart.com/linqconnect/download.html (trial version) or from Registered Users' Area (for users with valid subscription only).
For more information, please refer to http://forums.devart.com/viewtopic.php?f=31&t=25663

As for the third issue with Navigation Properties, this is the designed behaviour.