Upgrade issue (from 3 to 4)

Discussion of open issues, suggestions and bugs regarding LinqConnect – Devart's LINQ to SQL compatible ORM
Post Reply
nimli
Posts: 5
Joined: Fri 21 Jan 2011 22:36

Upgrade issue (from 3 to 4)

Post by nimli » Fri 10 Jan 2014 16:35

Hello,

While testing an upgrade from 3.1 to 4.4, I see the following error during code-recompilation:

The type of namespace name 'KeyGenerator' does not exist in the namespace 'Devart.Data.Linq.Mapping' (are you missing an assembly reference?)

This comes from the {OurProject}.Designer.cs file.

Looking at the Object Browser, I see in "Devart.Data.Linq" of LinqConnect 3.1, there's namespace "Devart.Data.Linq.Mapping.KeyGenerator". However, this namespace does not exist in the same dll of version 4.4.

I wonder if I've missed anything in my test. What should I do to solve this issue?

Thank you!!

MariiaI
Devart Team
Posts: 1472
Joined: Mon 13 Feb 2012 08:17

Re: Upgrade issue (from 3 to 4)

Post by MariiaI » Mon 13 Jan 2014 10:43

We have made a major refactoring of the LinqConnect engine since version 4.0 and since this version the references to System.Data.Linq are removed, and LinqConnect uses only its own classes. So it is necessary to replace all occurrences of "System.Data.Linq." with "Devart.Data.Linq.".
Please check that your code (*.Designer.cs file) doesn't contain "System.Data.Linq." and there is no reference to the System.Data.Linq assembly. Please re-generate your model with the assemblies from the new version and tell us about the results.

nimli
Posts: 5
Joined: Fri 21 Jan 2011 22:36

Re: Upgrade issue (from 3 to 4)

Post by nimli » Thu 16 Jan 2014 00:56

Thank you for getting back to us.

Instead of re-generating the codes, we try the "Upgrade Wizard" again. But this time, we click the checkbox that says "Remove System.Data.Linq reference from source." Afterward, we are able to re-compile the code.

The issue is solved. Thank you!

MariiaI
Devart Team
Posts: 1472
Joined: Mon 13 Feb 2012 08:17

Re: Upgrade issue (from 3 to 4)

Post by MariiaI » Thu 16 Jan 2014 06:25

Glad to see that the issue was resolved. If you have any further questions, feel free to contact us.

Post Reply