✅ New post in my Modernizing .NET series: Validators in CoreWCF — how to bring back pre‑deserialization SOAP validation using AssertValidator + ParameterInspector.
🔗 https://medium.com/@michael.kopt/50c0eb2f2feb
#DotNet #DotNetCore #DotNet8 #DotNet9 #DotNet10 #ASPNet #ASPNetCore #CoreWCF #WCF #SOAP #CSharp
Next part of Modernizing .NET:
🧼 Part 3 - Migrating WCF SOAP services to .NET 8? I used CoreWCF to keep legacy endpoints alive—no rewrite needed.
🔗 https://medium.com/@michael.kopt/modernizing-net-part-3-surviving-soap-with-corewcf-8a947ebd55e9
#WCF #CoreWCF #SOAP
#DotNet #DotNet8 #DotNet9 #ASPNetFramework #ASPNet #ASPNetCore #CSharp
🧼 Modernizing .NET — Part 3: Surviving SOAP with CoreWCF

How I revived legacy WCF SOAP services in .NET 8 using CoreWCF — without rewriting hundreds of public endpoints.

Medium
C64 C Sharp Coding Brings the Commodore 64 Into the .NET Era - The Oasis BBS

C64 C Sharp coding brings live C64 development to .NET, showing how C# and modern tools create real 8-bit programs with instant feedback.

The Oasis BBS
🧙‍♂️ Modernizing .NET – Part 2: HttpContext is the dark magic of ASP.NET Framework. Here's how I revived HttpContext.Current in .NET 8—without rewriting 1000 endpoints.
🔗 https://medium.com/@michael.kopt/%EF%B8%8F-modernizing-net-part-2-httpcontext-and-the-dark-magic-of-migration-621b0ce7586c
#DotNet #DotNet8 #DotNet9 #ASPNetFramework #ASPNet #ASPNetCore #CSharp #CodeMigration #LegacyCode
🧙‍♂️ Modernizing .NET — Part 2: HttpContext and the Dark Magic of Migration

How I revived HttpContext.Current in .NET 8 to support legacy ASP.NET Framework code — without rewriting thousands of endpoints.

Medium
.NET and .NET Framework November 2025 servicing releases updates - .NET Blog

A recap of the latest servicing updates for .NET and .NET Framework for November 2025.

.NET Blog
🚀 Modernizing .NET — Part 1: C# Preprocessor Directives

How I unified a legacy ASP.NET Framework and .NET 8 codebase using conditional compilation and custom preprocessor directives.

Medium

Still running your app on an older .NET version? You are missing out!

Here is why every modern business is upgrading right now.
• Faster runtime performance
• Built-in AI & ML support out of the box
• Lighter, safer deployments with Native AOT
• Enhanced security and cloud-ready optimization
• Less code. More productivity. More profit.

Old tech slows growth, .NET 9 is how you scale and beyond.Contact Prishusoft today!

Read More: https://prishusoft.com/product-reengineering

#AIinSoftware #TechUpgrade #Dotnet9

Preparing Your .NET MAUI Apps for Google Play's 16 KB Page Size Requirement - .NET Blog

Learn about the upcoming 16 KB page size requirement for Google Play and how to ensure your .NET MAUI apps are ready for the November 2025 deadline.

.NET Blog
.NET STS releases supported for 24 months - .NET Blog

.NET STS releases will be supported for 24 months

.NET Blog
When #dotnet9 was released last year that broke dotnet watch test for months.

Trying out
#dotnet10 I see that dotnet watch run is even broken (on Microsoft's own dotnet 10 devcontainer). And nobody seems to care.

I expect the same shitshow this release :(

github.com/dotnet/sdk/issues/49563

#dotnet #dev #microsoft
dotnet watch does not restart on request hangs waiting for process · Issue #49563 · dotnet/sdk

Description: I am trying to run dotnet watch in a standalone blazor web assembly project(i have seem this behaviour with my asp.net backed as well) when the app requests a restart or i do a CTRL+R ...

GitHub