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.
Start from the client and sample code, override components where business rules differ and keep upgrades possible.
The .NET client, the ASP.NET MVC sample store and the administration console shorten the distance from install to a working storefront.
The extensibility model is designed to replace specific behaviour, such as tax calculation, without forking the whole product.
Building on .NET, OData and SQL Server means the team can use familiar tools and hire for familiar skills.
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.
A successful extension is one that can survive an upgrade. Record the version it targets and rerun the relevant tests when the core changes.
Standards, documentation and tools that are relevant to this topic. They open on the publisher's site.
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.