If you try and open a solution with a form with ReportViewer without restarting you will see errors indicating that the “ The variable 'reportViewer1' is either undeclared or was never assigned.“. Remember to restart Visual Studio any time you need to open a project with ReportViewer so that the DLL is loaded from the correct location. You may save the project and are good to go. Once completed, delete the ReportViewer tool from the tool box. ReportViewer is now located in the ToolBox. Scroll to the right and you will see the version 14.0.0.0 associated to it. You should see ReportViewer checked in the dialog. Then double-click on lib and again on net40.įinally, double click on the file The version number will probably change in the future. In our example we can paste in the packages folder as shown in the text of Package Manager Console.Ĭ:\Users\jdoe\Documents\Projects\_Test\ReportViewerTest\WindowsFormsApp1\packages We need to browse to the proper DLL that is located in the solutions Packages folder, so hit the browse button. Right-click in the toolbox and use Choose Items. Now we can temporarily add the ReportViewer tool to the tool box. You should see text describing the installation of the package. Open the NuGet Package Manager Console ( Tools/NuGet Package Manager/Package Manager Console)Īt the PM> prompt enter this command, case matters.This isĪ crucial step, errors will occur if VS is not restarted when If you have the Microsoft Rdlc Report Designer for Visual Studio extension installed, uninstall it.Ĭlose your solution and restart Visual Studio. You need this to actually edit the reports. You will have to have a project with a form open to do this.Įdited - It looks like the current version of the RDLC Report Designer extension no longer interferes.If you have ReportViewer in the Toolbox, remove it.The following steps need to be followed for each project that requires ReportViewer. Microsoft Support had told me this is a bug, but as of Apit is "working as designed". Installing the extension Microsoft Rdlc Report Designer for Visual Studio and then adding that to the ToolBox results in a non-visual component that appears below the form. Visual Studio 2017 does not have the ReportViewer tool installed by default in the ToolBox.
#Visual studio 2017 application wizard how to#
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)
