SSDT for VS2017 version 15.9.10 and Aspose.BarCode

Aspose.BarCode Product Family
1

When attempting to use Aspose.BarCode with this version of SQL Server Data Tools for Visual Studio 2017, an error message stating: “Could not load file or assembly ‘Microsoft.ReportingServices.Designer.Controls,Version 14.0.0.0, Culture=neutral,PublicKeyToken=89845dcd8080cc91’ or one of its dependencies. The system can not find the file specified.”

This is using Aspose.BarCode for Reporting Services 19.1, and the Bin\VS2019 assembly that should be the one used with this 15.8.1+ SSDT, 15.x version of Reporting Services.

Is there something wrong with the assembly or is this a defect?

Here is the version information for the version of SSDT being used.

Microsoft SQL Server Data Tools for Visual Studio 2017 (SSDT)
Version 15.9.10
VisualStudio.15.Release/15.9.10+28307.557
Microsoft .NET Framework
Version 4.7.03062

Installed Version: IDE Standard

Microsoft Visual Studio Tools for Applications 2017 00371-40000-00001-AA119
Microsoft Visual Studio Tools for Applications 2017

C# Tools 2.10.0-beta2-63501-03+b9fb1610c87cccc8ceb74a770dba261a58e39c4a
C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.

Common Azure Tools 1.10
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.

NuGet Package Manager 4.6.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.

Project 1.0
Information about my package

ProjectServicesPackage Extension 1.0
ProjectServicesPackage Visual Studio Extension Detailed Info

ResourcePackage Extension 1.0
ResourcePackage Visual Studio Extension Detailed Info

ResourcePackage Extension 1.0
ResourcePackage Visual Studio Extension Detailed Info

SQL Server Analysis Services 15.0.1331.137
Microsoft SQL Server Analysis Services Designer
Version 15.0.1331.137

SQL Server Data Tools 15.1.61903.01040
Microsoft SQL Server Data Tools

SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 15.0.1100.123

SQL Server Reporting Services 15.0.1331.137
Microsoft SQL Server Reporting Services Designers
Version 15.0.1331.137

SsmsVsIntegration 1.0
Information about my package

Visual Basic Tools 2.10.0-beta2-63501-03+b9fb1610c87cccc8ceb74a770dba261a58e39c4a
Visual Basic components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.

Visual Studio Code Debug Adapter Host Package 1.0
Interop layer for hosting Visual Studio Code debug adapters in Visual Studio

2

@uhhealth,
We are analysing your query and will get back to you soon to share our feedback.

3

@uhhealth,
We have analyzed the error message and it seems that it’s not an issue with Aspose.BarCode for RS. We guess you should manually copy the DLL from “C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Reporting Services” to “C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\CommonExtensions\Microsoft\SSRS (different target path than noted in other posts)”.

You may also check a stackoverflow.com thread for similar issue as follows:

If still your issue is not resolved, you may uninstall Visual Studio and SQL Server and then reinstall both. It’s better if you freshly install everything.

You may also try using some other machine to confirm that this is not an issue with Aspose.BarCode for RS rather it is with Microsoft.ReportingServices.Designer version issue. Maybe you have some older DLL in GAC etc. so you should browse online to fix the issue as follows:
https://social.msdn.microsoft.com/Forums/en-US/071d046d-65f4-4969-9c15-2f0321a2e68d/could-not-load-file-or-assembly-microsoftreportingservicesdesignerversion10000?forum=vstsstart

4

For the reporting services 2019 you need to copy dll from VS2019 folder. Or you could use configuration utility and setup “VS 2017 Community (x86)(SSRS 15.x)”.

Also there were changes in Aspose.BarCode for Reporting Services to VS2019 (will be in 19.6), however they were made only for Visual Studio 2019 which require .NET 4.6 instead 4.5 for these libraries.