dotweave, from tinyrack, automates assembly-level code injection to alter compiled output during the build. The tool runs as part of your project compilation and applies developer-defined weaving logic to binaries without editing source files. It exposes an API for custom weavers and uses attribute-based targeting to limit scope. Designed for .NET engineers and architects, dotweave suits teams that need precise assembly manipulation with minimal external framework overhead.

What does Dotweave change inside a build pipeline?

Dotweave operates on compiled assemblies, performing bytecode-level edits rather than source transformations. It provides an API that modifies Intermediate Language (IL) in DLLs and EXEs after compilation, enabling injection of cross-cutting code such as logging or validation. Developers create custom weavers that match classes, methods, or attributes and the tool applies those rules to the build output automatically, so the final assembly contains the injected logic without source edits.

How does Dotweave affect build performance and workflows?

The tool is designed to add little build overhead, described as a lightweight alternative to larger weaving frameworks. It integrates with standard Windows development environments and the build pipeline, so the weaving step runs as part of compilation rather than a separate manual pass. That design keeps the weaving process close to existing CI and local builds, limiting workflow disruption while keeping build artifacts consistent with developer expectations.

Is using Dotweave safe for production assemblies?

Dotweave modifies compiled binaries, so scope control matters. Attribute-based targeting and custom weavers let you restrict which types receive edits, reducing accidental changes. Because changes occur at IL level, teams should test woven output in controlled builds and include assembly-level checks in their verification process. The fact that it runs during compilation means woven changes are reproducible from the build configuration rather than applied at runtime.

Do I need IL knowledge or specialist skills to use Dotweave?

Basic scenarios can be simpler, but custom weavers require low-level insight. The tool abstracts some common patterns, yet creating targeted, safe IL transformations calls for a working understanding of .NET IL and assembly structure. Its audience is .NET engineers and architects who are comfortable with build tooling and bytecode concepts; less technical users will depend on prewritten weavers or community modules to avoid mistakes.

A practical choice for developers who inspect and extend their toolchain

Dotweave is a pragmatic option for .NET developers who need automated, build-time assembly weaving while keeping their pipeline transparent. Because the project is hosted on GitHub, teams can review weaver modules before use and adapt them to internal standards. Expect a learning curve for bespoke IL work, but the project suits teams that prefer lightweight, inspectable weaving over heavier frameworks. Recommended.