RDLC reports on .NET Core 8

Marco 0

Hi at all,

I'm using a rdlc report inside a .net core 8 app but i'm getting this error

{"An error occurred during local report processing.;The definition of the report 'report path inside the project' is invalid.\r\nAn unexpected error occurred in Report Processing.\r\nCompiler executable file C:\WINDOWS\Microsoft.NET\Framework64\v8.0.2\vbc.exe cannot be found."}

It only work if i copy the vbc.exe from another .net framework version, but if i deployed the app in azure i can't do this. It's possible to solve this problem without the copy of vbc.exe(Visual Basic Command Line Compiler)?

Thanks

Fred Gates 5 Reputation points

2024-04-15T10:13:22.3833333+00:00

It seems you’re encountering a common issue with RDLC reports in .NET Core where the system is looking for the vbc.exe compiler executable in a directory that doesn’t exist. This is because RDLC reports were originally designed to work with the .NET Framework, and .NET Core does not include the Visual Basic compiler by default.

Here are a few steps you can take to resolve this issue without copying vbc.exe:

Ensure Compatibility: Make sure that the AspNetCore.Reporting package you’re using is compatible with .NET Core 8. This package is often used to render RDLC reports in .NET Core applications.

Update NuGet Packages: Update all related NuGet packages to their latest versions that support .NET Core 8. This might include My Milestone Card Microsoft.ReportViewer.WebForms, Microsoft.ReportViewer.ProcessingObjectModel, and Microsoft.ReportViewer.Common.

Change Build Action: Go to the properties of your .rdlc file and set the Build Action to “Content” and Copy To Output Directory to “Copy Always”. This ensures that the report definition is included in the published application.

Use a Different Library: If the above steps don’t work, consider using a different library that supports RDLC report generation in .NET Core, such as ReportViewerCore.NETCore1, which is a community-supported package.

Check for Updates: Keep an eye on official Microsoft documentation or community forums for any updates or patches that might address this issue in the future.