Thank you for your honest feedback about our recent move to stop development of Telerik Data Access integration with Visual Studio.
I understand your frustration. The fact that we are no longer shipping our Visual Designer does not mean that you are forced to stop using Q1 2015 (or any earlier) version of Telerik Data Access that contains all the tools that you are used to.
We will continue to deliver Q1 2015 package to existing clients when they request it (or you can actually download it from Your Account page in our site) and we will be offering help and guidance through either our support system or the community forums.
Moving away from Visual Studio integration will allow us to focus our attention to the runtime of the product and some other projects and we believe these are the right things to invest our time and effort into.
In general you have two options:
- continue using Q1 2015 version with RLINQ models without any additional effort
- migrate to code-only mapping and NuGet packages
Our recommendation for projects that are pass their active development phase is to use the first option, while projects that are just starting or in active development should be migrated to code-only mapping.
Of course you are the one that should make the choice according to your specific situation.
Getting back to your problem at hand - OpenAccessNuGet.targets
is optimized to work with Fluent models by default. You need to enable enhancing of RLINQ models there before you can use it. You have to set UseXmlMapping
build variable to true. You have two options to do that:
- Add <UseXmlMapping>true</UseXmlMapping> to your model project file like this:
Please add the code snippet above after between the last configuration-related PropertyGroup and the first ItemGroup.
<!-- Enable enhancing of RLINQ models when using NuGet packages -->
- Change OpenAccessNuGet.targets to set proper default value for UseXmlMapping:
While the second approach may seem easier to implement, bear in mind that the next time you update your NuGet targets file it will be replaces and you will have to redo the fix.
If you need any further assistance updating your project, please let us know.
Check out the latest announcement
about Telerik Data Access vNext as a powerful framework
able to solve core development problems.