1. 29 2月, 2020 2 次提交
  2. 08 2月, 2020 1 次提交
  3. 23 1月, 2020 1 次提交
  4. 09 1月, 2020 1 次提交
  5. 08 1月, 2020 1 次提交
  6. 03 1月, 2020 2 次提交
  7. 01 1月, 2020 5 次提交
  8. 11 12月, 2019 1 次提交
  9. 07 12月, 2019 1 次提交
  10. 06 12月, 2019 2 次提交
  11. 26 11月, 2019 1 次提交
  12. 23 11月, 2019 1 次提交
  13. 22 11月, 2019 4 次提交
  14. 21 11月, 2019 2 次提交
    • A
      refactoring & bug fixing · 84d81af4
      Allison Chou 提交于
      84d81af4
    • M
      Move to new API for GetSuggestedActions · 342796fd
      Manish Vasani 提交于
      Editor team recently added a new GetSuggestedActions API overload that allows providing a more detailed operation scope message. This PR moves us to that API for Roslyn suggested actions. We now display the name of the executing analyzer/fixer/refactoring when user hits Ctrl + Dot to bring up the light bulb. This should help the users identify the slow extension and help us in improving performance of our analyzers/fixers/refactorings.
      342796fd
  15. 20 11月, 2019 1 次提交
  16. 15 11月, 2019 1 次提交
  17. 09 11月, 2019 1 次提交
  18. 07 11月, 2019 1 次提交
  19. 02 11月, 2019 1 次提交
  20. 24 10月, 2019 3 次提交
  21. 23 10月, 2019 1 次提交
    • M
      Enable logging of informational telemetry for analyzers/fixers/refactorings... · f18d016a
      Manish Vasani 提交于
      Enable logging of informational telemetry for analyzers/fixers/refactorings executed during Ctrl + .
      
      If user enables informational RoslynEventSource telemetry following the steps at https://aka.ms/reportPerf, we log the execution times for each analyzer/fixer/refactorings when computing the code fixes and refactorings to show in the light bulb. This will help us identify slow analyzers/fixers/refactorings that lead to UI delays with "Gathering suggestions" dialog.
      f18d016a
  22. 18 10月, 2019 1 次提交
  23. 04 10月, 2019 1 次提交
  24. 26 9月, 2019 1 次提交
  25. 21 9月, 2019 1 次提交
  26. 20 9月, 2019 1 次提交
  27. 05 9月, 2019 1 次提交