Progress® Telerik® Reporting Feedback Portal
Back to Feed
Request a Feature Report a Bug
Unplanned
Last Updated: 18 Nov 2025 23:21 by Mark
Mark
Created on: 18 Jan 2024 12:12
Category: Reporting
Type: Bug Report
2
Telerik.Reporting NuGet package brings unnecessary assemblies when used in .NET Framework projects
The Telerik.Reporting NuGet package brings unnecessary assemblies when used in .NET Framework projects due to the change to the nuspec in the Telerik Reporting - Progress® Telerik® Reporting R2 2022 SP1 (16.1.22.622) release.
5 comments
Mark
Posted on: 18 Nov 2025 23:21
Apparently, without a .NET472 and a .NET48 "group targetFramework", NuGet will choose .NET Standard 2.0 as it is considered a closer match.  (.NET472 for projects >= 4.7.2 and < 4.8)
Mark
Posted on: 18 Nov 2025 23:02

I just downloaded the latest version and seem to have the same basic issue.

My project targets .NET Framework 4.8, and instead of pulling the .NET Framework 4.6.2 files, it pulls the .NET Standard 2.0 files which includes many transitive dependencies that would be satified by assemblies within the .NET Framework.

It seems that the correct behaviour would be to use the .NET Framework 4.6.2 files.  Microsoft Copilot said it does this because .NET Standard 2.0 is considered newer than .NET Framework 4.6.2

Can you confirm that I should be using the .NET Framework 4.6.2 files?

I am assuming that there is no advantage to using the .NET Standard 2.0 files.

Mark
Posted on: 08 Aug 2024 17:14

I wondered what was happening with this because in my original support ticket (1637210) you had said that you "plan to include it with the .NET Framework target version update."

It seems like that was completed, but this appears to remain open.

I will continue to use my modified NuGet package for the time being, and will continue to watch for updates.

Thank you for this update.

ADMIN
Dimitar
Posted on: 08 Aug 2024 10:45

Hello Mark,

The Reporting team is aware of the issue, however, we haven't yet planned a release date for the fix. With that being said, I added the issue to the discussion for the next sprint so that it can be considered for one of the releases in the coming months.

We will update the status of the item as soon as the fix is scheduled for release. Please stay tuned.

Regards,
Dimitar
Progress Telerik

Stay tuned by visiting our roadmap and feedback portal pages, enjoy a smooth take-off with our Getting Started resources, or visit the free self-paced technical training at https://learn.telerik.com/.
Mark
Posted on: 01 Aug 2024 16:40
Has this been addressed, or is this still planned for a future release?
Create an account Log In
View
Type
Status
Category