Multiple external mapping files generated

Discussion of open issues, suggestions and bugs regarding LinqConnect – Devart's LINQ to SQL compatible ORM
Post Reply
zsolt.soczo@gmail.com
Posts: 10
Joined: Mon 30 May 2011 20:58

Multiple external mapping files generated

Post by zsolt.soczo@gmail.com » Wed 01 Jun 2011 20:59

Sometimes when I run the custom tool for xxx.lqml in VS 2010 it generates a new mapping file, xxx2.xml, xxx22.xml, etc. What is the reason of this behavior?

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

Post by StanislavK » Thu 02 Jun 2011 14:31

Could you please specify the steps you perform when this issue occurs? We couldn't reproduce this behaviour in our environment.

zsolt.soczo@gmail.com
Posts: 10
Joined: Mon 30 May 2011 20:58

Post by zsolt.soczo@gmail.com » Thu 02 Jun 2011 15:55

I could reproduce it. It happens in Visual Studio, when the .xml file is read only, because it is not checked out of the source control.
The DevartLinqToSqlGenerator tries to update the mapping file, but it can't, because it is read only. I think this is the main reason of the problem.

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

Post by StanislavK » Fri 03 Jun 2011 15:17

Could you please specify the source control system you are using? I've tried setting the file to be read-only, and was prompted to make it writable when saving the model.

zsolt.soczo@gmail.com
Posts: 10
Joined: Mon 30 May 2011 20:58

Post by zsolt.soczo@gmail.com » Fri 03 Jun 2011 16:36

In my machine it does not depends on the source control, i simply make the file read only using explorer it reproduce the issue.
To make sure, it happens in Visual Studio, not in Entity Developer.

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

Post by StanislavK » Mon 06 Jun 2011 08:20

Could you please specify the following:
- the product you are using (e.g., LinqConnect or dotConnect for Oracle);
- the exact (including the build number) version of this product;
- the operating system you are using;
- the version and edition of Visual Studio you are using.

At the moment, we couldn't reproduce this issue.

Post Reply