Hey guys,
since the latest VS2019 update im receiving a "bufferAdapter is not a VSTextDocData" error when pressing Ctrl+S to save inside VS in the DB editor. Closing the diagram gets the confirmation for saving which works fine.
VS2019: 16.7.3
LinqConnect: 4.9.2033.0
EntityDeveloper: 6.8.1049.0
bufferAdapter is not a VSTextDocData
Re: bufferAdapter is not a VSTextDocData
We have reproduced the error with .NET Core / .NET 5 projects in VS2019 v16.7 and will notify you when it is fixed.
-
- Posts: 26
- Joined: Thu 06 Feb 2020 18:23
Re: bufferAdapter is not a VSTextDocData
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.
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.
-
- Posts: 26
- Joined: Thu 06 Feb 2020 18:23
Re: bufferAdapter is not a VSTextDocData
Ok thank you for your feedback.
I will try that way for now.
I will try that way for now.
Re: bufferAdapter is not a VSTextDocData
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 Entity Developer v6.11.1219: viewtopic.php?f=32&t=44957.
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.
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.