Paul "Code Grump" Turner

Ignored examples don't get executed, so I dropped in a little config switch to enable emitting / omitting code for these examples. I made the default to omit examples with...

The error NU5017 is quite specific, relating to a lack of assemblies or assembly references in a package: https://learn.microsoft.com/en-us/nuget/reference/errors-and-warnings/nu5017 This is _true_ for Roslyn packages and I don't see this...

I think disabling the symbol packing is a good move for now. Maybe even permanently. Progress for now.

Misery: for the NUnit implementation, the existing behaviour is to emit ignored examples: the opposite from the other generators. What should we do, be consistent (with a config switch to...

@gasparnagy We're finally here: a generator that produces C# code for the three supported test frameworks. Would you give me your impression of the code-changes and thoughts on what's next?...

Regarding 32: it's because there's a discrepancy between our current implementations: MSTest and xUnit emit these examples, where the nUnit handling omits them. They're excluded _early_ in the pipeline, too...

Regarding 3: configuration using an additional file can be done. We'd have to include it in the compilation to have Roslyn be able to access its contents. The major downside...

Regarding 9: Those directives are to stop the analyzer being included in the compiled output of the project. Essentially, you only want it as a design/build-time dependency and not as...

Regarding 8: the nullable stuff is only really useful to aid code that is being written as an extension of the class. I noticed that our classes are marked as...

Regarding 13: This was a bug in equality checks involving type hierarchies, a particularly prickly topic I have yet to find an airtight pattern for. With the equality checks fixed,...