1. 19 5月, 2017 1 次提交
  2. 18 5月, 2017 1 次提交
  3. 17 5月, 2017 1 次提交
  4. 16 5月, 2017 3 次提交
  5. 15 5月, 2017 1 次提交
  6. 13 5月, 2017 11 次提交
  7. 12 5月, 2017 2 次提交
  8. 11 5月, 2017 2 次提交
  9. 10 5月, 2017 2 次提交
  10. 09 5月, 2017 2 次提交
  11. 06 5月, 2017 2 次提交
  12. 05 5月, 2017 4 次提交
    • C
      Remove WriteLine. · cc4852d8
      CyrusNajmabadi 提交于
      cc4852d8
    • C
      Swallow very specific exception messages. · 60a63eb6
      CyrusNajmabadi 提交于
      60a63eb6
    • T
      Fix a small memory leak related to batching project loads · 112afcb7
      Tom Meschter 提交于
      Fixes https://github.com/dotnet/project-system/issues/1918.
      
      The language service implements `IVsSolutionLoadEvents.OnBeforeLoadProjectBatch` and `IVsSolutionLoadEvents.OnAfterLoadProjectBatch` to support asynchronous solution loads. While a batch is in progress we try to avoid pushing added projects to the workspace and instead store them in a list. When the batch is complete we may push all of those projects to the workspace at once.
      
      The current implementation has a memory leak. Project may be added outside of a pair of `OnBeforeLoadProjectBatch`/`OnAfterLoadProjectBatch` calls, and it is possible for projects to be added without those methods ever being called. However, during a solution load adding a project always causes us to put it in the list of batched projects. Since we only clear the list on calls to `OnBeforeLoadProjectBatch` or `OnAfterLoadProjectBatch` the user could close the project or even the whole solution and we could still be holding on to one or more projects and all of their associated memory.
      
      The fix here is to add a `bool` to track whether or not we're batching projects, and only put an added project in the list if we are.
      112afcb7
    • C
      ea6935d6
  13. 04 5月, 2017 3 次提交
  14. 03 5月, 2017 4 次提交
  15. 01 5月, 2017 1 次提交