VersaTul Documentation
VersaTul is a collection of focused .NET libraries for common application work such as configuration, data access, import and export flows, logging, mail delivery, and scheduled processing.
It is designed for teams that want reusable building blocks without committing to one large framework. You can start with a single NuGet package for one concrete problem and add adjacent packages only when you need them.
If you are evaluating the library for the first time, the fastest path is:
Pick the developer job you need to solve.
Start with one package or one small package combination.
Follow a short quickstart or scenario path.
Expand into the package reference only after the first workflow is working.
Start By Problem
Use these paths if you want the quickest route to a relevant package.
I need strongly typed application settings: start with Getting Started.
I need relational data access: start with SQL Data Access Workflow.
I need to import CSV or text data: start with File Import Workflow.
I need export or formatting helpers: start with Data Export Workflow.
I need logging in a service or background process: start with Logging Setup Workflow.
I need a package starting set for my application type: start with Recommended Paths.
Start In 5 Minutes
If you want a fast first win, start with the onboarding path instead of browsing the full catalog.
Read Getting Started for a copy-paste configuration quickstart.
Read Choosing Packages for an intent-first guide to the package ecosystem.
Use Scenario Guides for end-to-end workflows that combine multiple packages.
Use Package Catalog after you know the workflow or package family you want.
Adoption FAQ
Common evaluation answers:
Start with one package, not the whole ecosystem.
Prefer Data Sql when provider flexibility matters and Data MsSql when SQL Server-specific behavior is the real requirement.
Use Logger with a sink package such as Logger File; the base logger package is not a sink by itself.
Use Recommended Paths if you want a package starting set by app type.
Use FAQ if you want the broader adoption and selection guidance in one place.
What To Read Next
Read Getting Started if you want the smallest copy-paste success case first.
Read Recommended Paths if you already know your application shape.
Read Scenario Guides if your main question is how packages combine in a real workflow.
Read Choosing Packages if you still need help narrowing the first package family.
Popular Workflows
These are the highest-value package combinations for first-time adopters.
Configuration bootstrap: start with Getting Started and then add
VersaTul.Configuration.Defaults.SQL-backed service: follow SQL Data Access Workflow.
File import pipeline: follow File Import Workflow.
Export pipeline: follow Data Export Workflow.
Logging setup: follow Logging Setup Workflow.
How VersaTul Is Organized
The ecosystem is organized as focused NuGet packages that can be used independently or combined to build larger solutions. Across the library set you will find support for:
Foundational application building blocks such as contracts, configuration, utilities, and object conversion.
Data access and data movement including SQL, SQL Server, MongoDB, EF Core, bulk copy, file readers, and caching.
File, transformation, and processing workflows including compression, streamers, file handling, display metadata, and pipelines.
Operational concerns such as logging, mail delivery, and task scheduling.
Note
These docs focus on the NuGet-distributed VersaTul library packages.