The outcome you experienced with Data Access Q2 2016 is expected. It is due to the deprecation of the Visual Studio integration in Q2 2015 (the .rlinq files are supported). Currently, Data Access is distributed only through its NuGet packages
. More details on the deprecation are available in this blog post
. In order to maintain your existing projects that consume Data Access (especially such with .rlinq files), you can apply any of the following suggestions:
Option 1: Migrate the .rlinq file to a fluent model and integrate the NuGet packages. The details and the workflow about the migration process are available here
Option 2: Freeze the version of Data Access on Q1 2015. Since Data Access Q1 2015 is the last version that distributes the Visual Studio integration, with this option you won't need to migrate the model.
In both cases, you will need to obtain Data Access Q1 2015. You can do so from here
I hope this helps. Let me know if you need further information.
Telerik by Progress
Check out the latest announcement
about Telerik Data Access vNext as a powerful framework
able to solve core development problems.