MBW.Generators

A small collection of Roslyn source generators.

Each generator ships as a single NuGet package containing both the generator
and its attributes. Install the package to get the annotations and run the
generator, or reference it with <PrivateAssets>all</PrivateAssets> if you
only need the attributes.

Generators

Generator	Description
NonTryMethods	Creates non-try wrappers for Try-pattern methods
OverloadGenerator	Generates overloads based on declarative attributes
GeneratorHelpers	Generates allocation-free Roslyn symbol helpers

Here’s a reviewed + extended version of your README snippet. I’ve tightened wording, added a bit of background and practical guidance, and included caveats / tips that future you (or consumers) will appreciate:

Logging

All analyzers in this package share a common, opt-in logger for troubleshooting.
By default, logging is disabled and analyzers are completely silent.

Enabling logging

You can turn it on via .editorconfig in the root of your solution or project:

# Enable/disable (default: false)
mbw_generators_logging_enabled = true

# Optional: override the pipe name (default: MBW.Generators.Log)
mbw_generators_logging_pipeName = MBW.Generators.Log

Once enabled, analyzers will attempt to connect to a named pipe.
The default pipe name is MBW.Generators.Log.

Viewing logs

Start the Tool.LogReader project before making edits in your IDE.
As soon as the analyzers connect, log messages will begin streaming in.

Typical workflow:

1. Launch Tool.LogReader (standalone console project).
2. Open your solution in Visual Studio / Rider / dotnet build.
3. Perform edits or builds — the analyzer will write trace messages into the log reader window.

Notes & caveats

• Best effort only: if the logger cannot connect to the pipe, it silently disables itself for the rest of the session (no retries).
• Zero overhead when off: when mbw_generators_logging_enabled = false (the default), log codepaths are completely skipped.
• Local runs only: this logger is intended for troubleshooting and development. Do not enable it in CI builds unless you explicitly want the output.