Jeroen Vannevel
Jeroen Vannevel
Step away from the pre-C# 6 `string.Format` and use an interpolated string instead. Take note that I'm not entirely sure yet if an interpolated string has all the capabilities `string.Format`...
I've noticed a few tests that use the `allowNewDiagnostics: true` argument when using a Code Fix. I don't think this should be allowed so take a look why I did...
Assigning a lambda inline to an event handler essentially makes sure that it can never be removed from that event handler. [This](http://thebillwagner.com/Blog/Item/2015-10-13-LambdaSyntaxandPerformance) article goes deeper into the subject. An example...
See: http://stackoverflow.com/questions/37436633/why-does-the-il-set-this-value-twice
I have added a few XML-related issues so it is probably interesting to aggregate them together here. I suggest that all new issues concerning XML docs are added here as...
- [ ] ImplementBasicDisposePattern #468 - [ ] DisposeMethodShouldHaveBooleanParameterOverload #469 - [ ] IDisposableDotDisposeIsImplementedCorrectly #470 - [ ] DoNotDefineConfusingDisposeOverloads #471 - [x] ExceptionThrownInDispose #472 - [ ] FinalizableTypeShouldImplementBasicDisposePattern #473 -...
We could check all symbols and see if they are either contained in a `using()` clause or call `x.Dispose()` somewhere.
Now we simply refer to the internal `Rule` property on each analyzer. This isn't acceptable because it means we're never really testing the message that each diagnostic display.
Refers to these lines: https://github.com/VSDiagnostics/VSDiagnostics/blob/develop/VSDiagnostics/VSDiagnostics/VSDiagnostics/Diagnostics/General/NullableToShorthand/NullableToShorthandAnalyzer.cs#L86
Some programmers have the habit of using `if(null == variable)` rather than the more expressive `if(variable == null)`. I think we should make a code fix that automatically puts these...