Update: Microsoft released a document on Apdescribing how to configure and use the reporting tool in Visual Studio 2017. Now you can position the reportViewer by actually interacting with the panel. Set the reportViewer's Dock property to Fill.In the Properties panel select the ReportViewer in the controls list dropdown.Return to the form's designer, you should see the reportViewer on the panel In the form's file, add the Reportviewer control to the panel. After adding the reportviewer to the WinForm.Microsoft Azure Feedback page - Restore Designtime features of the WinForms ReportViewer Control Please consider voting on it to get Microsoft's attention. I've created a feedback request at the suggestion of Microsoft SQL BI support. While now visible, the designer treats the control as if it didn't exist. While you still cannot interact with the control directly, these additional steps give a workaround so the control can be sized on the form. This is the group responsible for the control. This is working as designed according to Microsoft SQL BI support. The control shows up below the form as a non-visual component.
But once dropped on the form it doesn't display. I was working with V150.1358.0.įollowing the directions in this answer gets the control in the designer's toolbox. Remember to restart Visual Studio after changing the toolbox entry.Ī newer version of the ReportViewer control has been released, probably coinciding with Visual Studio 2019. It may be easier to manually delete references to post 150.900 versions of ReportViewer and readd them than it is to fix them. Use the drop down box to select the older version. It works similarly to the previous versions.
You can roll back to 150.900.148 in the Nuget solution package manager. Removing the latest version and rolling back to 150.900.148.0 seems to work on multiple computers I'm using with VS2017 and VS2019. This includes being able to resize and modify the ReportViewer Tasks on the control itself. My short testing shows that it works again in the forms designer where 150.1357.0 and 150.1358.0 did not.
Microsoft has released a new version of the control 150.1400.0 in their Nuget library.
0 kommentar(er)
