---
title: .NET Client
---

The .NET client serves as the foundation for most Chronicle clients. Its design philosophy is to
offer a streamlined API for quick onboarding, while also empowering developers with full control
and extensibility. Out of the box, the client provides sensible defaults to help you get started
rapidly, but every default is fully overridable to suit advanced scenarios.

For example, you can instantiate a `ChronicleClient` with just the server `URI` and immediately
begin working. You may use the built-in discovery method to automatically discover all artifacts,
or selectively discover only those you need. If you require custom behavior, you can override the
discovery mechanism entirely by implementing your own `IClientArtifactsProvider`.

This approach ensures an easy entry point for new users, while also supporting advanced
customization for those who need it.

## Packaging

The .NET client uses runtime-only packaging to hide internal implementation details. It includes the [contracts](/chronicle/contributing/kernel/contracts/) and
the `Connection` project as runtime-only assemblies, ensuring they're not exposed in IntelliSense or available for direct compilation by consumers.
See [internalization](/chronicle/contributing/clients/internalization/) for details on how this works.

## Using statements

- Common usings are provided in `GlobalUsings.cs` files, don't add any using statements already in this file.
- Include using statements not covered by any `GlobalUsing.cs` definitions.
- Don't add any `System` using statements.

## Language

- C# does not allow for multiple inheritance.