Posts tagged ‘.NET’
Posts about the .NET stack — ASP.NET Core, Entity Framework Core, C# patterns, and tooling — applied to Optimizely CMS and Commerce projects.
-
:
Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell
What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(), prerendering.
-
:
OptiPowerTools.ScheduledJobsInsights: Execution History for Optimizely's Native Scheduled Jobs
A drop-in base class and Blazor UI that records what Optimizely CMS 13 scheduled jobs actually did — logs, metrics, result summaries, and retention.
-
:
OptiPowerTools.Hangfire 2.0.0: CMS 13 Support and Sample Jobs
OptiPowerTools.Hangfire 2.0 adds Optimizely CMS 13 / .NET 10 support and ships ready-to-run sample jobs to shorten Hangfire setup on Optimizely projects.
-
:
OptiPowerTools.Hangfire: A Drop-in Hangfire Integration for Optimizely CMS 12
OptiPowerTools.Hangfire is an open-source NuGet package that turns the manual Hangfire-on-Optimizely-CMS-12 setup into two lines of code.
-
:
Catalog Traversal with Hangfire. Part 3: Advanced Job Management
Part 3: using Hangfire for advanced catalog traversal job management in Optimizely Commerce — retries, monitoring, distributed execution, flexible scheduling.
-
:
Catalog Traversal in Action. Part 2: Real-World Scheduled Job Patterns
Part 2: applying the catalog traversal service to real Optimizely Commerce scheduled jobs with error handling, progress reporting, and resilience patterns.
-
:
Memory-Efficient Catalog Traversal in Optimizely Commerce. Part 1: Building the Service
Part 1 of a series on streaming catalog traversal in Optimizely Commerce — a memory-efficient service that processes large catalogs without OOM errors.
-
:
Adding Hangfire to Episerver/Optimizely CMS 12
Step-by-step guide to integrating Hangfire into Optimizely/Episerver CMS 12 with menu provider, controller, and authorization filter for background jobs.