bufferAdapter is not a VsTextDocData

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for MySQL
Post Reply
raubv0gel
Posts: 14
Joined: Mon 27 Apr 2020 12:35

bufferAdapter is not a VsTextDocData

Post by raubv0gel » Thu 12 Nov 2020 22:01

Any help on this? Image

I have a new project using .NET 5. I’m trying to use EF 6 and Devart dotconnect.

Shalex
Site Admin
Posts: 9269
Joined: Thu 14 Aug 2008 12:44

Re: bufferAdapter is not a VsTextDocData

Post by Shalex » Fri 13 Nov 2020 11:37

The latest updates of Visual Studio 2019 brought a number of changes in behavior that is incompatible with older versions. Entity Developer integrated into VS2019 (Normal and Preview) has problems in a number of scenarios with saving models for .NET Core and .NET 5 projects. For now, we recommend that you use the standalone Entity Developer for .NET 5 development whenever possible to avoid losing your changes.

We are working on solving the arisen problems with VS2019.

As a temporary workaround, save the model in VS2019 via File > Save As and leave the original name. It should work this way.

raubv0gel
Posts: 14
Joined: Mon 27 Apr 2020 12:35

Re: bufferAdapter is not a VsTextDocData

Post by raubv0gel » Fri 13 Nov 2020 12:55

Thanks for advice! Changing the Model, closing it, will prompt for saving changes – works too.

I’m looking forward to see VS 2019 16.8 and EF 5 support.

Best regards!

Shalex
Site Admin
Posts: 9269
Joined: Thu 14 Aug 2008 12:44

Re: bufferAdapter is not a VsTextDocData

Post by Shalex » Fri 04 Dec 2020 21:06

Entity Framework Core 5.0 is supported by dotConnect for MySQL v8.19: viewtopic.php?f=2&t=44278.

Shalex
Site Admin
Posts: 9269
Joined: Thu 14 Aug 2008 12:44

Re: bufferAdapter is not a VsTextDocData

Post by Shalex » Mon 12 Apr 2021 13:47

The bug with throwing "bufferAdapter is not a VsTextDocData" when saving a model in .NET Core, .NET Standard, .NET 5, .NET 6 projects of Visual Studio 2019 is fixed in dotConnect for MySQL v8.19.1866: viewtopic.php?f=2&t=45001.

Be aware of a side effect caused by our fix - the diagram window of a model is not marked with the asterisk in its tab title in Visual Studio after the model has been modified. We will look for a solution to this issue.

Post Reply