Completed
Last Updated: 20 Oct 2020 08:13 by Theo
Release R3 2020 SP1
Theo
Created on: 11 Jun 2020 13:37
Category: UI for WinForms
Type: Bug Report
1
RadGridView: GridViewSpreadExport.FileExportMode is not respected when exporting to a stream

If you have two RadGridView controls and you want to export both of the grids to a common file on two different sheets, it is suitable to use FileExportMode.NewSheetInExistingFile. However, when using the export overload to a stream doesn't respect the ExportMode.

Workaround: use exporting to a file:

            string exportFile = @"..\..\exportedData.xlsx";
            GridViewSpreadStreamExport spreadStreamExport = new GridViewSpreadStreamExport(this.radGridView1);
            spreadStreamExport.FileExportMode = FileExportMode.NewSheetInExistingFile;
            spreadStreamExport.ExportVisualSettings = false;
            spreadStreamExport.RunExport(exportFile, new SpreadStreamExportRenderer());

 

5 comments
Theo
Posted on: 20 Oct 2020 08:13

Thank you for getting back to me.

We are using a combination of versions which is the issue. Our solution stack consists of a shared common library of code, covering WinForms designer forms as well as not UI related shared functionality.

The issue is that if we upgrade the common library to the latest version, then all of our other solutions that depend on the common library also needs to update. This is due to our experience that mixing versions of the Telerik WinForms assemblies does not work well. This is also the reason that I am getting so much push back from my manager and director for my request to upgrade to the latest versions of Telerik. It has a huge impact on our eco system.

They are scared that upgrading will have unintended bugs and issues causing a lot of resources to be redirected in addressing it. To their point, if there are no breaking changes and there are no issues in the latest version, why are we upgrading to a latest version to resolve bugs in the current version we are using.

We currently run

- older projects - 2017.2.613.40, 2018.2.515.40

- newer projects - 2019.1.117.40

If we do upgrade, we would like to align all solutions and projects to a single unified version

Thank you

ADMIN
Nadya
Posted on: 20 Oct 2020 08:01

Hello, Theo,

Yes, you are correct. The R3 2020 SP1 release version includes everything of the R3 2020 version and before that. By default, upgrading to the latest version gives you the opportunity to benefit from the latest improvements and new controls.

There are no breaking changes in R3 2020 SP1. However, I am not familiar which is the exact version that you use in your application. Here you can find our release history and see what's new from your current version till now. 

I hope this information helps.

Regards,
Nadya
Progress Telerik

Five days of Blazor, Angular, React, and Xamarin experts live-coding on twitch.tv/CodeItLive, special prizes, and more, for FREE?! Register now for DevReach 2.0(20).

Theo
Posted on: 19 Oct 2020 15:46

Am I correct in assuming that SP1 includes everything of 2020.3 and we only need to upgrade to SP1 to utilise the latest version.

Are there any breaking changes that we need to be aware about?

Thank you

 

ADMIN
Nadya
Posted on: 19 Oct 2020 15:37

Hello, Theo,

I am happy to inform you that the R3 2020 SP1 release is scheduled for this week. Stay tuned!

Regards,
Nadya
Progress Telerik

Five days of Blazor, Angular, React, and Xamarin experts live-coding on twitch.tv/CodeItLive, special prizes, and more, for FREE?! Register now for DevReach 2.0(20).

Theo
Posted on: 19 Oct 2020 13:54

Thank you for the update.

When is SP1 release scheduled as we are investigating updating our current version from 2018/2019 to latest release and getting all products and shared libraries to use the same version of Telerik

Thank you