👁 Image
Rystem.Content.Abstractions 10.0.8

Rystem.Content.Abstractions

Rystem.Content.Abstractions contains the shared content API, the registration builder, and the cross-provider migration service.

It does not implement storage by itself. Real storage arrives through provider packages such as Blob, File Share, SharePoint, or InMemory.

Installation

dotnet add package Rystem.Content.Abstractions

What this package adds

This package defines:

• IContentRepository
• IContentRepositoryBuilder
• ContentRepositoryOptions
• ContentRepositoryResult
• ContentRepositoryDownloadResult
• ContentInformationType
• IContentMigration

At DI level, AddContentRepository() currently registers:

• IContentMigration as Transient

Provider registrations are added later through With...Integration(...) extension methods.

Architecture

The core model is intentionally small:

• IContentRepository is the only storage contract
• AddContentRepository() returns an IContentRepositoryBuilder
• providers register named implementations through the shared factory system
• migrations resolve source and destination repositories from IFactory<IContentRepository>

In the current source tree and tests, named resolution is done with IFactory<IContentRepository>, not an IContentRepositoryFactory abstraction.

Registration API

IContentRepositoryBuilder exposes three registration shapes:

The built-in Blob, File, and SharePoint providers sit on top of WithIntegrationAsync(...). The InMemory provider uses WithIntegration(...) and overrides the lifetime to Singleton.

The provider-specific WithBlobStorageIntegration(...), WithFileStorageIntegration(...), WithSharepointIntegration(...), and WithInMemoryIntegration(...) extensions are defined by the provider packages, not by this package itself.

Minimal setup

var repositories = services.AddContentRepository();

repositories.WithInMemoryIntegration("inmemory");

When you need a provider with async setup:

var repositories = services.AddContentRepository();

await repositories.WithBlobStorageIntegrationAsync(options =>
{
 options.ContainerName = "supertest";
 options.ConnectionString = configuration["ConnectionString:Storage"];
}, "blobstorage");

Consuming named repositories

The content tests resolve repositories like this:

public sealed class ContentService
{
 private readonly IContentRepository _contentRepository;

 public ContentService(IFactory<IContentRepository> factory)
 => _contentRepository = factory.Create("blobstorage");
}

IContentRepository contract

Important caveat: overwrite is part of the shared interface, but not every provider enforces it the same way.

Shared models

ContentRepositoryOptions

var options = new ContentRepositoryOptions
{
 HttpHeaders = new ContentRepositoryHttpHeaders
 {
 ContentType = "image/png",
 CacheControl = "max-age=3600",
 ContentDisposition = "attachment; filename=image.png"
 },
 Metadata = new Dictionary<string, string>
 {
 ["author"] = "alice"
 },
 Tags = new Dictionary<string, string>
 {
 ["version"] = "1"
 }
};

ContentInformationType

Result models

Path and Uri are provider-defined. Do not assume they have identical semantics across Blob, File Share, SharePoint, and InMemory.

Migration service

IContentMigration copies content between named providers.

This example matches the usage style in src/Content/Rystem.Content.Tests/Rystem.Content.UnitTest/Integrations/AllStorageTest.cs.

ContentMigrationResult result = await contentMigration.MigrateAsync(
 sourceName: "inmemory",
 destinationName: "filestorage",
 settings: options =>
 {
 options.Prefix = "Test/Folder1/";
 options.OverwriteIfExists = true;
 options.Predicate = item => item.Path?.Contains("fileName6") != true;
 options.ModifyDestinationPath = path => path.Replace("Folder2", "Folder3");
 });

Available settings:

Migration behavior notes

The current implementation is a straightforward copy loop:

• it resolves both repositories through IFactory<IContentRepository>
• it enumerates source items with ListAsync(..., downloadContent: false, ContentInformationType.None)
• it downloads each matched item with ContentInformationType.All
• it uploads the downloaded bytes plus options to the destination repository

Important caveats from the source:

• NotMigratedPaths exists on ContentMigrationResult, but the current implementation never fills it
• when an upload returns false, the result currently lands in NotContentPaths
• there is no provider-native server-side copy or batching logic

Writing a custom provider

If you want your own backend, implement IContentRepository and register it through the builder.

internal sealed class MyContentRepository : IContentRepository
{
 public IAsyncEnumerable<ContentRepositoryDownloadResult> ListAsync(
 string? prefix = null,
 bool downloadContent = false,
 ContentInformationType informationRetrieve = ContentInformationType.None,
 CancellationToken cancellationToken = default)
 => throw new NotImplementedException();

 public Task<ContentRepositoryDownloadResult?> DownloadAsync(
 string path,
 ContentInformationType informationRetrieve = ContentInformationType.None,
 CancellationToken cancellationToken = default)
 => throw new NotImplementedException();

 public Task<ContentRepositoryResult?> GetPropertiesAsync(
 string path,
 ContentInformationType informationRetrieve = ContentInformationType.All,
 CancellationToken cancellationToken = default)
 => throw new NotImplementedException();

 public ValueTask<bool> UploadAsync(
 string path,
 byte[] data,
 ContentRepositoryOptions? options = null,
 bool overwrite = true,
 CancellationToken cancellationToken = default)
 => throw new NotImplementedException();

 public ValueTask<bool> SetPropertiesAsync(
 string path,
 ContentRepositoryOptions? options = null,
 CancellationToken cancellationToken = default)
 => throw new NotImplementedException();

 public ValueTask<bool> DeleteAsync(string path, CancellationToken cancellationToken = default)
 => throw new NotImplementedException();

 public ValueTask<bool> ExistAsync(string path, CancellationToken cancellationToken = default)
 => throw new NotImplementedException();
}

Then register it:

services
 .AddContentRepository()
 .WithIntegration<MyContentRepository>("custom");

Related packages

• Rystem.Content.Infrastructure.Storage.Blob
• Rystem.Content.Infrastructure.Storage.File
• Rystem.Content.Infrastructure.M365.Sharepoint
• Rystem.Content.Infrastructure.InMemory

Use this package when you want the contract and migration layer; add a provider package when you want real storage.