News For Dev-ops

Pure Virtual C++ 2026, our free, one-day virtual conference for the whole C++ community, is live right now! Join hosts Mads Kristensen and Sinem Akinci for three hours of featured sessions, and real-time Q&A in the chat. Watch live now → streaming on YouTube (Microsoft Reactor channel) and Twitch. Bring your curiosity and your questions! Our hosts and speakers are in the live chat, so this is a chance to interact with the speakers directly. Today's live schedule The broadcast starts now . Here's the schedule: Time (PT) Session Speaker 9:00 AM Welcome & opening Mads Kristensen, Sinem Akinci 9:00 AM C++ semantic awareness in the CLI: From Project Load to Code Change Sinem Akinci 9:20 AM Mind The Gap: C++/Rust Interop Victor Ciura 9:45 AM From Completions to Agents: AI-Driven C++ in Visual Studio Augustin Popa 10:25 AM Cut Your Build Times Without Becoming a Build Expert David Li 10:40 AM C++/WinRT: Build faster and smaller with...

You've built an eval. You've established a baseline and found the gaps. Now you have hypotheses about how to fix them: maybe a documentation rewrite, or a different CLI output format. The natural next step is to ship the change and measure again. Don't do that just yet. Why most hypotheses fail Every improvement you think of is a hypothesis. "If I add a warning callout to the release notes, the agent will use the CLI instead of attempting a manual upgrade." It sounds reasonable, might even be obvious. But LLMs don't reason the way you expect them to, and obvious changes produce counterintuitive results with uncomfortable regularity. We've seen this first-hand working on a SharePoint Framework (SPFx) project upgrade scenario. SPFx projects upgrade incrementally, version by version, each step introducing its own configuration- and dependency changes. The agent needed to discover a CLI tool from documentation. The documentation included a tip recommend...

Today, AWS announces standardized product metadata for Amazon Bedrock in AWS Data Exports (Cost and Usage Report), giving FinOps teams and cloud administrators consistent, structured attributes to understand  Bedrock costs. AWS Data Exports lets you create customized exports of your AWS cost and usage data and deliver them to Amazon S3 for querying with Amazon Athena or loading into your data warehouse. With these attributes, you can attribute Bedrock spend without building custom logic to parse various product metadata in CUR 2.0. The standardized attributes include model provider, model name, pricing unit, inference type (such as input tokens or output tokens), and feature (the inference serving mode, such as On-Demand or Batch), along with a unified "Amazon Bedrock" product family name that consolidates all Bedrock costs. In CUR 2.0, the model provider, model name, inference type, and feature attributes are available in the product map column, and pricing unit is availab...

Pure Virtual C++ 2026 , our free, one-day virtual conference for the whole C++ community, goes live tomorrow, Tuesday, July 21, 2026 at 9:00 AM PT (16:00 UTC) on YouTube (Microsoft Reactor) and Twitch, hosted by Mads Kristensen and Sinem Akinci . Register now → But you don't have to wait until tomorrow to start watching. Our full slate of on-demand sessions is available right now on the Visual Studio YouTube channel. These talks aren't aired during the live broadcast. They're yours to watch on your own schedule, today or any day after. [cta-button text="Watch the on-demand playlist" url="https://www.youtube.com/playlist?list=PLDd6OJEZ3V7c" color="btn-primary" align="left"] And tomorrow, we go live Before we dive into the on-demand sessions, here's our conference schedule for tomorrow. The broadcast runs about three hours starting at 9:00 AM PT (16:00 UTC) on Tuesday, July 21. During the five featured sessions , we'l...

Suppose you have some C++/WinRT code that receives a delegate from an outside source, and you might invoke that delegate from a potentially different COM context. However, the original delegate may not be agile. How can you make an agile version of that delegate? The easy way is to wrap the delegate in an agile_ ref , and then resolve the agile_ ref back to a delegate when you want to invoke it. template<typename Delegate> Delegate make_agile_delegate(Delegate const& d) { return [agile = winrt::agile_ref(d)](auto&&...args) { return agile.get()(std::forward<decltype(args)>(args)...); }; } But if it were that easy, why would we call this article "part 1"? More in part 2. Post Updated on July 20, 2026 at 03:00PM Thanks for reading from devamazonaws.blogspot.com

Amazon CloudWatch announces the launch of coding agent insights, giving engineering leaders visibility into how AI coding tools are driving value across their organization. Coding Agent Insights integrates with Claude apps gateway for AWS to collect telemetry from Claude Code without additional instrumentation. Other supported coding agents include Codex and GitHub Copilot.  As organizations scale AI coding agent adoption, they need to understand return on investment. Coding agent insights is built on OpenTelemetry metrics emitted by your coding agents and presents them alongside your existing CloudWatch operational data. This helps you answer questions like which teams would benefit from expanded access, where are agents accelerating delivery, and how can you right-size token budgets across departments. You can track spend trends, set proactive token billing alerts, correlate agent adoption with improvements in commit throughput and pull request velocity, or identify the models...