File-based XML mapping loading problem

Discussion of open issues, suggestions and bugs regarding LinqConnect – Devart's LINQ to SQL compatible ORM
crazypit
Posts: 163
Joined: Wed 15 Apr 2009 08:43

Post by crazypit » Mon 31 Jan 2011 14:02

Using the latest version, i still get a XmlSchemaException : Guid

at Devart.Data.Linq.Mapping.aj.b(XmlReader A_0, String[] A_1)
at Devart.Data.Linq.Mapping.aj.g(XmlReader A_0)
at Devart.Data.Linq.Mapping.XmlMappingSource.FromReader(XmlReader reader)
at Devart.Data.Linq.Mapping.XmlMappingSource.FromStream(Stream stream)

If i remove all the Guid attributes (what is this exactly? I opened an older lqml with the latest Entity Developer and when i saved, every entity & column had a Guid attribute...), i get a same MaxLength exception. Gosh...

StanislavK
Devart Team
Posts: 1710
Joined: Thu 03 Dec 2009 10:48

Post by StanislavK » Tue 01 Feb 2011 15:18

Guid' is a new keyword used for internal purposes only. The problem with Guids is the same issue as the one that occurs with other non-standard mapping keywords. We are working on it, but cannot provide any timeframe. At the moment, we can only suggest to remove these keywords manually or create a simple program that will remove them automatically.

crazypit
Posts: 163
Joined: Wed 15 Apr 2009 08:43

Post by crazypit » Wed 02 Feb 2011 07:51

Well, ok, but i've been trying to load mapping from file for over a month now. And i think this is a much more critical issue than e.g. support for multiple diagrams per model in Entity Developer...

crazypit
Posts: 163
Joined: Wed 15 Apr 2009 08:43

Post by crazypit » Fri 04 Mar 2011 11:32

It's been a month. Anything new on that?

StanislavK
Devart Team
Posts: 1710
Joined: Thu 03 Dec 2009 10:48

Post by StanislavK » Wed 09 Mar 2011 12:54

We plan to implement substantial changes related to model building and code generation in the next minor version (not build) of Entity Developer. In particular, this issue should be fixed within these changes.

We will post here when this version is released.

StanislavK
Devart Team
Posts: 1710
Joined: Thu 03 Dec 2009 10:48

Post by StanislavK » Fri 22 Apr 2011 09:39

We have fixed the problem with external mapping for LinqConnect models: if the Mapping Mode property of the model is set to File, a separate .xml file containing only standard mapping elements is now created. These changes are available in the latest 2.50.22 Beta build of LinqConnect. The new build can be downloaded from
http://www.devart.com/linqconnect/download.html
(the trial version) or from Registered Users' Area (provided that you have an active subscription):
http://secure.devart.com/

For more information about the fixes and improvements available in LinqConnect 2.50 Beta, please refer to
http://www.devart.com/forums/viewtopic.php?t=20827

Post Reply