Search found 8 matches
- Wed 22 Sep 2021 09:32
- Forum: Entity Developer
- Topic: Visual Studio 2022
- Replies: 29
- Views: 1097436
Re: Visual Studio 2022
Thanks Shalex
- Fri 10 Sep 2021 08:35
- Forum: Entity Developer
- Topic: Visual Studio 2022
- Replies: 29
- Views: 1097436
Visual Studio 2022
Is there going to be a Visual Studio 2022 compatible version of Entity Developer available?
If so when will we be able to try it out? I need to keep working on an older project for a while until it is phased out next year so am planning ahead for November when VS2022 is officially released.
Thanks
If so when will we be able to try it out? I need to keep working on an older project for a while until it is phased out next year so am planning ahead for November when VS2022 is officially released.
Thanks
- Wed 07 Oct 2020 09:22
- Forum: Entity Developer
- Topic: EF insert using SQL view suddenly giving optimistic concurrency error
- Replies: 5
- Views: 11301
Re: EF insert using SQL view suddenly giving optimistic concurrency error
After much testing I have identified the issue as being related to Entity Developer.
It appears that as long as the highest version number of ED I use is 6.7.965 then all is well. Any version newer than that (tested up to 6.9.1092) has the issue.
Luckily re-installing the older version, deleting the generated POCO's and regenerating them has worked.
It appears that as long as the highest version number of ED I use is 6.7.965 then all is well. Any version newer than that (tested up to 6.9.1092) has the issue.
Luckily re-installing the older version, deleting the generated POCO's and regenerating them has worked.
- Wed 16 Sep 2020 08:07
- Forum: Entity Developer
- Topic: EF insert using SQL view suddenly giving optimistic concurrency error
- Replies: 5
- Views: 11301
Re: EF insert using SQL view suddenly giving optimistic concurrency error
@Shalex Thanks for the reply, however isn't that only in MySQL? Never come across that one for MS SQL and so far can't find any reference to it anywhere.
- Mon 14 Sep 2020 15:05
- Forum: Entity Developer
- Topic: EF insert using SQL view suddenly giving optimistic concurrency error
- Replies: 5
- Views: 11301
EF insert using SQL view suddenly giving optimistic concurrency error
For the last few weeks I am seeing the following error in my development code whenever any insert using an SQL view happens in our code base -
"Store update, insert, or delete statement affected an unexpected number of rows (0). Entities may have been modified or deleted since entities were loaded. See http://go.microsoft.com/fwlink/?LinkId=472540 for information on understanding and handling optimistic concurrency exceptions."
App is using EF6.2
My colleagues do not get the error using the exact same code (pull my feature branch and run it). We are using VS2019 and Devart’s Entity Developer.
This all started after updates to my development machine e.g. VS 16.7.1, ED 6.8.1049, etc.
Pseudo code which is failing
The class maps through Entity Developer (model first) to a SQL view. This is an insert of a new object, NOT an edit of an existing one.
I know how to handle optimistic concurrency so please don't suggest ways to do that. The problem is that suddenly working code has stopped working.
I have tried, removing the updates which applied, also used a separate PC - a fresh Windows install, with older versions VS 16.6.5 and ED 6.8.1019 (also repeated using latest versions) and I still get the same error.
Error also follows if I deploy code (VS Publish) to a Cloud service but not if a colleague deploys the same code.
Any ideas are appreciated.
"Store update, insert, or delete statement affected an unexpected number of rows (0). Entities may have been modified or deleted since entities were loaded. See http://go.microsoft.com/fwlink/?LinkId=472540 for information on understanding and handling optimistic concurrency exceptions."
App is using EF6.2
My colleagues do not get the error using the exact same code (pull my feature branch and run it). We are using VS2019 and Devart’s Entity Developer.
This all started after updates to my development machine e.g. VS 16.7.1, ED 6.8.1049, etc.
Pseudo code which is failing
Code: Select all
context.<model class>.AddObject(model);
context.SaveChanges(); <= Error happens when this executes
I know how to handle optimistic concurrency so please don't suggest ways to do that. The problem is that suddenly working code has stopped working.
I have tried, removing the updates which applied, also used a separate PC - a fresh Windows install, with older versions VS 16.6.5 and ED 6.8.1019 (also repeated using latest versions) and I still get the same error.
Error also follows if I deploy code (VS Publish) to a Cloud service but not if a colleague deploys the same code.
Any ideas are appreciated.
- Thu 23 May 2019 14:03
- Forum: Entity Developer
- Topic: Entity Developer in Visual Studio 2019
- Replies: 5
- Views: 10577
Re: Entity Developer in Visual Studio 2019
Thanks Shalex
- Wed 22 May 2019 16:16
- Forum: Entity Developer
- Topic: Entity Developer in Visual Studio 2019
- Replies: 5
- Views: 10577
Re: Entity Developer in Visual Studio 2019
Hi Shalex,
Is there any update on when this issue will be addressed please?
As of today's update to Visual Studio 2019 (16.1.0) the Entity Developer extension is not being loaded by Visual Studio. Quote -
Following the link after this it showed the Entity Developer Extension as the one not being loaded.
Thanks
Is there any update on when this issue will be addressed please?
As of today's update to Visual Studio 2019 (16.1.0) the Entity Developer extension is not being loaded by Visual Studio. Quote -
.Visual Studio did not load one or more extensions that were using deprecated API's
Following the link after this it showed the Entity Developer Extension as the one not being loaded.
Thanks
- Wed 17 Apr 2019 15:21
- Forum: Entity Developer
- Topic: Entity Developer in Visual Studio 2019
- Replies: 5
- Views: 10577
Entity Developer in Visual Studio 2019
Using Entity Developer and have the latest version 6.4.719 installed. Visual Studio 2019 is still notifying me that "This extension uses deprecated API's and will not be compatible with a future Visual Studio update".
Hopefully Devart is already aware of this happening and is working on a fix for this potential future issue. No doubt other extensions are also going to be affected.
Hopefully Devart is already aware of this happening and is working on a fix for this potential future issue. No doubt other extensions are also going to be affected.