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
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 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
Someone asked about getting the WinRT XAML Toolkit controls to show up in Visual Studio Toolbox. I can see that they do show up when I look at the sample project that uses the source code version of the WinRT XAML Toolkit and I can find them in Blend in an app project that uses NuGet-packaged version of the Toolkit - just by searching for the controls by name, but they don't automatically show up in VS Toolbox somehow. I saw in Tim Heuer's article that you can make them show up in the Toolbox if you do a VSIX deployment, but the Toolkit doesn't support that option right now.
Is it possible to get it to work with NuGet or are using the source code or building Extension SDK the only options?
I think the possible way to do this would be to allow package manager to take additional parameters which would then add them to toolbox
If the default project templates reset the toolbox items each time, this might work great otherwise we will see versioning related issues in no time.
I am using Sandcastle Help file builder (1.9.4.0), Sandcastle (2.7.0.0) and .NET Framework 4.0 assemblies to generate the Class reference for Visual Studio.
I have used Framework version is .NET 4.0.30319 and Help File Format is MSHelpViewer and Presentation Style is vs2005 in Sandcastle Help file builder. It is working fine in VS 2010 (Help viewer 1.1). It shows Script error in VS 2012 (Help Viewer 2.0).
Shall I need to change any settings to solve this issue?
I randomly get this error. There's a lot of stuff online that requires you to mess with the registry and such. A much easier solution I found somewhere is to go to select Manage Content icon, and then make some change to the Help contents that you have selected, for example Add in some help topic that is currently not in, or Remove some topic. Then click Update, and its usually fine after that!
I’m using visual studio 2008 and moles version 0.93. Everything works well except when I try to debug any test that uses a Moled type. The test skips all my breakpoints. And I get the following message in the output window:
Unable to attach. Check for one of the following.
The application you are trying to debug uses a version of the Microsoft .NET Framework that is not supported by the debugger.
The debugger has made an incorrect assumption about the Microsoft .NET Framework version your application is going to use.
The Microsoft .NET Framework version specified by you for debugging is incorrect
Please see the Visual Studio .NET debugger documentation for correctly specifying the Microsoft .NET Framework version your application is going to use for debugging.
If I try debbuger.Break () I get a message: "No symbols are loaded for any call stack frame. The source code cannot be displayed."
I’m in a crunch right now chasing an issue with one our main components and it has been a pain (like I need novocaine) trying to figure anything out without being able to step through the code.
I want to take advantage of mole's "smooth debugging experience". However, I can't seem to get the debugger to attach at all.
Thanks,
Bzz
See the solution to this issue here:
http://social.msdn.microsoft.com/Forums/en/pex/thread/91c08bf4-3260-458c-a221-91f030a75499
I had this problem when I moved a project from Visual Studio 2010 to Visual Studio 2008. Here's what I did to fix it.
Close Visual Studio. Navigate to the Debug/bin location. Delete the following files:
*.vshost.exe
*.vshost.exe.config
*.vshost.exe.manifest
Open the solution. Goto the project Settings. Under the Application Target Framework, select a framework lower than the one you are working with (you'll set it back later). Visual Studio will close and re-open your project automatically. Then set the Target Framework back to the original version you were working with. Rebuild all, and debugging will work properly.