The newest Report Viewer for Visual Studio 2017 has some bugs that prevent us from using it. We’ve downgraded to Microsoft ReportViewer Runtime 2015 for Web Forms (v 12.0.2402.15). However, the report designer in Visual Studio creates new reports in the new “2016” format, and even editing old reports upgrades them to the new format as well. The older Report Viewer doesn’t understand the new format and bombs.
The new report designer is an extension to Visual Studio, “Microsoft Rdlc Report Designer for Visual Studio,” version 14.2. We haven’t found an earlier version of the designer available as an extension.
We’ve tried installing an earlier version of SQL Set Data Tools, but the report designer was still the same. We also haven’t found a separate download for the earlier report designer.
Is there a way to add the older report designer to VS 2017? Or do we have to downgrade to VS 2015?
(A similar problem here: Change RDL version for RDLC Reports in Visual Studio 2017)
The problems in ReportViewer that made it unusable for use were partially resolved in a later version. For example, the CSS in the ReportViewer changed the styles in the rest of the surrounding web page, which was pretty horrible (now fixed). We also saw problems of the viewer's export button drop-down list positioned far from its intended location. We had to fix that with custom JavaScript on the page.
You can include/add any RDLC created on VS 2015 to VS 2017 by click on add existing item and select the RDLC directly from your local location and will run on your VS .Add existing item
From what I can tell, ReportViewer for Visual Studio 2017 which is Version 14, is for compiling in Framework 4.5. My application is depended on 4.0 and if I switch then a bunch of other libraries need to be updated as well. I would rather get the previous version of ReportViewer 12 working, as it was working for my application without issues.
With ReportViewer Designer 14 for VS2017 installed, there is an error in the design of the page, and the application deployed and running on the server does not render the Report.
So, which way to move? Up or back...and how.
Related
I have all MFC stuff installed foe my VS-2019 Porfessional.
I miss the Add New Item "MFC Class From Tyspelib" used in former version to create a simple IDispatch wrapper.
I checked everything and I installed the same stuff like in VS-2017. I see this in my VS-2017 version.
What did I miss?
Many Wizards, including that, have been removed from the VS2019.
The release notes say:
Deprecations - Visual Studio 2019
The following C++ ATL/MFC wizards are no longer available: ATL COM+ 1.0 Component Wizard, ATL Active Server Pages Component Wizard, ATL OLE DB Provider Wizard, ATL Property Page Wizard, ATL OLE DB Consumer Wizard, MFC ODBC Consumer, MFC class from ActiveX control, and MFC class from Type Lib. Sample code for these technologies is archived at Microsoft Docs and the VCSamples GitHub repository.
These changes start from VS2017 ver 15.3.
The change began with this edition, but no consistent behavior was completed.
Add ATL Simple Object in Visual Studio 2017
If you can do what you want with VS2017's latest version 15.9.13, you should work there and port to VS2019.
Furthermore, some work is impossible in 15.9.13. In that case, you need to work with older versions in the following way and port to VS2019
User registration at https://visualstudio.microsoft.com/
Download and install the product version below if you have a MSDN subscription, otherwise uses the Community version.
Visual Studio 2017 (version 15.0) (Note: This should never be updated)
Visual Studio 2015 with Update 3
If this is not possible, you will need to do something manually that Wizard did automatically.
This wizard was removed in VS2017 15.3, but then returned in VS2019 16.8. It also available in VS2022.
https://devblogs.microsoft.com/cppblog/typelib-and-activex-now-supported-in-mfc-wizards/
But Microsoft documentation is still outdated. As for now, VS 2019 does not have "Add class from typelib" option at project context menu. Instead, you need to "Add"->"New Item..." and find "MFC Class from Typelib"
Currently I am using VS2017 Community.
I have downloaded the Windows IoT template for VS2017 community to do UWP programming.
After created the project, when I try to open the XAML file in designer view, I encountered this Message:
visual studio requires a newer version of windows to display this content.
please update to windows 10 Fall Creator update(10.0.16299.0)
So, I downloaded latest Win10 SDK
But Now I have this message:
visual studio requires a newer version of windows to display this content.
please update to UAP (10.0.16299.0)
What I need to do?
Thanks
You need the VS 2017 (15.4 update) or later to get the Windows 10 Fall Creators Update SDK (16299) integration.
If you have the 15.4 update already, then run the Visual Studio Installer, go to the Individual Component tab, and then check the components for 16299. Hit Modify.
See this blog post.
UPDATE: For C#/C++ projects, you set which Windows 10 SDK is used by editing the Project Properties and setting the Target Platform Version to 10.0.16299.0. You can also use the "Retarget solution" or "Retarget project" option.
I use ResXFileCodeGeneratorEx for generating ids. This was working till the time I used Visual Studio 2010 IDE but it is not working for Visual Studio 2017.
Please help for the same.
Extension for Visual Studio 2019 can be found here
Extension for Visual Studio 2017 can be found here
The deleted answer to this question pointed to the location of a newly built ResXFileCodeGeneratorEx but was deleted because it only contained a single link and no context. I'm not the original answerer, but figured that it may still be valuable to have this information:
It seems to have been renamed to ResXCodeFileGeneratorEx, and if you search through the menu in Visual Studio under Tools > Extension and Updates, you need to search for "Extended Strongly Typed Resource Generator".
However, the internal name is still the same, so the Custom Tool action should remain ResXFileCodeGeneratorEx.
I'm not aware whether or not it works on Visual Studio 2019, but since the original source is still around, it oughtn't be too hard to resolve that yourself if you need it.
To install it, simply doubleclick the VSIX file, it will popup with the VS Version Instance Selector, where you can select to which of your VS 2017 instances (pro, community, preview) you want to install the extension to.
Reporting template Component (RDLC) not exists to as New Item in Visual Studio 2017 Enterprise.
How to resolve this?
I have tried by installing SQL Server Data Tools.
Previously it works for me in Visual Studio 2015.
There is a bug in the extension Microsoft Rdlc Report Designer for Visual Studio that the ReportViewer shows up as a non-visual component.
Instead use the NuGet Package Microsoft.ReportingServices.ReportViewerControl.WinForms for each project that will use the ReportViewer. Part of the solution involves removing the ReportViewer from the toolbox after use and restarting Visual Studio before opening the next project/solution.
Please see this answer to a similar question for step by step details.
The RDLC editor for VS2017 is only available as a VSIX installer from the marketplace: Download
I have just used VS2015 to add the new item. All other stuff seems to be fine in VS2017 (bearing in mind that you installed the VSIX extension)
I have a form in which I have placed a MFC DateTimePicker control. I set its format property to Time. Work with my app and everything is fine. But when I close visual studio and open it the next time, format has changed to its default value.
I noticed everything saves just fine, since if I build my solution using devenv.exe at command line the dialogs are displayed correctly. So it seems to me that whenever I open VS, it changes my setting.
How do I avoid this?
EDIT:
Tried VS2010, the problem did not occur there. However the project I'm working on is using VS2003 so the problem still persists.
congrats,
you are the 210th user of visual studio who found that bug but don't worry this will not show you from visual studio 2005 onward.
As per release note by Microsoft this issue came due to the,
behavior occurs because a problem exists in the Visual Studio .NET resource editor for Visual C++ projects.
For more information on this please seen following bug of visual studio resource editor.
FIX: The Format property of the DateTimePicker control reverts to Short Date in Visual Studio .NET 2003