This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
Since the Report Viewer control was first introduced over a decade ago, it has been a key component that allowed developers to surface report content easily in their applications. But although the application development landscape has changed significantly since that time, support for the control is limited to both WinForms and WebForms. With the introduction of new, cross-platform options starting with .NET Core in 2016, we’re focusing our investments on new capabilities in Microsoft Power BI to fill this need for you and your customers moving forward.
As you move beyond the Report Viewer and transition to using the Power BI embedded capabilities, application developers can use a single set of APIs to bring both interactive and paginated reports to their modern applications, far surpassing the capabilities ever offered to date. Power BI also offers support for over 100 first- and third-party data sources, with connectivity for additional data sources added on a monthly basis to the Power BI service.
As paginated reports are the same reports you use in SQL Server Reporting Services (SSRS), it’s easy to migrate them to the Power BI service. In addition to published migration guidance for you, we’ve built a migration tool that’s hosted in GitHub you can download and use to easily migrate your files to the Power BI service. Check out this video on YouTube from Patrick LeBlanc that walks through the tool and migration process.
We have also made several investments in Power BI embedded to help developers adopt and use both paginated and Power BI reports in the Power BI service for their needs.
We want to emphasize that we’ll continue to support the current Report Viewer control, and any applications dependent on it, with critical bug fixes and security issues as per the Microsoft Modern Support Lifecycle. Products governed by the Modern Lifecycle Policy will provide a minimum of 12 months' notification prior to ending support if no successor product or service is offered. For reference, read more about the Modern Lifecycle Support Policy.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.