Skip to content
Open source core .NET 4.5 and SQL Server Sannois, France
MAGELIAWebStore
Platform · 16 of 18

Extend the edges, not a fork

Start from the client and sample code, override components where business rules differ and keep upgrades possible.

01

A practical starting point

The .NET client, the ASP.NET MVC sample store and the administration console shorten the distance from install to a working storefront.

02

Component overrides

The extensibility model is designed to replace specific behaviour, such as tax calculation, without forking the whole product.

03

Standards keep the door open

Building on .NET, OData and SQL Server means the team can use familiar tools and hire for familiar skills.

Customise the decision point

Before extending, find the smallest component that actually differs. Replacing one rule is easier to test and maintain than copying a large section of the application into a local fork.

Keep customisations in a separate project with its own tests. Document the extension point and the reason it was chosen.

Upgrade with evidence

A successful extension is one that can survive an upgrade. Record the version it targets and rerun the relevant tests when the core changes.

In practice
  • Prefer an override over a fork.
  • Keep custom code in a separate, testable project.
  • Record the core version each extension targets.
  • Rerun extension tests after every core upgrade.

Related capabilities

Primary sources

Reference shelf

Standards, documentation and tools that are relevant to this topic. They open on the publisher's site.

  • .NET platform Runtime, tooling and framework documentation from Microsoft.
  • OData The open data protocol used by the WebStore services layer.
  • NuGet Package distribution used by the .NET client and samples.
  • Microsoft Learn Reference material for the Microsoft development stack.
  • GitHub Source hosting and issue tracking for .NET projects.
  • SQL Server Database engine documentation and editions.
  • OWASP Application security guidance and cheat sheets.
  • Semantic Versioning Version numbering conventions used in release notes.
  • W3C Web standards for markup, accessibility and internationalization.
  • web.dev Performance, accessibility and Core Web Vitals guidance.
Next step

Put this capability against your own catalog

The useful test is a real assortment, a real market and a real order. Bring those to a conversation rather than a generic feature list.