home.social

#dotnetcore — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #dotnetcore, aggregated by home.social.

fetched live
  1. 🧭 Modernizing .NET, Part 33: good architecture can still be the wrong migration strategy.

    📨 We used events, CQRS, and Clean Architecture selectively—but avoided combining the ASP.NET Core move with a full DDD, event-sourcing, or microservices rewrite.

    Preserve behavior. Isolate dependencies. Modernize incrementally. 🧱

    medium.com/@michael.kopt/moder
    #DotNet #DotNetCore #ASPNET #ASPNETCore #SoftwareArchitecture

  2. 🧭 Modernizing .NET, Part 33: good architecture can still be the wrong migration strategy.

    📨 We used events, CQRS, and Clean Architecture selectively—but avoided combining the ASP.NET Core move with a full DDD, event-sourcing, or microservices rewrite.

    Preserve behavior. Isolate dependencies. Modernize incrementally. 🧱

    medium.com/@michael.kopt/moder

  3. New version of my #avalonia_ui testing framework today. nuget.org/packages/Mostlylucid

    One of my least downloaded but the one I use most. For AvaloniaUI apps like StyloAgent / lucidView / lucidResume it allowed me to automate UI build & test.

    New version adds stuff like drag & drop support; futher support for user interactions (esp around docks) etc..etc...

    #avalonia_ui #dotnetcore #testing #playwright (like)

  4. New version of my #avalonia_ui testing framework today. nuget.org/packages/Mostlylucid

    One of my least downloaded but the one I use most. For AvaloniaUI apps like StyloAgent / lucidView / lucidResume it allowed me to automate UI build & test.

    New version adds stuff like drag & drop support; futher support for user interactions (esp around docks) etc..etc...

    #avalonia_ui #dotnetcore #testing #playwright (like)

  5. 🏗️ Framework migrations rarely fit one architecture label.

    In Part 32, I break down how layered architecture, modular monolith structure, middleware flow, and service-oriented boundaries can coexist in an ASP.NET Core migration.

    🧱 Not rivals.
    🔁 Different levels.
    🔌 Different responsibilities.

    medium.com/@michael.kopt/%EF%B
    #dotnet #dotnetcore #aspnet #aspnetcore #architecture

  6. 🏗️ Framework migrations rarely fit one architecture label.

    In Part 32, I break down how layered architecture, modular monolith structure, middleware flow, and service-oriented boundaries can coexist in an ASP.NET Core migration.

    🧱 Not rivals.
    🔁 Different levels.
    🔌 Different responsibilities.

    medium.com/@michael.kopt/%EF%B

  7. 🔌 Don’t migrate every dependency directly.

    In ASP.NET Core migrations, ports work best when they describe application needs, not library APIs.

    - Wrap SmtpClient behind IEmailSender.
    - Move dictionary token storage behind IUserTokenStore.
    - Swap adapters when the infrastructure is ready.

    medium.com/@michael.kopt/use-p

    #DotNet #DotNetCore #SoftwareArchitecture #ASPNET #ASPNETCore

  8. 🔌 Don’t migrate every dependency directly.

    In ASP.NET Core migrations, ports work best when they describe application needs, not library APIs.

    - Wrap SmtpClient behind IEmailSender.
    - Move dictionary token storage behind IUserTokenStore.
    - Swap adapters when the infrastructure is ready.

    medium.com/@michael.kopt/use-p

  9. 🌿 Part 30 of Modernizing .NET starts the architecture chapter.

    First topic: Strangler Fig Architecture.

    Don’t rewrite the whole ASP.NET Framework app at once.

    ✅ Route one feature.
    ✅ Replace one slice.
    ✅ Keep fallback.
    ✅ Delete the legacy path when stable.

    medium.com/@michael.kopt/moder
    #dotnet #dotnetcore #aspnet #aspnetcore

  10. 🌿 Part 30 of Modernizing .NET starts the architecture chapter.

    First topic: Strangler Fig Architecture.

    Don’t rewrite the whole ASP.NET Framework app at once.

    ✅ Route one feature.
    ✅ Replace one slice.
    ✅ Keep fallback.
    ✅ Delete the legacy path when stable.

    medium.com/@michael.kopt/moder

  11. 🧙‍♂️ HttpContext.Current was only step one.

    Legacy System.Web code often expects Request.Params, Response.Write, headers, redirects, and connection checks.

    🧩 Wrap the old surface
    🔌 Delegate to ASP.NET Core
    ⚠️ Delete the bridge later

    #dotnet #dotnetcore #aspnet #aspnetcore
    medium.com/@michael.kopt/%EF%B

  12. 🧙‍♂️ HttpContext.Current was only step one.

    Legacy System.Web code often expects Request.Params, Response.Write, headers, redirects, and connection checks.

    🧩 Wrap the old surface
    🔌 Delegate to ASP.NET Core
    ⚠️ Delete the bridge later


    medium.com/@michael.kopt/%EF%B

  13. Part 28 of Modernizing .NET: memory spikes on Linux are often file I/O problems in disguise.

    🧠 trim backup scope
    🌊 stream copies
    🚦 throttle parallelism
    🗂️ check CIFS serverino

    medium.com/@michael.kopt/moder
    #dotnet #dotnetcore #aspnet #aspnetcore #linux #performance

  14. Part 28 of Modernizing .NET: memory spikes on Linux are often file I/O problems in disguise.

    🧠 trim backup scope
    🌊 stream copies
    🚦 throttle parallelism
    🗂️ check CIFS serverino

    medium.com/@michael.kopt/moder

  15. Modernizing .NET Part 27! 🔤

    Solving the "Windows vs Linux" string sorting headache.

    ✅ Consistent behavior across OS
    ✅ Custom NLS-compatible comparer
    ✅ Fix broken CI/CD tests

    medium.com/@michael.kopt/moder
    #dotnet #dotnetcore #csharp #aspnet #aspnetcore #linux #unicode #windows #nls #icu #sorting #algorithm

  16. Modernizing .NET Part 27! 🔤

    Solving the "Windows vs Linux" string sorting headache.

    ✅ Consistent behavior across OS
    ✅ Custom NLS-compatible comparer
    ✅ Fix broken CI/CD tests

    medium.com/@michael.kopt/moder

  17. Modernizing .NET Part 26! 🛡️

    Today we’re implementing the Rate Limiting Middleware in ASP.NET Core.

    ✅ Concurrency control
    ✅ Stable response times under load
    ✅ No more cascading failures

    medium.com/@michael.kopt/%EF%B
    #dotnet #csharp #dotnetcore #aspnet #aspnetcore #ratelimiting #performance

  18. Modernizing .NET Part 26! 🛡️

    Today we’re implementing the Rate Limiting Middleware in ASP.NET Core.

    ✅ Concurrency control
    ✅ Stable response times under load
    ✅ No more cascading failures

    medium.com/@michael.kopt/%EF%B

  19. Modernizing .NET Part 25! 🛡️

    Today we’re talking about rate limiting as a safety mechanism.

    ✅ Prevent CPU thrashing
    ✅ Manage concurrency correctly
    ✅ Controlled degradation vs. catastrophic failure

    medium.com/@michael.kopt/%EF%B
    #dotnet #aspnet #dotnetcore #aspnetcore #csharp #programming #performance

  20. Modernizing .NET Part 25! 🛡️

    Today we’re talking about rate limiting as a safety mechanism.

    ✅ Prevent CPU thrashing
    ✅ Manage concurrency correctly
    ✅ Controlled degradation vs. catastrophic failure

    medium.com/@michael.kopt/%EF%B

  21. Modernizing .NET Part 21! 📂

    Moving custom WebDAV server logic to .NET Core.

    ✅ Cross-platform support
    ✅ ~40% faster request processing
    ✅ Single codebase strategy

    medium.com/@michael.kopt/moder

  22. Modernizing .NET Part 20! 🏗️

    Migrating legacy .aspx pages to .NET Core without a full rewrite.

    ✅ Zero ViewState overhead
    ✅ Keep existing .aspx URLs
    ✅ Modern API-driven UI

    medium.com/@michael.kopt/%EF%B
    #dotnet #dotnetcore #aspnet #aspnetcore #csharp #webforms

  23. Modernizing .NET Part 20! 🏗️

    Migrating legacy .aspx pages to .NET Core without a full rewrite.

    ✅ Zero ViewState overhead
    ✅ Keep existing .aspx URLs
    ✅ Modern API-driven UI

    medium.com/@michael.kopt/%EF%B