earloc

asked the pros over at https://github.com/dotnet/roslyn-sdk/issues/1056

This one here looks promising: https://github.com/dotnet/sdk/issues/20355

https://learn.microsoft.com/en-us/dotnet/csharp/roslyn-sdk/tutorials/how-to-write-csharp-analyzer-code-fix

ground paved, despite being the opposit of this issue: https://github.com/earloc/TypealizR/pull/225

Once set up, quality-gate check should be enabled again to require a minimum code-coverage for PRs.

Closing, as the generated types only contain static-properties, which cannot be extended in a way that actually make sense. Also, using these types should be avoided, as they tend to...

Recently revisited possibilities to support this based on [this discussions](https://github.com/earloc/TypealizR/discussions/78#discussioncomment-4721466) over at #78. > SamplesWithCode.resx ```xml Cheers! Hello '{0}' ``` > SamplesWithCode.Designer.cs ```csharp internal class SamplesWithCode { //other stuff ommited...

Maybe the generated methods need an additional `IFormatProvider`-parameter or any other mechnism to get rid of the dependency on the `internal static global::System.Globalization.CultureInfo Culture`-property from those `*.Designer.cs` files.

think about the following project structure, where all projects have `TypealizR` consumed: - Solution - `Library A` - `Library B` - references `Microsoft.Extensions.DependencyInjection.Abstractions` - `Library C` - references `Library B`...

Most simple solution would probably be to generate said extension-method for all of the above assemblies, which (directly or indirectly) reference `Microsoft.Extensions.DempendencyInjection.Abstractions` within a namespace preventing collisions. In above sample...