Missing assembles OpenAccess when building

[Marcel]

Hello,

I am receiving the following error after I started to work on a solution on a second computer which uses Windows 10 and Visual Studio 2013. On the other computer with Windows 7 and Visual Studio 2013 the solution builds fine.

 

Error78 The "OpenAccessDeploy" task could not be loaded from the assembly C:\<Project directory>\OpenAccessAssemblies\enhancer.exe. Could not load file or assembly 'Microsoft.Build.Utilities, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.<Project Name>

 

Also the Visual Designer is not able to load the rlinq file and visualize it, it shows now xml.

I already tried to reinstall Telerik DataAccess and cleaned and rebuild the solution but without success.

 

Please let me know how to solve this.

 

Regards,

Marcel

 

[Doroteya]

Hello Marcel,

This error could appear on Windows 10 because it doesn't have .NET Framework 3.5 installed out-of-the-box. The solution in this case, as well as a few additional ideas are available in this forum thread.

I hope this helps.

Regards,
Doroteya
Telerik by Progress

 

[Marcel]

Thanks Doroteya, building the solution works now.

But I can still not open the rlinq file?

Any suggestions?

Marcel

[Doroteya]

Hi Marcel,

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.

Regards,
Doroteya
Telerik by Progress