Recommended Paths

This page gives opinionated starting points for common application types so new adopters do not have to assemble a package set from scratch.

Use these as small starting sets, not as instructions to install everything at once.

Console App Or Utility Tool

Start with:

1. Configuration

2. Extensions or Utilities

3. Logger File if operational visibility matters

Why this path works:

It gives a small application explicit settings, reusable helpers, and simple local logging without adding unnecessary infrastructure.

Service With Relational Data Access

Start with:

1. Configuration

2. Data Sql

3. Data Contracts

4. Logger and a sink such as Logger File

Then add:

1. Data MsSql only if SQL Server-specific behavior becomes necessary.

Best next read:

1. SQL Data Access Workflow

SQL Server Import Pipeline

Start with:

1. Data FileReader

2. Data Bulk

3. Data MsSql

4. Logger File

Why this path works:

It separates file parsing, schema mapping, upload execution, and diagnostics into clear package boundaries.

Best next read:

1. File Import Workflow

Reporting Or Export Workflow

Start with:

1. Collection Streamers

2. Display Attributes

3. Object Converters

4. Compression when archive output matters

5. Mailer when exported files need delivery

Why this path works:

It keeps export structure, formatting, and delivery concerns modular.

Best next read:

1. Data Export Workflow

Operational Logging Baseline

Start with:

1. Logger

2. Logger File

Then expand to:

1. Logger Mail for alerting by email

2. Logger Web for remote endpoint delivery

Best next read:

1. Logging Setup Workflow

Notification Or Mail Workflow

Start with:

1. Configuration

2. Mailer

3. Collection Streamers when attachments are generated from exported data

Why this path works:

It keeps transport, settings, and attachment generation separate.

Background Processing Or Scheduling

Start with:

1. Scheduler

2. Logger File

3. Configuration

Why this path works:

Recurring jobs are much easier to adopt safely when scheduling, settings, and diagnostics are in place from the start.

Selection Rules

1. Start from the application problem, not the full package catalog.

2. Prefer one workflow path at a time.

3. Add sink or storage-specific packages only after the base workflow is working.

4. Use scenario guides when two or more packages are likely to be adopted together.

What To Read Next

1. Read Choosing Packages if your application type still maps to several possible starting sets.

2. Read Scenario Guides if you want the end-to-end version of one of these paths.

3. Read Compatibility And Support if framework support and dependency shape are still part of the evaluation.