Report must be 'interpreted' not 'compiled' after updating to 2019.2.1
Report must be 'interpreted' not 'compiled' after updating to 2019.2.1
Using reports.web with an ASP MVC Core 2.2 application. After I updated the package to 2019.2.1 when previewing a report stimulsoft warns that the report must be interpreted and can't be compiled. This happens even with a basic report that has a single data item on it. From some searching it appears that having a report be interpreted is not ideal in that the expressions do not function correctly?
-
- Posts: 6266
- Joined: Tue Mar 20, 2018 5:34 am
Re: Report must be 'interpreted' not 'compiled' after updating to 2019.2.1
Hello,
In the NET Core version, the Compilation is not supported, only Interpretation mode is available.
Thank you.
In the NET Core version, the Compilation is not supported, only Interpretation mode is available.
Thank you.
-
- Posts: 21
- Joined: Wed Dec 02, 2020 9:21 pm
Re: Report must be 'interpreted' not 'compiled' after updating to 2019.2.1
Is Compilation mode still not supported in NET Core versions?
Re: Report must be 'interpreted' not 'compiled' after updating to 2019.2.1
Hello,
For the version 2021.1, when using the .NET Core framework, we have added support for compilation for reports. Now you can use all the reporting tool features like compilation at runtime, functions, publishing reports as classes. Compilation for .NET Core 3.1 is only available on Windows systems, and .NET 5.0 is available on all supported systems.
Thank you.
For the version 2021.1, when using the .NET Core framework, we have added support for compilation for reports. Now you can use all the reporting tool features like compilation at runtime, functions, publishing reports as classes. Compilation for .NET Core 3.1 is only available on Windows systems, and .NET 5.0 is available on all supported systems.
Thank you.