1. 29 4月, 2017 1 次提交
  2. 24 4月, 2017 1 次提交
  3. 23 4月, 2017 6 次提交
  4. 22 4月, 2017 3 次提交
    • J
      Get the tab size from our options instead of from the text buffer directly · f23c0f70
      Jason Malinowski 提交于
      In 2f206670 I changed CodeModel to not open an editor when somebody
      called GetStartPoint(), but it turns out that some paths of
      GetStartPoint() internally called GetTabSize which assumed the text
      was backed by a text buffer. This was the original reason the
      EnsureEditor call was added, but I incorrectly determined that the
      it was no longer needed. Now we just pass our OptionSet from the
      document down and ask that, which will work in all cases.
      f23c0f70
    • C
      2f112131
    • T
      Show diagnostic nodes in multi-targeting projects · 8f4d3ef3
      Tom Meschter 提交于
      Normally a given project will only show a single set of analyzer nodes, and finding those nodes and mapping to their underlying `AnalyzerReference`s is relatively easy.
      
      When a project has multiple target frameworks, however, things get harder. Instead of a one-to-one mapping from projects in hierarchy to projects in the workspace, we have a one-to-many mapping: there will be one Roslyn project **per target framework** per hierarchy project. There are a few pieces to making this work properly:
      
      1. When we have found a hierarchy item for an analyzer we already walk up the hierarchy to find the node for the project. We modify this to also look for the node representing the particular target frameworks (that is, with a "TargetNode" capability), if any, and extract the TargetFrameworkMoniker.
      
      2. The `IHierarchyItemToProjectIdMap` has been updated to take that TargetFrameworkMoniker as an optional argument.
      
      3. When checking the hierarchy associated with each Roslyn project we now extract and compare its TargetFrameworkMoniker, if desired.
      8f4d3ef3
  5. 20 4月, 2017 4 次提交
  6. 14 4月, 2017 1 次提交
  7. 09 4月, 2017 1 次提交
  8. 07 4月, 2017 3 次提交
  9. 04 4月, 2017 1 次提交
  10. 30 3月, 2017 1 次提交
  11. 29 3月, 2017 1 次提交
  12. 23 3月, 2017 1 次提交
  13. 22 3月, 2017 1 次提交
    • J
      Clean up some lifetime state management in AbstractLanguageService · 81d1bc54
      Jason Malinowski 提交于
      This type follows the pattern that we assert in the finalizer that it
      should have been cleaned up. If the type failed to initialize, we would
      throw and crash the process even though the underlying failure is
      already past at that point. I'm not saying we shouldn't crash there,
      but that's a separate decision and we should then target the correct
      place.
      81d1bc54
  14. 19 3月, 2017 2 次提交
  15. 16 3月, 2017 1 次提交
    • K
      Pick the right project for P2P refs in lightweight solution load and cross-targeting. · 75000286
      Kevin Pilch 提交于
      If a project being loaded in lightweight solution load references a CPS project
      that does cross-targeting, we may crash trying to hook up P2P references,
      because we were looking for a single project matching the project file name, and
      language.  In the case of cross-targeting though, we create a project for each
      TFM, and the .Single call would blow up.
      
      To fix this, we now continue looking through projects until we find one with an
      output path that matches our reference.
      
      Fixes #17570.
      75000286
  16. 15 3月, 2017 5 次提交
  17. 14 3月, 2017 1 次提交
  18. 13 3月, 2017 2 次提交
  19. 11 3月, 2017 4 次提交