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 https://feedback.azure.com/d365community/idea/ec1af842-4d25-ec11-b6e6-000d3a4f0da0. Unfortunately, there are currently no plans to do that (see https://devblogs.microsoft.com/dotnet/announcing-net-5-0-preview-6/). There are some enthusiast ports/recompilations floating around on github and nuget, but they are not official. The https://docs.microsoft.com/en-us/archive/blogs/sqlrsteamblog/ is dead, the last entry is from 2018. There's a third-party company providing an RDLC renderer, but https://docs.microsoft.com/en-us/archive/blogs/sqlrsteamblog/microsoft-acquires-report-rendering-technology-from-forerunner-software. Nothing has been heard since. There is currently no ReportViewer designer for Visual Studio 2022. Getting one is currently the https://developercommunity.visualstudio.com/search?space=8&sort=votes&q=2022. 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 ?The Evolution of Conversational AI in Microsoft’s Ecosystem
Over the past two decades, conversational AI has shifted from a futuristic curiosity to a core part of how we interact with technology. And while many companies have shaped this field, one of the most influential players has consistently been Microsoft. From the early days of clippy (yes, that Clippy) to the cutting-edge Copilot ecosystem today, Microsoft’s journey mirrors the broader evolution of conversational AI itself. It’s a story of ambition, experimentation, setbacks, breakthroughs, and ultimately, transformation. In this blog, we’ll explore how conversational AI has developed within Microsoft’s ecosystem—how it started, the key milestones along the way, and where it’s all heading next. https://dellenny.com/the-evolution-of-conversational-ai-in-microsofts-ecosystem/Top 10 Things You Can Do with GitHub Copilot as a New Developer
If you’re just starting your coding journey, GitHub Copilot can feel like having a mentor right inside your code editor. It doesn’t just autocomplete code—it helps you learn, experiment, and ship projects faster. Here are the top 10 things you can do with GitHub Copilot as a new developer: https://dellenny.com/top-10-things-you-can-do-with-github-copilot-as-a-new-developer-2/
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.Let's remember how Visual Studio 2022 could eat up 100 GB of memory
Visual Studio 2022 is out! I think it's a good point to recall an interesting bug in VS 2022 Preview 3. How could Visual Studio 2022 eat up more than 100 GB of memory and what did XML bombs have to do with it? I've https://pvs-studio.com/en/blog/posts/csharp/0865/%20. Enjoy reading! 🙂 Now the bug is fixed, and yhttps://docs.microsoft.com/en-us/visualstudio/xml-tools/xml-document-validation?view=vs-2022#entity-reference-limit. 🙂 I would like to take this opportunity to congratulate Visual Studio and .NET development teams. Good job!
