Package Catalog

This page is the broad map of the VersaTul library ecosystem.

Use it after you already know the problem area you are working in and want to discover adjacent packages, not as the first step for adoption.

If you are new to the ecosystem, start with Getting Started or Choosing Packages before using this page as a jump table.

How To Use This Page

  1. Find the package family closest to your current problem.

  2. Open the package page with the narrowest scope that can solve it.

  3. Use the relationship notes to identify the next companion package only if needed.

Good times to use the catalog:

  1. You already know you need data access and want to compare the available data packages.

  2. You already use one VersaTul package and want to see what pairs naturally with it.

  3. You want a full ecosystem map after finishing a quickstart or an initial evaluation.

Foundation Packages

These packages provide shared abstractions, configuration support, helpers, and reusable building blocks.

  1. Contracts for shared interfaces used throughout the ecosystem.

  2. Configuration for application setting access and configuration lookup.

  3. Configuration Defaults for standard default settings used by VersaTul packages.

  4. Object Converters for object-to-dictionary and related conversion workflows.

  5. Extensions for common extension methods.

  6. Utilities for general-purpose helper functionality.

Data And Storage Packages

These packages focus on querying, repository patterns, copying data, reading files, and caching.

  1. Caching for in-memory caching abstractions and implementations.

  2. Data Contracts for database-oriented contracts and shared data abstractions.

  3. Data Bulk for bulk data movement scenarios.

  4. Data Sql for provider-based relational data access built on common ADO.NET abstractions.

  5. Data MsSql for Microsoft SQL Server-specific data access and bulk-copy support.

  6. Data MongoDB for repository-style MongoDB access.

  7. EFCore for reusable EF Core repository patterns.

  8. Data FileReader for reading CSV and text files as IDataReader sources.

File, Processing, And Transformation Packages

These packages help when your workflow involves export, formatting, compression, file access, or multi-step processing.

  1. Compression for stream compression and decompression.

  2. Collection Streamers for exporting collections to output formats such as CSV, tab-delimited text, or JSON.

  3. Display Attributes for metadata-driven output formatting.

  4. Handler File for file-system operations and disk-based workflows.

  5. Pipeline Infrastructure for composing filter and transformation pipelines.

Operational Packages

These packages support logging, message delivery, and scheduled execution.

  1. Logger for shared logging contracts and core behavior.

  2. Logger File for file-based logging.

  3. Logger Mail for email-based logging.

  4. Logger Web for endpoint or web-based logging.

  5. Mailer for SMTP-based email sending.

  6. Scheduler for recurring and event-driven scheduling workflows.

Relationship Highlights

Some packages are most valuable when understood together.

  1. Logger, Logger File, Logger Mail, and Logger Web form a shared logging stack.

  2. Configuration and Configuration Defaults usually appear together in application setup.

  3. Collection Streamers, Display Attributes, and Object Converters complement each other in export scenarios.

  4. Data FileReader and Data Bulk fit naturally in import and migration workflows.

  5. Contracts and Data Contracts define extension points reused by multiple concrete packages.