In this post I describe the recent architectural changes to the NetEscapades.EnumGenerators package, which is now a metapackage, to support more scenarios

Andrew Lock's blog focuses on ASP.NET Core development, web APIs, and software architecture. Readers can find tutorials, code samples, and explanations covering topics such as RESTful API design, authentication, and authorization in ASP.NET Core. Additionally, they can learn about dependency injection, middleware, and performance optimization techniques.

.NET Escapades

NetEscapades.EnumGenerators, a .NET source generator that produces fast enum extension methods, has been restructured into three packages ahead of a stable 1.0.0 release. The change was triggered by a breaking issue: users who set PrivateAssets=all and ExcludeAssets=runtime on the package reference (a common pattern for library authors) started getting CS0012 errors after new EnumParseOptions and SerializationOptions types were added to the attributes DLL. The solution splits the package into a metapackage (NetEscapades.EnumGenerators), a generator-only package (NetEscapades.EnumGenerators.Generators), and a runtime dependencies package (NetEscapades.EnumGenerators.RuntimeDependencies). If the runtime dependencies package is absent, the generator emits nested type versions of the options types instead, avoiding transitive dependency requirements at the cost of more verbose API usage. The post also outlines open questions around analyzer defaults, nested type visibility, and API overload ambiguity that need resolving before the 1.0.0 release.

Splitting the NetEscapades.EnumGenerators packages: the road to a stable release

Why should you use an enum source generator?

Adding new features by adding to the marker attribute dll