> For the complete documentation index, see [llms.txt](https://docs.zongsoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zongsoft.com/documentation/en/framework/core.md).

# Core Library

Responsibilities and main namespace of Zongsoft.Core core class library.

[`Zongsoft.Core`](https://github.com/Zongsoft/framework/tree/main/Zongsoft.Core) is the core class library of Zongsoft framework and does not rely on third-party class libraries. It provides basic abstractions, utility classes, service models, and runtime capabilities that are shared by other modules in the framework.

## Main Abilities

* Collections, transformations, randomization, enumerations, and common extensions.
* Communication, execution pipeline and component model.
* Configuration, options, INI Profile and resource handling.
* Caching, serialization, transactions and lightweight state machines.
* Security, credentials, and authorization basic abstractions.
* service container, command model, background worker.
* Terminal application support.

## Code Location

```
framework/Zongsoft.Core
```

## Namespace

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref">Page</th></tr></thead><tbody><tr><td><strong>common base</strong></td><td>Collections, common tools, reflection, resources, and text processing.</td><td><a href="/documentation/en/framework/core/common.md">Zongsoft.Common</a></td></tr><tr><td><strong>Components and Services</strong></td><td>Component model, commands, application context, service access and distributed collaboration.</td><td><a href="/documentation/en/framework/core/components.md">Zongsoft.Components</a></td></tr><tr><td><strong>version expression</strong></td><td>Semantic versioning, four-segment numerical version numbers, and version comparison.</td><td><a href="/documentation/en/framework/core/version.md">Zongsoft.Versioning</a></td></tr><tr><td><strong>Configuration and data abstraction</strong></td><td>Configure bindings, options files, data access abstractions, and data metadata.</td><td><a href="/documentation/en/framework/core/configuration.md">Zongsoft.Configuration</a></td></tr><tr><td><strong>runtime capabilities</strong></td><td>Caching, communication, messaging, scheduling, serialization, transactions and state flow.</td><td><a href="/documentation/en/framework/core/caching.md">Zongsoft.Caching</a></td></tr><tr><td><strong>Application support</strong></td><td>diagnostics, security, terminal, IO and expression handling.</td><td><a href="/documentation/en/framework/core/diagnostics.md">Zongsoft.Diagnostics</a></td></tr></tbody></table>

## When to Read This Section

When you need to understand common types, service abstractions, command models, option configurations, or terminal capabilities in other modules, you should first return to the core class library. Modules such as plugin framework, data engine, and Web basic library will reuse the basic abstraction here.

## Related Resources

* [Zongsoft.Core source code directory](https://github.com/Zongsoft/framework/tree/main/Zongsoft.Core)
* [Zongsoft.Core README](https://github.com/Zongsoft/framework/blob/main/Zongsoft.Core/README.md)
* [Zongsoft.Core NuGet package](https://www.nuget.org/packages/Zongsoft.Core)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zongsoft.com/documentation/en/framework/core.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.