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.
Related
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!
I am trying to check for my build definition under team explorer build option. I am not getting any options. It is blank.
Any idea how I can get my Build definitions.
I am working in VS 2013
If you are using the same user account on another system in VS2013, this issue seems only related to your local VS 2013.
Try to close the VS, clear both TFS and VS cache, then reopen it.
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
I'm using VS2013 to development and maintain a couple of SP2013 projects. However, I think somehow I managed to corrupt one of the projects.
When I go to the "Package.package" designer, I see only (mapped SP) folders in there (it should also include the feature of the project). When I double-click, thus remove, one of these and try to re-add it, I get the following error msg
http://i.imgur.com/nC8RdOq.png
Same goes when I try to add the feature to the package
What's also strange is that if I go into the Feature designer, I cannot add any items. VS gives a similar type of err msg:
http://i.imgur.com/wqC5nAg.png
Few more details:
the projects were SP2010 projects and I successfully converted these to SP2013 some time ago.
using Visual Studio Premium 2013, Update 3, running as an administrator.
tried removing the feature and re-adding it; did not help.
tried running VS in safe mode, resetting the user settings via the command line devenv; did not help.
tried closing the designer, VS, rebooting; did not help.
i am able to add/remove items to the package/feature in other projects so I suspect it not to be a VS2013 bug
I just had the same Issue when adding items to feature or including features in package. I solved it by updating Visual Studio 2013 Developer Tools.
After updating to: Microsoft Office Developer Tools for Visual Studio 2013 - August 2015 update
We have recently upgraded to windows 7 and have noticed that there are compatibility issues with my previous version of MS visual Studio 2005.
From taking a look around the web I believe that this issue is due to SP1 for Windows 7. My organisation will not get rid of SP1 just for one or two developers so I need to figure out a work around.
This is the issue...
I have an old MS visual studio website that has a report located on the home. This report was created in MS VS 2005.
Other versions of Visual Studio in have are 2010 and 2012. I have tried to convert the 2005 report into 2010 and this does state that it has been converted but I still cant open or do anything with the report. My 2005 web site is too large to convert or move into 2010 and we can still maintain this 2005 site by opening this up in 2010. It just seems to be a problem with the 2005 report.
I'm running out of options to make a simple change to a report. Anyone else got any ideas? I have even tried to create this report in 2010 and then add this to my 2005 site but this doesn't work.
Regards
Betty.
You say a report and then say that it is a whole site? Why not run a second site in tandom? Make a whole new site and name it differently like
http:// (servername)/Reports2012
Then put reports there. You cannot open a converted report in a site that is for a prior version, you can view it in Microsoft Business Intelligence Studio, BIDS, which is an add on to Visual Studio. If you can upgrade but cannot view it there, there is something wrong with the language file potentially. I would then make a copy of it in the old 2005 BIDS, then take that copy and see if you can upgrade that and if it will work. If that STILL does not work you could make a test report in BIDS 2010(SQL 2012 works on VS 2010, yes weird but true) to assure you can create reports there. Many times people try to open SQL Server 2012 Reports on VS 2012 and it won't work. You need 2010 add on you can find it under All Programs>MS SQL Server 2012>SQL Server Data Tools(They made the naming very confusing as it opens up and display BIDS, but calls itself 'Data Tools' under the programs). Every other version of SSRS lines up with that year of SQL Server to that year of VS. Not 2012.
If the report upgrade still does not work, yet you can create a run a new report fine; I would suggest potentially opening up the file dircectly. Your projects in a Reports solution generally have a file '(something).rdl' that RDL is the actual file and is just XML markup of the language. This is a last resort as you are essentially trying to do manually what the upgrade is failing to do in the xml. You merely copy a working report, and then paste the parts of the old report into their correct sections. Ensure the XML is valid as well.
If you cannot manage that to work you will need to recreate the report from scratch.