1. 17 12月, 2016 2 次提交
  2. 10 12月, 2016 1 次提交
  3. 24 9月, 2016 1 次提交
  4. 15 9月, 2016 1 次提交
  5. 05 8月, 2016 1 次提交
  6. 02 8月, 2016 1 次提交
    • J
      Remove many of the dependency projects · 585d3d19
      Jared Parsons 提交于
      The dependency projects serve a few purposes:
      
      - Help ensure package unity by serving as a single place for a NuGet reference.
      - Make NuGet updates simple by having a single place to change.
      - Grouping together related packages to make it easy to take a dependency on say Visual Studio editor.
      
      The first two points are largely obsolete now that our project.json references are strictly validated on every build and have a single update mechanism.  This meant a lot of our depnedency projects were just making Roslyn.sln bigger.
      
      As such I went through and deleted all of them which had only 1 or 2 project.json entries.  I left the VS ones which tend to group 10+ references together.  They are still serving a valid "reference VS" purpose.
      585d3d19
  7. 18 5月, 2016 1 次提交
  8. 21 4月, 2016 3 次提交
  9. 20 4月, 2016 3 次提交
  10. 16 4月, 2016 1 次提交
    • D
      Unify NuGet dependencies across the tree · 4aef0b06
      David Kean 提交于
      To prevent projects across the tree from having different dependencies, we unify
      external package dependencies by creating empty C# projects that represent them.
      We then make use of project.json package inheritance (where a project inherits
      all packages dependencies from their dependencies) to unify it across the tree.
      
      No projects outside of this tree, should be directly referencing versions of
      these dependencies manually.
      
      For this check-in I've tackled Metadata, Reflection, and DiaSymReader. Will tackle
      the rest in future commits.
      4aef0b06
  11. 14 4月, 2016 1 次提交
  12. 12 4月, 2016 2 次提交
  13. 10 3月, 2016 2 次提交
  14. 27 2月, 2016 1 次提交
  15. 17 2月, 2016 2 次提交
  16. 12 2月, 2016 1 次提交
  17. 11 2月, 2016 1 次提交
  18. 05 2月, 2016 1 次提交
  19. 23 1月, 2016 1 次提交
  20. 11 1月, 2016 1 次提交
  21. 22 12月, 2015 1 次提交
  22. 16 12月, 2015 1 次提交
  23. 22 11月, 2015 1 次提交
  24. 04 11月, 2015 1 次提交
  25. 28 10月, 2015 1 次提交
  26. 24 10月, 2015 1 次提交
    • J
      Update project.jsons to support building with Update 1. · 42526f58
      Jason Malinowski 提交于
      With Visual Studio 2015 Update 1 you should not specify -anycpu
      in the runtimes section. Right now we'll have both to allow us to build
      with and without Update 1, and we'll remove the old ones once we've
      made the transition.
      
      Update 1 also tries deploying implementations for some class libraries,
      so I'm updating all our test and VSIX deployment class libraries to
      now include implementations.
      42526f58
  27. 18 10月, 2015 2 次提交
  28. 16 10月, 2015 1 次提交
  29. 14 10月, 2015 1 次提交
  30. 13 10月, 2015 1 次提交
  31. 10 10月, 2015 1 次提交