ColumnWeaver.NET feature reference
ColumnWeaver.NET lets a .NET application reuse one object-to-string transformation engine while client, product, or integration output layouts are defined as separate schemas. The package targets .NET Framework 4.8 and .NET Standard 2.0. The Windows Forms configurator targets .NET Framework 4.8.
Column types
- Property: reads flat or nested properties from an input object.
- Formula: computes values using supported expressions, earlier columns, and configuration variables.
- Conditional: selects a configured true or false value based on a condition.
- Custom function: invokes a named function registered by the consuming application.
- Fixed text: emits a constant label or token.
Shared output controls
Columns can be ordered, enabled or disabled, named or aliased, and assigned a separator override. Shared value handling includes null policies, .NET format strings, casing, trimming, maximum length, prefixes, suffixes, configurable padding, and ordered literal or regular-expression replacement rules. Configurations also support a global separator and typed variables.
Reusable execution and configuration
Create a mutable client when configuration changes should be detected, or create/freeze a precompiled client for a stable schema. ParseMany processes forward-only enumerables incrementally. Configuration validation and JSON/XML serialization APIs are available in the library.
Configurator scope
The Windows Forms configurator edits columns and variables, supports JSON open/save, previews CLR sample objects using the compiled engine, and offers a separate JSON-input test sandbox. XML serialization is supported by the library API, but XML file open/save controls are not exposed in the current configurator. Preserving separator slots for disabled columns is also API-level and has no configurator control.
Performance boundaries
Compilation avoids repeating some schema work, but configured execution is not equivalent to a hand-written formatter. In the published workload-specific benchmarks, hard-coded C# is faster in several single-record cases. Review the full BenchmarkDotNet report and benchmark the intended schema and production workload.
Detailed source-verified inventory
For option semantics, combinations, UI limits, and example configurations, read the detailed feature inventory in the repository. For a client-specific trading output example, see the common questions and linked worked example.