1. 14 3月, 2020 1 次提交
  2. 25 1月, 2020 2 次提交
  3. 24 1月, 2020 2 次提交
  4. 23 1月, 2020 2 次提交
  5. 12 12月, 2019 1 次提交
  6. 27 9月, 2019 1 次提交
  7. 06 8月, 2019 1 次提交
  8. 30 7月, 2019 1 次提交
  9. 13 6月, 2019 1 次提交
  10. 11 6月, 2019 2 次提交
  11. 21 5月, 2019 1 次提交
  12. 16 5月, 2019 1 次提交
  13. 08 5月, 2019 1 次提交
  14. 15 3月, 2019 4 次提交
  15. 14 12月, 2018 1 次提交
  16. 29 7月, 2018 1 次提交
  17. 26 7月, 2018 1 次提交
  18. 24 2月, 2018 2 次提交
  19. 18 2月, 2018 1 次提交
  20. 17 2月, 2018 1 次提交
  21. 25 1月, 2018 2 次提交
  22. 18 1月, 2018 1 次提交
  23. 01 12月, 2017 1 次提交
  24. 23 8月, 2017 1 次提交
  25. 09 8月, 2017 1 次提交
    • J
      Don't pick a project arbitrarily when navigating to symbols · b1d19282
      Jason Malinowski 提交于
      When we were navigating to a symbol with Go to Definition, we were
      roundtripping the symbol to a symbol key, and then trying to
      reconstitute the symbol by finding a project that had the reference
      and then grabbing that symbol. There are two problems with this
      approach:
      
      1. We might get the symbol for the wrong language, which impacts the
         language we use to generate metadata as source. This fixes
         dotnet/roslyn#16818.
      
      2. We might not even get the right symbol. Assembly identity in this
         case was using display name, which could be the wrong portable
         surface area or wrong version.
      
      The fix is to instead carry along the project ID of the originating
      symbol, and resolve against that.
      b1d19282
  26. 02 8月, 2017 2 次提交
  27. 01 8月, 2017 4 次提交