1. 03 8月, 2017 1 次提交
  2. 01 8月, 2017 2 次提交
  3. 16 6月, 2017 1 次提交
    • D
      Accessibility for Inline Rename in the Editor · 86e29d7d
      David Poeschl 提交于
      Fixes
      https://devdiv.visualstudio.com/DevDiv/_workitems?id=391624&_a=edit
      
      - Inline Rename fields now consist of a themeable/customizable
      background, foreground, and border. The border is used in High Contrast.
      - Resolved and Unresolved conflict borders can now be themed &
      customized.
      - Resolved and Unresolved conflict borders now have different dash
      styles so they are distinct from each other and regular Inline Rename
      fields. The Dashboard shows a key indicating which type of conflict
      corresponds to which border dash style.
      86e29d7d
  4. 18 5月, 2017 1 次提交
    • H
      log info for ab testing · 95a7c450
      Heejae Chang 提交于
      state progress as below
      
      1. StartCandidacyRequirementsTracking <- first time user user LB (only once per user)
      2. HasMetCandidacyRequirements <- when requirement is met (only once per user)
      3. AnalyzerEnabledFlight <- when the user accepted as flight group (multiple times until user take action)
      4. InfoBarShown <- when info bar is shown (multiple times until user takes an action)
      
      actions user can take. (this can only happen once)
      1. AnalyzerVsixHyperLine <- user choose to go to the link
      2. NeverShowAgain <- user decide not to participate in the experiment
      
      if user choose to install vsix (this can only happen once - unless user manually reinstall the vsix...)
      1. Installed
      2. Uninstalled
      
      the first time user installed the vsix, we will report these extra info
      1. DocumentDiagnostics - report only once per a document
      2. ProjectDiagnostics - report only once per project
      
      these 2 report include count per errors and FSA status. these only report once and never report again.
      95a7c450
  5. 13 5月, 2017 3 次提交
  6. 11 5月, 2017 1 次提交
  7. 10 5月, 2017 1 次提交
  8. 09 5月, 2017 1 次提交
  9. 04 5月, 2017 1 次提交
  10. 03 5月, 2017 2 次提交
  11. 01 5月, 2017 1 次提交
  12. 30 4月, 2017 1 次提交
  13. 23 4月, 2017 1 次提交
  14. 20 4月, 2017 1 次提交
  15. 18 4月, 2017 1 次提交
  16. 07 4月, 2017 1 次提交
    • K
      Don't create deferred projects for things that opt-out of DPL · 8f1018eb
      Kevin Pilch 提交于
      While investigating #17570, I discovered that we would sometimes create
      "deferred" Roslyn projects for .NET Core projects that just hadn't been
      asynchronously created yet. In *theory* that did no functional harm - they would
      just get closed and converted to real projects when the project system created
      the real project, but might as well not even bother creating them.
      
      While I'm here, clean up PR feedback from #17335.
      8f1018eb
  17. 22 3月, 2017 1 次提交
  18. 15 3月, 2017 1 次提交
  19. 14 3月, 2017 1 次提交
  20. 13 3月, 2017 1 次提交
  21. 09 3月, 2017 1 次提交
  22. 07 3月, 2017 1 次提交
  23. 02 3月, 2017 1 次提交
    • K
      Fix SolutionLoadEvents · fb9577e4
      Kevin Pilch 提交于
      So, it turns out that when you AdviseSolutionEvents, the shell actually
      checks the same object for all of the related solution events interfaces
      to fire events to them. This meant that after commit
      e6a43cb5, we never actually received any
      IVsSolutionLoadEvents or IVsSolutionWorkingFoldersEvents. The impact of
      this is that we never called "FinishLoad" to populate the Roslyn
      workspace with the projects that had been loaded.
      
      Most features would appear to work, as we would load a project and it's
      dependencies when a file was opened, but we would then not load any
      thing that depends on it, so features like Find All References and
      Rename wouldn't work reliably.
      
      Fixes
      https://devdiv.visualstudio.com/DevDiv/_workitems?_a=edit&id=389698.
      fb9577e4
  24. 01 3月, 2017 1 次提交
  25. 24 2月, 2017 1 次提交
    • K
      Move IVsSolutionEvents to VisualStudioWorkspaceImpl · e6a43cb5
      Kevin Pilch 提交于
      In Lightweight solution load, we depend on
      IVsSolutionEvents.OnAfterOpenSolution being called to populate the
      workspace and create projects.  However we were subscribing from
      VisualStudioProjectTracker, which we defer create until a project is
      opened.  This meant we never got the event for the first time a solution
      was opened, and so we failed to populate the workspace.
      e6a43cb5
  26. 23 2月, 2017 1 次提交
  27. 10 2月, 2017 1 次提交
  28. 05 1月, 2017 1 次提交
  29. 31 12月, 2016 4 次提交
  30. 29 12月, 2016 4 次提交