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/
Build Custom Engine Agents in AI Foundry for Microsoft 365 Copilot
If you already have a multi‑agent AI application, you can surface it inside Microsoft 365 Copilot without adding another orchestration layer. Use a thin “proxy agent” built with the Microsoft 365 Agents SDK to handle Copilot activities and forward a simple request to your existing backend (in this example, we will use a simple Semantic Kernel multi‑agent workflow on top of Azure AI Foundry that writes and SEO‑optimizes blog posts). Develop fast and deploy to Azure with the Microsoft 365 Agents Toolkit for VS Code.The Future of AI: Creating a Web Application with Vibe Coding
Discover how vibe coding with GPT-5 in Azure AI Foundry transforms web development. This post walks through building a Translator API-powered web app using natural language instructions in Visual Studio Code. Learn how adaptive translation, tone and gender customization, and Copilot agent collaboration redefine the developer experience.The Future of AI: Vibe Code with Adaptive Custom Translation
This blog explores how vibe coding—a conversational, flow-based development approach—was used to build the AdaptCT playground in Azure AI Foundry. It walks through setting up a productive coding environment with GitHub Copilot in Visual Studio Code, configuring the Copilot agent, and building a translation playground using Adaptive Custom Translation (AdaptCT). The post includes real-world code examples, architectural insights, and advanced UI patterns. It also highlights how AdaptCT fine-tunes LLM outputs using domain-specific reference sentence pairs, enabling more accurate and context-aware translations. The blog concludes with best practices for vibe coding teams and a forward-looking view of AI-augmented development paradigms.
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 HeinziHow to Migrate Legacy Applications Using GitHub Copilot
Migrating legacy applications to modern platforms is one of the most challenging tasks in software development. Legacy systems often contain years of business logic, outdated frameworks, and dependencies that are no longer supported. At the same time, businesses need these applications to remain reliable and secure while benefiting from modern practices. This is where GitHub Copilot can become a powerful ally. By acting as your AI pair programmer, Copilot can help accelerate repetitive refactoring tasks, suggest modern equivalents for deprecated code, and provide scaffolding for newer frameworks. While it won’t completely automate a migration, it can dramatically reduce the effort and improve developer productivity. https://dellenny.com/how-to-migrate-legacy-applications-using-github-copilot/The Future of AI: Developing Lacuna - an agent for Revealing Quiet Assumptions in Product Design
A conversational agent named Lacuna is helping product teams uncover hidden assumptions embedded in design decisions. Built with Copilot Studio and powered by Azure AI Foundry, Lacuna analyzes product documents to identify speculative beliefs and assess their risk using design analysis lenses: impact, confidence, and reversibility. By surfacing cognitive biases and prompting reflection, Lacuna encourages teams to validate assumptions through lightweight evidence-gathering methods. This experiment in human-AI collaboration explores how agents can foster epistemic humility and transform static documents into dynamic conversations.Mastering GitHub Copilot: Tips, Shortcuts, and Prompts That Work
GitHub Copilot has quickly become one of the most powerful coding assistants available to developers. Powered by AI, it can autocomplete lines of code, generate functions, write tests, and even help with documentation. But to get the most out of Copilot, you need more than just enabling it in your IDE—you need to know how to prompt it effectively, use shortcuts, and apply the right strategies. Here’s a practical guide to mastering GitHub Copilot. https://dellenny.com/mastering-github-copilot-tips-shortcuts-and-prompts-that-work/Using GitHub Copilot to Teach Programming A New Approach for Educators
Artificial Intelligence is transforming the way we learn, work, and create. One of the most intriguing applications in computer science education is GitHub Copilot, the AI-powered coding assistant. While originally designed to boost developer productivity, Copilot has the potential to reshape programming education—acting as a tutor, coding partner, and motivator for students. In this post, we’ll explore how educators can use GitHub Copilot to support teaching, highlight potential benefits and pitfalls, and suggest practical strategies for integrating it into the classroom. https://dellenny.com/using-github-copilot-to-teach-programming-a-new-approach-for-educators/.WapProj build using "unvirtualizedResources" removed entry from manifest
I have a .wapproj that needs to use RegistryWriteVirtualization (aka "Flexible Virtualization) as described in Flexible virtualization - MSIX | Microsoft Learn This is for an MSIX package that will not be delivered via the Microsoft Store. The changes are made to the Package.appxmanifest file, and saved. The build action in Visual Studio removed the Capability declaration line for "unvirtualizedResources" from the Package.appxmaifest file before processing the file, leading to an error complaining that the RegistryWriteVirtualization requires this capability. Workaround: I can mark the file read-only outside of Visual Studio to keep VS from changing the file as a temporary workaround to prove out that the code depending upon these settings works. Why workaround is not acceptable: This workaround is not long-term viable, as other developers and automated workflows working on the project will lose the read-only setting (as it will not persist in GitHub) and have a broken build. It is clear that the VS code looking at this file is aware of both the desktop6 and virtualization schemas and their requirements and restrictions, but seemingly, although aware of other rescap capability extensions is unaware of this one. Requested action: Please add support for missing capabilities declarations in Visual Studio and/or underlying tools.
