Rider 2026.2 EAP 6 is out! This preview build improves how async call stacks are presented during debugging. The debugger now reduces noise from generated async and task infrastructure frames, making it easier to follow the logical flow of your code instead of digging through compiler-generated implementation details. You can download the EAP build from our website here 👉 jetbrains.com/rider/nextvers…

Released .NET Starter Kit v1.8 for building binary or source-only NuGet packages via GitHub or AZDO. New: .slnx solutions, Azure DevOps pipeline templates, C# Coding Guidelines skills, .NET 10, updated dependencies, a Fallout-based build pipeline, and .editorconfig refinements.

Released Mockly 1.7 with request header matching, generic For(HttpMethod)/Head/Options, ProblemDetails responses, file/stream/bytes responders, query & form matching, response headers, new assertions, and automatic agent skill registration. mockly.org/

Formal Complaint: GitHub Copilot Token-Based Billing Model @GitHubCopilot Subject: Critical Issue with New Token-Based Billing — Product Has Become Unusable Summary of the Issue I am writing to formally complain about the recent shift to token-based billing for GitHub Copilot, which was rolled out this morning. This change has fundamentally broken the value proposition of the product and is rendering it unusable for paying subscribers, including myself. Specific Problems Observed Within just a few hours of the new billing model going live, the developer community is already reporting alarming consumption patterns: Pro subscribers paying $39/month are reporting that 60% of their monthly credits were depleted in only 2 hours of normal usage. One user reported losing 20% of their entire monthly allowance from a single file review — no code generation, just a review. At this rate, a paying customer will exhaust their plan in less than a single working day, despite paying a premium subscription fee. This is not "normal usage at scale" — this is a broken pricing model that punishes the very developers who rely on Copilot daily for their work. Why This Makes the Product Unusable The core promise of Copilot was a predictable, always-available AI coding assistant integrated into the developer workflow. Token-based billing destroys that promise because: Developers cannot predict costs. Every keystroke, every file review, every refactor becomes a financial calculation rather than a productivity boost. The tool actively discourages use. Users will hesitate before invoking Copilot, defeating the entire point of an AI assistant. The $39/month Pro tier is misleading. Customers signed up expecting reliable access, not a pre-paid metered service that runs out mid-morning. Heavy users — your most loyal customers — are penalized the most. The Competitive Reality While GitHub Copilot is moving toward a restrictive metered model, competitors are moving in the opposite direction: Cursor offers Composer 2.5 with unlimited usage once token limits are reached on their plans, ensuring developers can keep working without interruption. Other tools (Windsurf, Cody, Continue) offer flat-rate or far more generous usage tiers. Developers will not stay on a platform that runs out of credits before lunch when alternatives offer uninterrupted productivity at the same or lower price point. My Demand If GitHub does not revise this licensing model, the product is effectively dead. I am requesting: Reinstatement of a flat-rate unlimited (or effectively unlimited) tier for Pro and Pro subscribers. Transparent, upfront communication of what each interaction actually costs in tokens. A grace period or credit refund for users who burned through their allowance under the new model without warning. A long-term commitment that core IDE-integrated features will not be metered into uselessness. Without these changes, I — along with a growing number of developers — will be canceling our subscriptions and migrating to Cursor or competing alternatives. The decision to monetize aggressively at the expense of usability will not be remembered as a successful pivot; it will be remembered as the moment GitHub Copilot lost its market. Please escalate this to the product and pricing teams immediately.

Isn't it about time @github or @githubstatus give a little update on the Copilot billing situation?

Back from the Kraków edition of @update_conf. Two talks, great conversations, plenty of laughs, and a flawlessly organized event. Huge thanks to the crew, and everyone who made it such a memorable week. #dotnet #csharp #community

3 prompts in the early morning with Sonnet 4.6 and I've already consumed a full day of #copilot credits. I guess I'm going to have to switch to #claude now. #mvpbuzz

⚙️ Design patterns give developers a shared vocabulary: Repository, Factory, Strategy, Observer, Decorator, etc. Well-known patterns make code easier to understand, extend, and maintain. 💡 If a class fits multiple patterns, it may be doing too much. #csharp #designpatterns

🌊 Another wave of expert sessions is taking over #UCK26! Jonathan Tower, Chris Woodruff, @DKrzyczkowski, @konradkokosa, @ddoomen, and @ptrstpp950 shared their expertise and inspired the community.

Mockly 1.6 will now automatically create a skill in your project's .agents/skills folder to help get the most out of HTTP mocking in .NET. Check out it out at github.com/dennisdoomen/mock…

Today and tomorrow, I'll be at the Polish edition of the amazing UpdateConf Krakow. I'm not just doing one, but two separate sessions. Will I see you there?

I watched “Star Wars: The Mandalorian and Grogu”in IMAX. Back in 2019, I had only seen the opening of The “Mandalorian” while examining the LED-shot “virtual production” technology, but this time I had no problem diving in. Action, car chases, close-quarters combat, sword fights, gun battles, death matches, aerial combat, giant monsters, giant mechs. A complete “everything versus everything” showcase. CGI, puppets, special makeup, animatronics, stop motion. Even the behind-the-scenes craftsmanship feels like it has everything packed in. X-Wings, AT-ATs, AT-RTs, speeders, stormtroopers, droids. Nearly every element from across the entire history of the Star Wars saga is in as well. An entertainment spectacle made with craftsmanlike skill by Jon Favreau.

Every codebase has boundaries. Inside a boundary, share abstractions freely. Across boundaries, use explicit contracts. Rule of thumb: “If this were a separate deployable unit, would this dependency still make sense?” Good boundaries reduce coupling. #dotnet #csharp

I’ve refreshed csharpcodingguidelines.com with new General Guidelines, a dedicated Testability section, updated modern C# guidance, and a rule for AI-generated code: use it if it helps, but own every line. See github.com/dennisdoomen/CSha…

⚔️ Last week at Techorama Belgium, I took over room 6 at Kinepolis Antwerp talking about building HTTP APIs in .NET! Covered: responsibility levels, versioning, OpenAPI docs, error/success codes, async APIs, minimal API & more. So much devs often overlook here. 🧵

Cooking up something new 🧑‍🍳 Join the waitlist for early access to technical preview of the GitHub Copilot app 👇 gh.io/github-copilot-app?utm…

It's finally here! Process API Improvements in .NET 11 devblogs.microsoft.com/dotne…

#UCK26 | From building properly versioned and well-documented HTTP APIs in ASP.NET Core to practical ways of keeping large C# projects maintainable, @ddoomen will share approaches, tools and engineering practices that help teams stay in control as products evolve. Expect practical insights into API design, OpenAPI, versioning strategies, .editorconfig, SonarCloud, NUKE pipelines, code quality and sustainable architecture decisions. 🎤 Learn more about the sessions: krakow.updateconf.net 💻 Watch live: now.updateconference.net 📍 27–28 May 2026, Krakow 🎟️ Want 10% off? Use discount code: DennisDoomen10 See you all in Krakow #UpdateConference #UpdateConferenceKrakow #dotnet #architecture #cleancode #aspnetcore #apidesign

What do you use for mocking HTTP requests in unit tests? Have you tried github.com/dennisdoomen/mock… already? Try it and share your opinions here.

🎤 Speaking at Techorama Belgium again! I'll share what I've learned about building professional HTTP APIs in .NET — API design, HTTP error codes, async APIs, caching, versioning, contract design, concurrency & OpenAPI. Will I see you there? #Techorama #dotnet