Unplanned
Last Updated: 19 Feb 2025 09:40 by ADMIN
Scheduled for 2025 Q1
Nikhil
Created on: 30 Oct 2023 10:05
Type: Feature Request
14
Migrate MsSqlServerStorage to use the new Microsoft.Data.SqlClient
The current version(R3 2023) of the MsSqlServerStorage implementation uses the old System.Data.SqlClient data provider which forces to use a different connection string from my application because keywords such as 'authentication' are not supported by the older provider.
6 comments
ADMIN
Milen | Product Manager @DX
Posted on: 19 Feb 2025 09:40

Hi all,

In the 2025 Q1 release we implemented the Microsoft.Data.SqlClient usage for the .NET runtime. Please give it a try!

The implementation targeting .NET Framework, however, encountered difficulties related to code security attributes. The implementation of the Microsoft.Data.SqlClient usage would lead to breaking change. Here is the detailed explanation:

As the Telerik Reporting Engine is widely used in a variety of .NET Framework scenarios, we have a few clients that run their code in partial trust isolation. Before the level 2 code transparency model that was introduced in .NET Framework 4.0, setting AllowPartiallyTrustedCallers (APTCA) seamlessly enabled these scenarios.

After the introduction of L2, we kept the attribute set to avoid breaking changes, but we had to comply with the enforced transparency checks that come with the attribute usage (security critical code cannot be directly called within transparent code assembly). In comparison the code security model is completely revamped in .NET and APTCA is only present for compatibility reasons, without enforcing any checks.
Since we had some hurdles with other assemblies that employ security critical code, we are now researching the best integration option. We aim at both moving technology forward for the .NET Framework offering and limit the impact on existing partial trust users.

On top of that, adopting Microsoft.Data.SqlClient in .NET Framework projects might produce build- and runtime- errors. Since Microsoft.Data.SqlClient is not part of the .NET Framework, all the projects that reference Telerik.Reporting through assembly references will have to add a reference to Microsoft.Data.SqlClient NuGet package manually, while in .NET this dependency gets resolved automatically, as NuGet refs are the standard there.

I hope the update is valuable to you. If there should be a call to action, it would be: Migrate to .NET, if you have not already! And, use NuGet references!

Any feedback or comments are welcome. 

Regards,
Milen | Product Manager @DX
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/.
James Glinsek
Posted on: 17 Oct 2024 15:04
Yeah, we need this too.
ADMIN
Todor
Posted on: 03 Sep 2024 09:50

Hello All,

We have discussed the requirement within the team and intend to release it in the first half of 2025.

The feature request will be properly tagged when this becomes official.

Regards,
Todor
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/.
William
Posted on: 27 Aug 2024 17:07
Following - need this!
Kevin S
Posted on: 18 Jul 2024 07:39
It is also extremely important for us. Thank you.
Steve
Posted on: 25 Apr 2024 14:15
This is extremely important to us for security reasons.