What's the future of RDLC ("client-side SSRS", aka "ReportViewer")?
This is the information I could gather so far: Getting an RDLC renderer for .NET 5+ is currently the fourth highest-voted feature on the SQL Server user wishlist. Unfortunately, there are currently no plans to do that (see the comments here). There are some enthusiast ports/recompilations floating around on github and nuget, but they are not official. The SQL Server Reporting Services Team Blog is dead, the last entry is from 2018. There's a third-party company providing an RDLC renderer, but Microsoft acquired them in 2018. Nothing has been heard since. There is currently no ReportViewer designer for Visual Studio 2022. Getting one is currently the fourth highest-voted feature on the Visual Studio 2022 wishlist. From a business perspective, I can totally understand that Microsoft is not giving this highly-loved feature the resources it needs. After all, they are basically giving away a great reporting engine for free, undermining their own SQL Server and Power BI sales. And they are not even hiding the fact that they'd rather have people purchase Power BI subscriptions, which is perfectly fine. They are a company, not a charity. Unfortunately, adding a dependency to a third-party cloud service is a no-go for many software development scenarios. Thus, I would like to start a discussion on the following points: It seems to me that MS no longer wants people to use their RLDC reporting engine in new projects. Is this observation correct? If you have a large repository of RDLC reports in your project, what are your migration plans? Are there drop-in replacements from third parties? Would Microsoft consider open-sourcing the RLDC engine, so that the community can "keep the product alive" for legacy scenarios and prevent this from being a blocker in .NET 5+ migrations? Best regards HeinziReview GitHub Pull Requests in Visual Studio 2022
Used the GitHub Extension for Visual Studio 2019 to review Pull Requests. Now it looks like that extension is included in VS 2022. However, when going to 'Git/GitHub/View Pull Requests' it redirects me to the browser. Do you know how you can review pull requests in VS 2022 ?
UWP SDK version issue (Your project does not reference "UAP,Version)
In UWP apps, does anyone know how to get rid of the following errors permanently? This happens when I switch between GIT branches where the source code is targeted to different Windows SDK versions. Your project does not reference "UAP,Version=v10.0.18362" framework. Add a reference to "UAP,Version=v10.0.18362" in the "frameworks" section of your project.json and then re-run NuGet restore. BoardPACWinAppBO NOTE: By removing bin and obj folders + cleaning the project + close and reopening VS randomly fix this issue. But this is not convenient. I'm using the latest version of VS 2022.
Unable to connect to TFS from Visual Studio 2017, getting TF31002: Unable to connect
I wonder if anyone could assist me with that. I am unable to connect to TFS from Visual Studio 2017, I get the error specified below "TF31002: Unable to connect to this Team Foundation Server: http://tfs.**************** Team Foundation Server Url: http://tfs.*************************** Possible reasons for failure include: The name, port number, or protocol for the Team Foundation Server is incorrect. The Team Foundation Server is offline. The password has expired or is incorrect. Technical information (for administrator): The remote server returned an error: (404) Not Found." Please note. I AM able to connect to this TFS server via the browser; thus, there is no issue with my credentials. I did look all over the internet for the solution, got the latest update for the VS2017, removed all stored credentials multiple times, did everything possible that I could find I vaguely remember that I dealt with the similar issue years ago but back then there was some sort of a hotfix issues by Microsoft, but now I am unable to find this hotfix Maybe anyone could suggest where I could locate this hotfix Thank you everyone in advance
Visual Studio and problems with custom controls
Hello @all, to first: sorry for my bad english ! And now to my problem: I have for some time with VisualStudio 2019 the following problem: In a project have custom controls. For example, a custom button that inherited from System.Windows.Forms. Public Class clsButton Inherits System.Windows.Controls.Button .... or Public Class clsMasterForm Inherits System.Windows.Forms.Form ... Everything works, the "new" button works great, the new properties are active and can be used without any problems. Suddenly, from one close of the project to the next open, VS2019 can't find the new controls. Also from the toolbox (for WinForms) these controls have disappeared. If I now exclude these controls from the project, and after a VS2019 restart, add them back to the project, everything works again. The controls are in the toolbox until the next time. Without that I can see any pattern/regularity. (Environment: W10 current patch level, VS2019 current patch level, 64 GB memory, in an ADS). Do any of you know what is happening here ? As I said it is rare and sporadic. I also had this under VS2010 (on W7 PC). Oh well, with VS2022 I could not test yet if it occurs there too. Thanks a lot SH
Visual Studio 2017 can't apply a license key
Driving me crazy. I've installed 3 different versions of VS2017 Professional from MSDN - community, 15 & 15.9 and I can't apply a license key. After installing, I launch VS and I get this on a modal screen: I have a MSDN y and need to use it. I can't clear this modal and input the key. If I "check for an updated license", I get this: As far as I know network/proxy settings are good. The thing is, I expected to be able to enter the key from the Help menu, so what I'm seeing isn't making any sense. I uninstalled the the Community version before installing professional. I wondering if I'm dealing with an artefact of that install?
