1. 08 12月, 2017 1 次提交
  2. 06 12月, 2017 2 次提交
    • T
      Fix the XliffTasks version · 12d30655
      Tom Meschter 提交于
      Version `0.2.0-beta-000080` only exists on my local system; we actually want version `0.2.0-beta-000081` which is publicly available.
      12d30655
    • T
      Enable XLF-based localization · 3669d047
      Tom Meschter 提交于
      1. Add the XliffTasks package for all projects.
      2. Automatically update XLF files during build on dev machines.
      3. Opt-in to the .NET Core satellite assembly generation task.
      4. Turn off localization for non-shipping projects by default.
      5. Work around an issue in locale-neutral CTO generation.
      3669d047
  3. 05 12月, 2017 2 次提交
  4. 29 11月, 2017 1 次提交
  5. 22 11月, 2017 2 次提交
  6. 21 11月, 2017 1 次提交
  7. 18 11月, 2017 1 次提交
  8. 17 11月, 2017 2 次提交
  9. 11 11月, 2017 1 次提交
    • A
      Upgrade CoreCLR toolset to work on Windows (#23110) · a55468cc
      Andy Gocke 提交于
      The old package had a bug in RunCsc.cmd that didn't properly
      quote the dotnet path. When the SDK is upgraded to a sufficient
      version by VS, the full dotnet path will be used, which contains
      spaces and fails without proper quoting. This updates us to a package
      which contains almost the same compilers, but includes the fix for
      quoting the dotnet path properly (in PR #23034).
      a55468cc
  10. 02 11月, 2017 3 次提交
  11. 01 11月, 2017 2 次提交
  12. 31 10月, 2017 2 次提交
  13. 30 10月, 2017 1 次提交
  14. 28 10月, 2017 1 次提交
  15. 27 10月, 2017 1 次提交
  16. 24 10月, 2017 1 次提交
  17. 18 10月, 2017 1 次提交
  18. 14 10月, 2017 1 次提交
  19. 11 10月, 2017 2 次提交
  20. 06 10月, 2017 1 次提交
  21. 05 10月, 2017 1 次提交
  22. 19 9月, 2017 2 次提交
  23. 15 9月, 2017 1 次提交
  24. 13 9月, 2017 1 次提交
  25. 09 9月, 2017 1 次提交
  26. 07 9月, 2017 2 次提交
  27. 02 9月, 2017 1 次提交
  28. 01 9月, 2017 2 次提交
    • J
      Fix CoreClr Windows tests · 517114f7
      Jared Parsons 提交于
      517114f7
    • J
      Fix the running of our CoreClr tests on Windows · ef8a3e54
      Jared Parsons 提交于
      This is at least temporarily using `dotnet vstest` to execute the tests.
      That allows us to run the tests but can't do things like generate
      compatible XML files that Jenkins can process.
      
      The new structure of the tests does mean that our Linux / Mac jobs are
      now broken though since we no longer have the deploy project.
      ef8a3e54