Compile old RDLCs in VS2019

Bryan Valencia 1 Reputation point
2021-05-20T22:50:56.96+00:00

Winforms
SQL Server

I have a project that I designed in VS2015 Pro.
I wanted to load it in VS2019 Pro.

EPIC FAIL.

Loaded the project into VS 2019, build failed, the MSI installer was incompatible, error, error after miserable error. Then I exited WITHOUT SAVING.

NOW when I try to edit my RDLC reports in VS2015, I have lost the Report designer, and the reports open as raw XML files.

When I execute my reports in the debugger from VS2019, I get this:

Microsoft.Reporting.WinForms.LocalProcessingException
  HResult=0x80131500
  Message=An error occurred during local report processing.
  Source=Microsoft.ReportViewer.WinForms
  StackTrace:
   at Microsoft.Reporting.WinForms.LocalReport.EnsureExecutionSession()
   at Microsoft.Reporting.WinForms.LocalReport.SetParameters(IEnumerable`1 parameters)
   at Onesource.Reports.ShippedNotInvoiced.ShippedNotInvoicedReport.SetParameters() in C:\...\Reports\ShippedNotInvoiced\ShippedNotInvoicedReport.cs:line 124

  This exception was originally thrown at this call stack:
    [External Code]

Inner Exception 1:
DefinitionInvalidException: The definition of the report '' is invalid.

Inner Exception 2:
ReportProcessingException: The definition of this report is not valid or supported by this version of Reporting Services. The report definition may have been created with a later version of Reporting Services, or contain content that is not well-formed or not valid based on Reporting Services schemas. Details: The report definition has an invalid target namespace 'http://schemas.microsoft.com/sqlserver/reporting/2016/01/reportdefinition' which cannot be upgraded.

My packages.config looks like this:

<?xml version="1.0" encoding="utf-8"?>
<packages>
  <package id="Microsoft.Office.Interop.Outlook" version="15.0.4797.1003" targetFramework="net45" />
  <package id="Microsoft.ReportViewer.2015" version="12.0.2.2403" targetFramework="net45" />
  <package id="Microsoft.ReportViewer.2015.Runtime" version="12.0.2.2402" targetFramework="net45" />
  <package id="Microsoft.ReportViewer.Runtime.Common" version="12.0.2402.15" targetFramework="net45" />
  <package id="Microsoft.ReportViewer.Runtime.WinForms" version="12.0.2402.15" targetFramework="net45" />
  <package id="Microsoft.ReportViewer.VS2015.WinForms" version="12.0.2.2402" targetFramework="net45" />
  <package id="Microsoft.SqlServer.Types" version="14.0.314.76" targetFramework="net45" />
  <package id="Shared.Management.Objects.for.SQL.Server.2012.SP1" version="11.0.3000.0" targetFramework="net45" />
</packages>
Visual Studio
Visual Studio
A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.
4,441 questions
SQL Server Reporting Services
SQL Server Reporting Services
A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
2,735 questions
VB
VB
An object-oriented programming language developed by Microsoft that is implemented on the .NET Framework. Previously known as Visual Basic .NET.
2,507 questions
0 comments No comments
{count} votes

6 answers

Sort by: Most helpful
  1. Joyzhao-MSFT 15,561 Reputation points
    2021-05-21T08:43:44.85+00:00

    Hi @Bryan Valencia

    Microsoft.Reporting.WinForms.LocalProcessingException HResult=0x80131500

    The error seems to have nothing to do with the report itself, but more of a problem caused by VS. However, I still recommend that you change to a simple report and repeat your previous steps for testing to rule out problems with the report itself.
    I'm not sure whether it is a version incompatibility. I have added VS-related tags for you. I hope that experts in this area can help you.
    Best Regards,
    Joy

    0 comments No comments

  2. Bryan Valencia 1 Reputation point
    2021-05-25T19:35:11.327+00:00

    So, what is a "Simple Report"?

    0 comments No comments

  3. Karen Payne MVP 35,016 Reputation points
    2021-05-25T20:51:14.947+00:00

    There are many items that will not work with .NET Core, the reports are not available at this time. You need to look for an alternate reporting tool e.g. FastReports for example which is not free and was pick randomly.

    0 comments No comments

  4. Bryan Valencia 1 Reputation point
    2021-05-25T22:07:35.517+00:00

    This isn't core.


  5. Bryan Valencia 1 Reputation point
    2021-05-25T22:57:16.013+00:00

    First I had to make sure these 2 were installed under Extensions in the VS menu.

    99598-manageextensions.jpg

    Then I updated Packages to this:
    <?xml version="1.0" encoding="utf-8"?>
    <packages>
    <package id="Microsoft.Office.Interop.Outlook" version="15.0.4797.1003" targetFramework="net45" />
    <package id="Microsoft.Report.Viewer" version="11.0.0.0" targetFramework="net45" />
    <package id="Microsoft.ReportingServices.ReportViewerControl.WebForms" version="150.1449.0" targetFramework="net45" />
    <package id="Microsoft.ReportingServices.ReportViewerControl.Winforms" version="150.1449.0" targetFramework="net45" />
    <package id="Microsoft.ReportViewer.2015" version="12.0.2.2403" targetFramework="net45" />
    <package id="Microsoft.ReportViewer.2015.Runtime" version="12.0.2.2402" targetFramework="net45" />
    <package id="Microsoft.ReportViewer.Common" version="10.0.40219.1" targetFramework="net45" />
    <package id="Microsoft.ReportViewer.Runtime.Common" version="12.0.2402.15" targetFramework="net45" />
    <package id="Microsoft.ReportViewer.Runtime.WinForms" version="12.0.2402.15" targetFramework="net45" />
    <package id="Microsoft.ReportViewer.VS2015.WinForms" version="12.0.2.2402" targetFramework="net45" />
    <package id="Microsoft.ReportViewer.WinForms" version="10.0.40219.1" targetFramework="net45" />
    <package id="Microsoft.SqlServer.Types" version="14.0.1016.290" targetFramework="net45" />
    <package id="Shared.Management.Objects.for.SQL.Server.2012.SP1" version="11.0.3000.0" targetFramework="net45" />
    </packages>

    This required REMOVING all the reporting services 2015 and older stuff.

    I did NOT have to delete reportviewers from my forms and recreate them all (thank God).

    Then I updated my app from old old old .NET Framework to .NET Framework 4.7.2.
    This actually crashed Visual Studio but the project loaded right back up after.

    I KNOW that I will run into similar issues with the Installer builder project in this solution, as it refuses to build right now.

    But I think we're on the right course.