1. 04 5月, 2017 4 次提交
  2. 03 5月, 2017 2 次提交
  3. 01 5月, 2017 7 次提交
  4. 29 4月, 2017 5 次提交
  5. 24 4月, 2017 1 次提交
  6. 23 4月, 2017 3 次提交
  7. 21 4月, 2017 2 次提交
  8. 20 4月, 2017 2 次提交
  9. 19 4月, 2017 1 次提交
  10. 18 4月, 2017 3 次提交
  11. 17 4月, 2017 1 次提交
  12. 16 4月, 2017 2 次提交
  13. 15 4月, 2017 2 次提交
    • F
      Refactored class names following PR feedback · 773919a2
      Fredric Silberberg 提交于
      773919a2
    • T
      Expose the rule set file path in CommonCommandLineArguments · 716f73eb
      Tom Meschter 提交于
      Currently the `CommonCommandLineParser` handles the `/ruleset` switch by reading the .ruleset file and setting the general and specific diagnostic options. However, it doesn't actually save the file path anywhere. This commit now exposes it through the `CommonCommandLineArguments` type, like any other switch that takes a file path.
      
      This change also corrects a subtle issue. As with other switches that take paths, if the `/ruleset` switch appears more than once the last occurrence should "win", and prior occurences should be ignored. However, the dictionary of specific diagnostic options was shared between processing one `/ruleset` and the next; even though the last one should win you could still end up with settings from the other ones. With this change the set of specific diagnostic options is reset with every `/ruleset` processed, ensuring only the last one has any effect.
      
      Technically this is a breaking change. However, you would have to work pretty hard to pass more than one `/ruleset` switch to the compiler. MSBuild only allows one, at most, so you would have to invoke the compiler directly.
      716f73eb
  14. 14 4月, 2017 3 次提交
  15. 13 4月, 2017 2 次提交