Thanks to Rhys Schmidtke, Senior Software Engineer, for contributing content to today’s post.A few weeks ago, of an updated Report Viewer control to NuGet, enabling you to embed paginated reports into your existing ASP.NET Web Forms apps and incorporating several enhancements we made for SSRS 2016, including modern browser support. Since then, many of you have tried the Release Candidate and shared your feedback. Today, we’re pleased to announce an updated Release Candidate for you to try. What’s new in this updateWith this update, the Report Viewer control. Includes resource files for 14 supported languages.
Install Microsoft Reportviewer Web Forms 9.0.0.0
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.ReportViewer.WinForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. 'cd 9.0.0.0b03f5f7f11d50a3a' if you have 9.0.0.0 and press 'enter'. You should be able to see the following DLL in this folder: Microsoft.ReportViewer.ProcessingObjectModel.dll 2(iv). Now use the following command to copy the dll file to your bin directory: copy.dll d: YourProject bin 3. COPY Microsoft.ReportViewer.Common.
Supports and renders properly on pages that use ASP.NET master pages. Supports pages accessed over HTTPS. Provides improved error messages in some common cases when the control might not be configured properlyFirst things firstIf you installed the previous Release Candidate into your app, you’ll need to first uninstall it. Great to see improvements being made!
However I just investigated updating and hit a potential issue.The previous preview “Microsoft.ReportViewer.Common.dll” referenced “Microsoft.SqlServer.Types.dll” version 13 which in turn referenced “SqlServerSpatial130.dll”. These other DLLs were installed as part of SQL Server 2016 or by installing Microsoft System CLR Types from the SQL Server 2016 Feature Pack.The new “Microsoft.ReportViewer.Common.dll” references “Microsoft.SqlServer.Types.dll” version 14 which is now part of the NuGet package. Which SQL Server version does this come from? It references “SqlServerSpatial140.dll” which doesn’t exist on a machine with SQL Server 2016 installed?
No, the control depends on the v14 assemblies, but the NuGet package includes most of them, including Microsoft.SqlServer.Types; the exception is SqlServerSpatial, which is a native (rather than managed) assembly and comes in x86 and x64 flavors. We’re considering adding it to the NuGet package (you’d need to add a line of code to your app to load the correct flavor, just as you do with the Entity Framework’s NuGet package), and regardless, an eventual SQL Server vNext Feature Pack would include it. Indeed you shouldn’t need to install the full SQL Server product just to get this assembly. If your aim is to deliver an improved report viewer control for SQL Server 2016 I don’t understand why you’d make it depend on beta vNext/CTP binaries? Will SQL Server 2016 never have a stable report viewer control?At the moment it renders it unusable for us as our application depends on “Microsoft.SqlServer.Types.dll” and its downstream native binaries to interact with geography columns via Entity Framework. We could reference v14 of this but currently that would require installation of SQL Server vNext/CTP onto Production servers which isn’t ideal and I can’t find a Feature Pack which might have a standalone CLR Types install for it.I guess if the NuGet package was updated to v14 (currently v11) and included native assemblies and a utility to load them it would provide a workable solution although it would still include beta SQL Server assemblies? Our aim is to deliver a single Report Viewer control that supports multiple versions of SSRS (currently, SSRS 2008 through 2016 and now vNext too), not just SSRS 2016.
We’re including all the assemblies you need, including Microsoft.SqlServer.Types, in the NuGet package – with SqlServerSpatial the outstanding exception. Again, I agree you shouldn’t need to install the full SQL Server product just to get this assembly; merely as a workaround for now, you can install it (on any server, not necessarily your production server) to get a copy. Once we have an updated Feature Pack, you’ll have the usual way to get the assembly, and as I said, we’re considering adding it to the NuGet package as well.
Install Microsoft.reportviewer.webforms
Hello,Just to confirm (by reading the response from Thomas D.’s question), currently Report Viewer Control 2016 does NOT support rendering Power BI Reports? So you can upload Power BI reports to SSRS 2016 but they are only viewable through the Report Manager Dashboard?We were testing the report viewer 2016 in our MVC app and are using the reports from the “Technical Preview” VM in Azure, and weren’t able to open any of the Power BI reports that were in the Report Dashboard. We got an error message saying “The operation you are attempting on item ‘Sample Sales Report’ is not allowed for this item type. (rsWrongItemType)”.If the above is true, is this something you don’t see it being supported any time soon? What is our best course of action for integrating both SSRS and Power BI in our MVC application?
Using Report Viewer Control 2016 and Power BI Embedded?ThanksJen.
Microsoft Report Viewer 9.0 Download
Dear all,We had a.Net 2 (Visual Studio 2008) website which we have upgraded to.Net 4 and VS2010. This used ReportViewer to access the reporting services reports. (We have upgraded to SQL 2008 as well now.)I have changed my solution to use ReportViewer v10, and I can see that from the references, and I have changed all pages and web.config to point to v10 too. However when I run the deployed website I get the following error: Could not load file or assembly 'Microsoft.ReportViewer.WebForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.I can't understand where it's looking for the v9 assembly from. Has anyone seen this problem before on how to fix it?Kind regardsSidharthSnippets from web.config.