search
AI OnAI Off
Baaijte.Optimizely.ImageSharp.Web v4 released
 Certification.png "Commerce Connect 14 Developer (Expert) Certification"){kind=small}
Vote:
Two small heads-ups from testing v4.0.0 on a live CMS 13.1.0 instance: Asset resolution under the new Applications routing worth a live smoke test. BlobImageProvider.GetAsync / BlobImageCache.GetContainer resolve the request to MediaData via UrlResolver.Current.Route(new UrlBuilder(path)). The API exists and isn't [Obsolete] on 13.1.0, so it restores/compiles/wires cleanly no load-time issues. I just couldn't confirm it still resolves /contentassets/… under CMS 13's per-application routing (my test env had no media). Probably fine, but it's the load-bearing call for the provider, so a quick ?width=300 on a real content asset would be reassuring. SixLabors.ImageSharp resolving below the declared floor. The csproj pins [3.1.12, 4.0.0), but my restore landed on 3.1.11 (one patch under) with no NU1605 build still succeeded, so latent rather than breaking, and possibly my own graph. Flagging it since the lib is built against 3.1.12. Happy to verify #1 on a CMS 13.1.0 instance with media if that's useful just say the word.
Edited,
Jun 13, 2026 14:34
Hi all,
Although I am no longer active in the Optimizely scene, I just uploaded a v4 version of the Baaijte.Optimizely.ImageSharp.Web package bringing support for v13 and updating the underlying SixLabors packages.
Summary of changes:
Targeting .NET 10 and Optimizely CMS 13
Package now uses:
Huge thanks go out to Jacob Jones for creating the actual PR for the upgrade.
Hope this helps!