How linlccc/easy works
Project type and purpose
• This is an open-source .NET “Easy” monorepo containing:
• A suite of framework libraries (Easy.Common, Easy.Extensions, DI abstractions & implementation, DynamicProxy)
• Two CLI/tools (IgnoreAccessChecks, MergeJson)
• MSBuild import/automation scripts (easyMSBuildImport)
• Tests and documentation for each component
• Its goal is to provide common utilities, extension methods, DI enhancements, dynamic proxy support, and build‐time tools.
File structure
• Top-level folders/files:
• easyMSBuildImport/… → custom MSBuild props & targets to auto-import and publish NuGet packages
• framework/… → each subdirectory is either a library or a tool (with src/ and tests/)
• readmes/… → markdown docs per component
• nuget.exe → CLI helper for listing packages
• Each framework/Easy.* subfolder contains a .sln, a src project, and tests → indicating per-component micro-library architecture
• Tools under framework/Easy.Tool.* follow the same pattern with src/build files and tests
README for additional insights
• The root README provides a high-level index of “架构” (framework extensions, DI abstractions, etc.) and “工具” (Json merge tool, ignore-access tool)
• It describes publishing tasks via MSBuild targets
a. Main components
• Build automation layer (easyMSBuildImport + Directory.Build.props/targets)
• Core utilities library (Easy.Common)
• Extension libraries (Easy.Extensions)
• DI abstraction library (Easy.Extensions.DependencyInjection.Abstractions)
• DI implementation library (Easy.Extensions.DependencyInjection)
• Dynamic proxy engine (Easy.Extensions.DynamicProxy)
• Tools:
– Easy.Tool.MergeJson
– Easy.Tool.IgnoresAccessChecks
• Test projects (per library/tool)
• Documentation site (readmes)
b. Relationships and interactions
• easyMSBuildImport → loaded by all projects at build time → automates package versioning & publishing
• Easy.Extensions depends on Easy.Common
• DI implementation depends on both DI.Abstractions and Easy.Common
• DynamicProxy may be used by DI implementation for AOP scenarios
• Tools reference none of the above libraries at runtime but each has its own build props/targets from easyMSBuildImport
• Test projects reference their corresponding src projects
c. Architectural patterns and principles
• Modular monorepo: each library/tool is isolated with its own solution, source, and tests
• Convention-based MSBuild extension: all projects share props/targets in easyMSBuildImport
• Dependency Injection pattern: clear separation of abstractions vs implementations
• Aspect-Oriented Programming with DynamicProxy
d. Key technologies
• .NET SDK-style projects, C#
• MSBuild Props & Targets customization
• NuGet packaging and publishing
• Reflection.Emit for proxy generation
• JSON merging via custom CLI tool
Final advice
• Modules and their inter-dependencies without over-splitting
• Both build-time (easyMSBuildImport) and run-time flows (library references, tool inputs/outputs)