I have a project in Visual Studio 2017 with .NET Framework 4. For reports I use the RDLC designer, but I have a problem. The designer creates the reports using RDL 2016 and I need you to use the 2010 definition.
Can I configure this?
I need it since the program has to be compatible with Windows XP and there is no ReportViewer Runtime that supports RDL 2016 for Windows XP.
I had the same problem, but if a did a new report it was all right, the new report was created and saved with the old schema:
xmlns="http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition". (report viewed with a text editor)
When I added a parameters and re-saved, VS turned the schema in
new schema:
xmlns="http://schemas.microsoft.com/sqlserver/reporting/2016/01/reportdefinition"
But I found a solution that work also with Windows XP:
I install all necessary to manipulate the report with VS 2017 (in Visual studio 2017 are all external plug-in), then change the reference of my project e take 2 new referenze to this DLL:
1)
..\project\packages\Microsoft.ReportingServices.ReportViewerControl.Winforms.140.340.80\lib\net40\Microsoft.ReportViewer.WinForms.dll
2)
..\project\packages\Microsoft.ReportingServices.ReportViewerControl.Winforms.140.340.80\lib\net40\Microsoft.ReportViewer.Common.dll
After that all work.
This new version of DLL handle both "old schema" and "new schema"
You can check ReportViewer version and installed in your Visual Studio 2017 using PM>
(Before doing this you have to delete previous Report viewer references )
https://www.nuget.org/packages/Microsoft.ReportingServices.ReportViewerControl.Winforms/140.1.291.2731477-rc
This package Manager work for me.
PM>Install-Package Microsoft.ReportingServices.ReportViewerControl.Winforms -Version 140.1.291.2731477-rc
Reporting solutions in VS have always been tied to the version of SSDT that is current at the time of release. e.g. VS 2015 only supported the Sql Server 2016 report schema.
I think the answer is that you might be able to do something to change the schema it uses by editing the XML directly, as suggested by Ricky A, but for proper, designer support this isn't going to work.
Article from Microsoft on schema versions supported here doesn't mention anything other than schema v2016 support in VS 2017: https://learn.microsoft.com/en-us/sql/reporting-services/plan-for-report-design-and-report-deployment-reporting-services
I am fairly sure that your VS licence will cover old versions, and different versions live happily side by side, so install whichever other version you need for the reporting project you are editing (along with the correct version of SSDT/BIDS etc).
Although too late, but I have fixed this issue by installing this package :
Microsoft RDLC Report Designer
Install-Package Microsoft.ReportingServices.ReportViewerControl.Winforms -Version 140.1.291.2731477-rc this saved my ass
Related
My Visual Studio version is 2019.
My ssrs reporting solution properties are set to SQL Server 2008R2, 2012 or 2014.
Visual Studio still builds the 2016 Version of my SSRS rdl Reports.
This leads to problems in deployment of the reports.
I know that I can fix the issues with the following post:
stackoverflow...
But afert every update of a report, the version jumps back to 2016.
I read that the problem is in the ServerTargetVersion of the SSDT but I cant find out how and where to set the the right build version.
I found this article on setting the Default Deployment Server version.
But in VS2019 I do not see the the option for "Alalyses Service Designer".
Does anyone have walkthrough?
How can I change the ServerTargetVersion?
I think quickest way is to go to the Solution Explorer window, right click on your PROJECT and go to Properties. It will open the deployment window and the very last option should be TargetServerVersion that will allow you to change the Target version.
I've inherited an old project which uses Devexpress 8.2.4 - so i went and installed an appropriate DXperience Subscription v8.2.4. Now, when I try to open the designer through Visual Studio 2019, I get a:
"This method explicitly uses CM policy, which has been obsoleted by the .NET Framework. In order to enable CAS policy for compatibility reasons, please use the NetFx40/LegacySecurtyPolicy configuration switch. Please see http://go.microsoft.com/fwlink/?LinkID=155570 for more information."
Then I tried to open the project in VS 2010, and upon attempt at opening the designer, same CAS policy error happens.
After editing the VS2010 DevEnv configuration file (and respective config file for VS 2019), as Thomas suggested in his answer here, my Visual Studio 2019 just started crashing during start, and my Visual Studio 2010 successfully started but it then crashed upon trying to select the designer object.
Yes, I'm trying to get this designer for Devexpress 8.2 to run in either IDE - I just need to get it to work so I can hopefully add a QR Code(is this even possible in v8.2.4???).
I just don't know how to access designer to actually graphically update the report. I did some Devexpress projects myself but using v19 and newer, but I'm having trouble now, opening this designer for old Devexpress 8.21.
Any help would be appreciated as this HAS to be done by tomorrow.
Also, if v8.2.4 doesn't support QR Code (an XRBarCode object), what would be an alternative for adding that QR Code functionality? Would I have to upgrade to newer versions - would that break something?
Thanks!
enter image description hereTrying to use SSRS in Visual Studio 2019 Community.
I am able to create a new "Report Server Project" Project in VS. However, when I try to "Add New Item" in the Project, I get the Error message:
Member not found. (Exception from HRESULT: 0x80020003 (DISP_E_MEMBERNOTFOUND))
I did install Data Server and Processing when downloading VS and also added the Extensions:
Microsoft Analysis Services Projects
Microsoft Reporting Services Projects
SQL Server Integration Services Projects
Which all seem to be active. I should also note that the "Add New Report" Wizard does work, it's the "Add New Item" that is throwing the error.
Any advice on how to correct?
Thanks to anyone helping!
I got this error and i solved it by adding the references for report viewer libraries in my current project, so basically when you create a new report project those dll are not included by default and visual studio can't find them.. Do a right click on your project and select Manage Nuget packages and install those two packages:
Corrected.Microsoft.ReportingServices.ReportViewerControl.Winforms (Current version = 150.1358.0)
Microsoft.ReportingServices.ReportViewerControl.Webforms (Current version = 150.1427.0)
Note: i am using Visual Studio Enterprise 2019 but i think the solution will work for 2017 too
So I hit the exact same error and got blocked. After googling for some time, seems MS has accepted that it's a bug, and they have this solution bundled as part of the new Preview ( Visual Studio 2019 version 16.9 Preview 3) and yes this is pretty new, like was release 3 days back when I'm writing this. Once I install and test I'll comment on this thread, but by the release notes (https://learn.microsoft.com/en-us/visualstudio/releases/2019/release-notes-preview#16.9.0.pre.3.0) looks like they've fixed this. I can't wait for the 16.9 to be release (16.9 is still not out), hence installing Preview to continue.
Update: So I installed Udpdate, and then i had to install the reporting service extension again(else it was saying reporting service project to be non-compatible), but post that I'm now able to add a report.
As of 3/8/2021 - I was running Visual Studio Professional 16.8.6 and was experiencing this issue. I upgraded to 16.9.0 (release data of 3/2/2021). Unlike ssethi11, it did not require the reinstallation of the SSRS extension.
The Official 16.9.1 is released.
Update visual studio and it should work now
I have some issues with my reports since I have updated them to VS2010 format.
Even though I have modified references to from v9 to 10 for Microsoft.ReportViwer.Common and Microsoft.ReportViewer.WinForms as well, when I try to type code. in a field, what is after "Code." is always underlined with red and I get #ERROR instead of the value I want when I print the report. I know it is case sensitive and I double checked the spelling multiple times.
Moreover, I don't know why but I have errors with the Fields! syntax; I seem to have to use the Fields().value to get them to work (at the places I don't need to call custom code too)
These reports worked well before conversion (over 20 reports converted this way) but do not now. Seems like custom functions are not "seen" by the report designer. I tryed to make them public, shared; all I had is the same stupid #ERROR display.
I want them to work in VS2010 to avoid always having to modify them in VS2008 and then go back in VS2010
It's a winform application with framework 3.5
Any idea of what could cause that and what is the remedy?
Many thanks
Nico
There are a couple of ways to use custom code in SSRS. Firstly you can enter VB directly into the window under
Report -- >Report Properties --> Code
Another way is to write a custom DLL (which can be done in any .NET language of course), which then needs to be copied to both your dev machine and the production report server.
You then need to create references to that assembly in the project using:
Report --> Report Properties --> References (I assume you know this).
If you are not using your own custom assembly, and just using a reference to one on your machine then there could be some confusion on the server as to where to find the dll's. You may need to copy DLL's to the folder as indicated in the KB link below:
http://support.microsoft.com/kb/920769
When you drag a field onto a tablix or textbox, and have a look at the value expression, does it use the Fields!Fieldname.Value syntax? That syntax is natural to SSRS so it sounds like something seriously broken in your visual studio 2010 there if that is not working. I take it you installed visual studio 2010 to create web applications. What you haven't explained is which version of BIDS or SSDT you are using. If you are developing reports for SSRS 2008 R2 or earlier, then these are not compatible with visual studio 2010. There's no compromise there.
If you are developing for SSRS 2012, then you are using either SSDT by itself (which installs a shell version of visual studio 2010) OR if you already have visual studio 2010 then you need to install service pack 1 for VS2010 and then install SSDT from the SQL Server 2012 disc.
http://msdn.microsoft.com/en-us/library/hh500335(v=vs.103).aspx
I am using VS2010, working on a WinForms application that uses the ReportViewer control to run a local report. However, .rdl and .rdlc reports written using Version 3.0 of the language can't be run by this control. This is a shame, because there are some features in 3.0 that would be darned handy.
I have read here that a new preview version of the control is out that would support 3.0. It is associated with the VS2012 preview.
Does anybody know:
Whether a download for just the control exists, and
Whether VS2010 can build a project with this control?
(I know the VS2010 report builder doesn't work with v3.0, but I can live without that if I have runtime viewer support for it.)
There is an update to the Beta runtime posted above. Please see my post http://blogs.msdn.com/b/arvindsh/archive/2012/12/11/microsoft-report-viewer-2012-update-a-gotcha-to-be-aware-of.aspx for details.
This could be what you are looking for: MICROSOFT REPORT VIEWER 2012 RUNTIME