1. 21 7月, 2016 1 次提交
  2. 14 7月, 2016 1 次提交
  3. 13 5月, 2016 1 次提交
    • K
      Get build working with VS "15" again · eea2452c
      Kevin Pilch-Bisson 提交于
      1. Reference a bunch of stuff from Nuget packages instead of VS.
      2. Move to Update 2 versions of packages.
      3. Now that we are using the packages, we're referencing
         Microsoft.VisualStudio.Shell.14.dll instead of .15 again.  This means
         that types that moved to Shell.Immutable.15 are not type forwarders.
         Luckily we didn't need anything from Shell.Immutable.15 in the project
         where it was a problem.
      eea2452c
  4. 20 4月, 2016 2 次提交
  5. 19 4月, 2016 1 次提交
  6. 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
  7. 14 4月, 2016 1 次提交
  8. 12 4月, 2016 2 次提交
  9. 02 4月, 2016 1 次提交
  10. 31 3月, 2016 1 次提交
    • J
      Move to the NuGet packages to pick up Microsoft.Shell.Immutable.14.0 · 253f74ff
      Jason Malinowski 提交于
      This fixes the ability to build with later versions of Visual Studio
      on your machine, since some later versions are incorrectly embedding
      type forwards to assemblies that they shouldn't be. The NuGet package
      includes dependencies of
      
      - Microsoft.VisualStudio.OLE.Interop
      - Microsoft.VisualStudio.Shell.Interop
      - Microsoft.VisualStudio.TextManager.Interop
      - Microsoft.VisualStudio.Shell.Immutable.11.0
      
      automatically, and so I remove those from the project files now too.
      253f74ff
  11. 01 3月, 2016 1 次提交
  12. 26 2月, 2016 1 次提交
  13. 17 2月, 2016 2 次提交
  14. 11 2月, 2016 1 次提交
  15. 22 12月, 2015 1 次提交
  16. 16 12月, 2015 1 次提交
  17. 04 11月, 2015 1 次提交
  18. 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
  19. 16 10月, 2015 1 次提交
  20. 09 10月, 2015 1 次提交
  21. 01 10月, 2015 1 次提交
  22. 19 9月, 2015 1 次提交
  23. 10 9月, 2015 1 次提交
  24. 03 9月, 2015 1 次提交