1. 05 3月, 2020 1 次提交
  2. 03 3月, 2020 1 次提交
    • T
      Remove package name tracking for analyzers loaded from VSIX (#42093) · b6756536
      Tomáš Matoušek 提交于
      The error list includes VSIX name in the tool name displayed in error list for diagnostics from analyzers loaded from VSIX.
      It doesn't seem displaying the package name is worth the extra complexity, especially since
      moving these analyzers to Solution snapshot would require re-implementing this tracking in another way.
      b6756536
  3. 23 1月, 2020 1 次提交
  4. 14 1月, 2020 1 次提交
  5. 12 12月, 2019 1 次提交
  6. 06 12月, 2019 1 次提交
  7. 27 11月, 2019 1 次提交
  8. 13 2月, 2018 1 次提交
  9. 29 4月, 2017 2 次提交
  10. 21 11月, 2016 1 次提交
  11. 11 4月, 2016 1 次提交
  12. 16 10月, 2015 1 次提交
  13. 26 8月, 2015 1 次提交
  14. 05 8月, 2015 1 次提交
    • M
      Implementation for Analyzer driver v2 for IDE analyzer host. · 3298740f
      Manish Vasani 提交于
      Changes include:
      
      1. Enhance CompilationWithAnalyzers to allow computing analyzer diagnostics for a specific tree/span within a compilation and/or for a subset of analyzers. Implementation ensures no duplicate analysis by tracking partial analysis state and caching the reported analyzer diagnostics.
      
      2. Overview of the new APIs added to CompilationWithAnalyzers:
          1. GetAnalyzerSyntaxDiagnostics(tree, analyzers, ct)
              1. Analogous to SyntaxTree.GetDiagnostics(ct)
              2. Gets analyzer diagnostics reported by executing syntax tree actions on the given tree.
          2. GetAnalyzerSemanticDiagnostics(semanticModel, spanOpt, analyzers, ct)
              1. Analogous to SemanticModel.GetDiagnostics(spanOpt, ct)
              2. Gets analyzer diagnostics reported by executing rest of the non-compilation actions on the given tree span.
          3. GetAnalyzerCompilationDiagnostics(analyzers, ct)
              1. Gets rest of the analyzer diagnostics which are reported by either of the following means:
                  1. Compilation actions (and compilation end actions)
                  2. Non-compilation actions reporting diagnostics on different tree: Executing a symbol action on a symbol definition in a tree, can report diagnostic on its partial definition in some other tree.
      
      3. Simplify IDE analyzer driver by switching it to using the new CompilationWithAnalyzers APIs for analyzer diagnostic computation. Both the IDE and compiler drivers now use the compilation event queue model for driving analysis.
      3298740f
  15. 30 6月, 2015 1 次提交
  16. 24 6月, 2015 2 次提交
  17. 11 4月, 2015 1 次提交
    • H
      added error source support · 2e438ae3
      Heejae Chang 提交于
      now, error list will have column (which is off by default) that shows source of each errors in a
      format "assembly name" for analyzers node. and "assembly name" [vsix name] for vsix
      2e438ae3
  18. 01 4月, 2015 1 次提交
  19. 27 2月, 2015 1 次提交