VERSION 10.0 is compiled for Sitecore 10.0 use and will not work on earlier versions.
Requires Sitecore 10.0
Requires .NET 4.8
Constellation is a collection of utilities for .NET CMS implementers.
The Foundation.Caching namespace contains a Cache facade class that allows a developer to cache an object to
either the Sitecore Cache or the System Web Cache.
In addition to providing quick access to these APIs, the facade also provides support for scoping cached objects at the following levels:
Request an ICacheManager from your service locator to use in your Controllers.
Portions based on work by Christopher Giddings: https://cjgiddings.wordpress.com/2012/02/03/sitecore-caching-utility/ updated heavily
for modularity and to support Sitecore 9.x
Install-Package Constellation.Foundation.Caching -Version 10.0.1.23545
dotnet add package Constellation.Foundation.Caching --version 10.0.1.23545
<PackageReference Include="Constellation.Foundation.Caching" Version="10.0.1.23545" />
paket add Constellation.Foundation.Caching --version 10.0.1.23545
Moved configuration file to official Foundation folder to ensure correct execution order.
NuGet packages (2)
Showing the top 2 NuGet packages that depend on Constellation.Foundation.Caching:
Compatible with Sitecore 10.0 Requires Sitecore 10.0 Requires .NET Framework 4.8 Constellation is a collection of utilities for .NET CMS implementers. The Feature.PageTagging.SitemapXml namespace is an extension of the base Feature that adds explicit support for Foundation.SitemapXml, based upon the Page Search Engine Directive fields available in the PageTagging module. This feature is shipped separately in case the user is not using Constellation.Foundation.SitemapXml or has a different implementation that is not compatible with the PageTagging feature.
Compatible with Sitecore 10.0 Requires Sitecore 10.0 Requires .NET Framework 4.8 Constellation is a collection of utilities for .NET CMS implementers. The Foundation.Mvc.Patterns library is an opinionated library that provides some base Controller and Repository classes for jumpstarting a Sitecore project. The purpose is to get developers to better separate data access logic from controllers and also to hide some uninteresting concerns. Repositories: Classes which accept a context to specify the conditions for accessing data in Sitecore along with facts for use in the query. The Repository is responsible for getting the results of a query, any caching, and any transformation into ViewModel output. Base Repositories: Repository - Just the basics of setting up the relationship between the repository and the controller. CachingRepository - Adds caching of the repository's output to the mix. SingleItemRepository - Includes both of above and is centered around queries that will retrieve a single Item. ItemListRepository - Includes the first two and is centered around queries taht will retrieve multiple Items. Controllers: Classes which are responsible for handling the transition from Sitecore to the View, including setting up a Repository Context, and getting the results from the Repository for sending to the View. Base Controllers: DatasourceRenderingController - Use when a Rendering has a Datasource Item and that Item is what's being rendered. ItemListController - Use when a Rendering will present a number of Items that have to be looked up in some fashion. On Sitecore startup, this package will scan all assemblies for IController and IRepository implementations and automatically add them to Dependency Injection. This feature can be disabled/changed via the config file for this package.
This package is not used by any popular GitHub repositories.