DotNet course on youtube in Telugu Link: youtu.be/A2xRFnnV6G8?si=T2Ue… #YouTuThumbnail #learn #course #youtube #techquestconnect

Names describe intent. Wiring defines behaviour. How a 2026 AI coding tool "fixed" a button that compiled, passed review, and never ran once #SoftwareEngineering #AICoding #DotNet #LegacyModernization #CodeReview linkedin.com/posts/sukumar-t…

I fully understand the chore here, having just updated a bunch of repos to dotnet 10, but can't you still have common flow for all the rest? Don't you have per repo nuget token secret now?

With .NET, the Microsoft Agent Framework, and Microsoft Foundry, you can design multi-agent solutions where specialized agents collaborate, coordinate, and get real work done. Learn how: aka.ms/dotnet/multi-agent-sy…

Web API con .NET CORE y Swagger Dapper SQL Server ⏱️ 6.9 hours ⭐ 4.36 👥 1,756 🔄 Dec 2024 💰 $14 → 100% OFF comidoc.com/udemy/web-api-co… #dotnet #webapi #sqlserver #udemy

🚨 Duplicate requests breaking your ASP.NET APIs? Implement the Idempotency Pattern to safely handle retries and prevent unwanted duplicate operations! 🔄 🛡️ Guide: ottorinobruni.com/how-to-imp… How do you handle duplicates? 👇 #dotnet #ASPNETCore #Idempotency

🚀 dotnetsheff is back 7th July in Sheffield with Sara Gowen talking Testcontainers EF Core testing with real databases—pizza, people, and practical dev learning meetup.com/dotnetsheff/event… #dotnet #efcore #testcontainers #sheffield #tech

Not sure I agree. CQRS makes sense even for smaller crud apps to differentiate data access across services. But yeah the other stuff is ridiculous. A Laravel event style system would be nice for dotnet though.

これUnity最適化してナレッジを組む必要があって、汎用ナレッジをうまく活用しつつ～とするとだめなやつかこれ。わかりやすい話だとbuildが～ってプロンプト書いてるとdotnet build使われる雰囲気がある。

Pointframe just got video trimming ✂️ You can now trim screen recordings in-app with a live preview, precise start/end handles, and one-click Save trimmed copy. It launches directly from Recent recordings in the tray, with improved cancellation handling and a cleaner workflow. Try it and tell me what you want next 👇 github.com/dimitar-radenkov/… #buildinpublic #dotnet #windows #productivity

I have a goal of $650. Come support my latest project to improve security for @Yubico and @dotnet users. github.com/sponsors/benjcall…

How it speeds up development: Less boilerplate, fewer manual mapping bugs, faster onboarding for new devs, and clean separation of concerns. Spend more time on business logic, less on plumbing. 📦 nuget.org/packages/Transitio… #dotnet #Transitio #BuildInPublic

Why use Transitio? If you're tired of writing repetitive mapping code between DTOs and models, Transitio handles it for you — expression-based, fast, and DI-ready. A clean, modern alternative for your mapping layer. #dotnet #DeveloperTools #Transitio #BuildInPublic

What is Transitio? 🚀 A lightweight, high-performance object mapping framework for .NET — supports profiles, nested mapping, and dependency injection. Targets .NET 8 & .NET 10. #dotnet #csharp #Transitio #BuildInPublic

AI、隙あらばUnity Test Frameworkじゃなくてdotnet使う雰囲気がある。

🚀C# 14: Top 5 Features Every .NET Developer Must Know in 2026 ✅ Extension Members ✅ Field-Backed Properties ✅ Improved Lambdas ✅ Better Pattern Matching ✅ Productivity Enhancements Read more: niotechone.com/c-14-preview-… #csharp #dotnet #niotechone

I wasn't consulted on the product. WCF backend server that dotnet core talks to.

Day 1 → Day 14. In just two weeks, my app will be live. So far we’ve built: ✅ Rich Domain Model with Value Objects ✅ Aggregate Root with strong encapsulation ✅ CQRS commands & queries ✅ EF Core SQLite persistence ✅ Blazor UI with MudBlazor ✅ Clean Architecture end-to-end ✅ AI-powered Code Reviewer & Judge agents The MVP already works. You can create activities, save them to SQLite, and view them in the app. Two weeks ago, this was just an idea. Now it’s becoming a product. Shipping beats dreaming. #dotnet #buildinpublic #blazor #cleanarchitecture #softwaredevelopment

#dotnet LTS support window too short for upgrade and adoption cycles ⬇️ This still comes up a lot. Have Microsoft got the balance right between being able to get us new features quickly while also being able to support existing releases for a reasonable time? Or do you think LTS version should have longer cycles for example? github.com/dotnet/core/issue…