Table of Contents

Namespace ToSic.Sxc

ToSic.Sxc is the namespace for 2sxc code.

Namespaces

ToSic.Sxc.Adam
ToSic.Sxc.Apps

This extends the ToSic.Eav.Apps with things relevant in a CMS. Most of this isn't documented yet.

ToSic.Sxc.Blocks

A unit of output it 2sxc is called a Block. In Dnn-Link, this can be like a Module, except that blocks can be inside other blocks.

Looking at it from the Platform like Dnn, the entry object is an ICmsBlock which contains context information (in Dnn's case, ModuleId etc.). Inside it is an IBlock which can itself contain more IBlocks.

Note that each Block itself has Views ICmsView and data specific to that block.

ToSic.Sxc.Cms.Data
ToSic.Sxc.Code
ToSic.Sxc.Context

Context information for the current request / scenario.

ToSic.Sxc.Data
ToSic.Sxc.DataSources
ToSic.Sxc.Dnn

This contains interfaces that are specific to 2sxc in Dnn.

The purpose is that both the EAV and 2sxc are meant to be platform agnostic, but Razor and WebApi developers in Dnn still need access to some helpers.

ToSic.Sxc.Edit.Toolbar
ToSic.Sxc.Engines

The Engines are the part of 2sxc that create output based on data.

It's basically the part that takes a full configuration, consisting of...

  1. What App
  2. What View
  3. What Template
  4. What Data - could be from a query or from the instance

...and then generates an HTML using Razor or Tokens or whatever engine may come in future.

ToSic.Sxc.Images
ToSic.Sxc.LookUp

This extends the abilities of ToSic.Eav.LookUp with more look-up objects for things that are either web-specific (like request objects) or DynamicData specific.

ToSic.Sxc.Search

The things here enable searching. They basically ensure that the CMS can ask for data to then index however the CMS wants to.

ToSic.Sxc.Services
ToSic.Sxc.WebApi