Mikkel Nylander Bundgaard
Mikkel Nylander Bundgaard
I'm not sure how much Prefiltering is being used, but I'm agreeing with you as I fear that we also have this kind of check in other areas of the...
Personally, I don't think we should change anything and just accept that this is how it is (meaning how VS shows unhandled exceptions) and then close the issue (we have...
Closed due to inactivity
@manfred-brands suggestion sounds good to me. Also note that EditorBrowsable has been broken for some time - see dotnet/roslyn#4434 - and still are as far as I know
I guess we need to add some logic to `ClassicModelAssertUsageCodeFix`, so it will use `NameColon` if it is supplied, then this will also fix the same issue in other codefixes...
Closed as answered
@payn-git Just to be sure I understand, but you mean something like this dotnet/roslyn-analyzers#1718 that provides a lot of rulesets? 
@lucasteles I've transferred the issue to the nunit.analyzers repository. Can you give an example of this problem - just for more context as I don't know much about FsCheck? Preferably...
Sorry about overlooking the last comments - I guess I lost track of them in a busy period. I've taken a closer look at FsCheck, the NUnit ITestBuilder vs ISimpleTestBuilder,...
As far as I have understod `SetUpFixture` are also considered a kind of test (at least they are part of the test hierarchy like a parent), so the following code...