Skip to the content.

Welcome to

The best and easiest namespace to Share Sitecore code: Shared.SharedSitecore


🔭 Current Projects


👯 Newest Projects!


The Evolution of the SharedSitecore Namespace

I. WhateverYouWant - Per Company, Per Project, etc., providing practically zero discoverability.
II. Sitecore.Shared - Made popular by John West.
III. Sitecore.Sharedsource - Made popular by John West.
IV. SitecoreShared - In an effort to avoid Sitecore namespace conflicts.
V. SeveralVariationsAndVersions - Insert several other variations and versions of the namespaces.
VI. Shared.SharedSitecore - Now, I introduce, the best so far: Shared.SharedSitecore. This should provide greatest discoverability (comes before Sitecore) and least namespace conflicts.
VII. Shared.SeleniumExtensions - I am now following this naming convention everywhere.
VIII. Shared - I am even working on a few projects worthy of the root level: Shared.

With well over 1000+ various packages/projects spread out across Github, Azure DevOps and various systems, it will take a little while to get everything moved.

Maintained by: David Walker aka Radical Dave aka Sitecore Dave

Disclaimer: All content is the opinion of its authors and do not represent the views of myself, employer or anyone else.

Unless otherwise stated, all code is provided as is, without warranties or conditions of any kind, either express or implied, including without limitation any implied warranties or conditions of title, fitness for a particular purpose, merchantability or non-infringement.

All trademarks are the property of their respective owners, ie: Azure, GitHub, Microsoft, Sitecore