Visual Studio 2022 Breaking Changes: What You Need to Know

When upgrading from Visual Studio 2019 to Visual Studio 2022, developers of .NET Core applications with SQL connections may encounter some breaking changes. One such change is the removal of the watermark group of settings from PdfExportOptions.PdfReExclusiveOptions class. To set a watermark, users should now use the Watermark property in the PdfExportOptions class instead.

Another significant change is the migration of the CommonDbConnectionAdapter class from the DataProviders assembly to the ActiveReports assembly. Similarly, the DataProvidersFactory class has been moved from the DataProviders assembly to the namespace in the assembly. This change affects users who are developing .NET Core applications with SQL connections and requires no special migration steps.

The default data provider for MSSQL has also changed, and NET Standard assemblies versions of AR.Core have been updated. Additionally, the TypeConverters related to section reports have been hidden, which may cause issues when designing section reports.

GrapeCity and Gcef in all ActiveReports packages names have been changed to MESCIUS. If users encounter problems using these TypeConverters in their project, they can contact the Support Team for assistance.

The Calendar sample is undergoing significant changes related to the public API of the sample controls. As a result, it is recommended that users postpone upgrading to Visual Studio 2022 and contact the Support Team if backward compatibility with old AR versions is required.

Lastly, RDL reports created in previous versions of ActiveReports are automatically converted to RDLX format when opened in the Designer. The legacy RDL report type has been removed, and RDL Multi-Section was renamed to RDLX. This change affects users who were previously using the WinForms and Web Designers.

In conclusion, while there are some breaking changes in Visual Studio 2022, they are mostly minor and do not require significant migration steps. Users can easily update their packages using the ActiveReports File Converter or perform the update manually by following the reference migration steps provided by Microsoft.

Visual studio 2022 breaking changes