1. 10 3月, 2016 2 次提交
  2. 08 3月, 2016 2 次提交
  3. 05 3月, 2016 2 次提交
  4. 03 3月, 2016 1 次提交
  5. 02 3月, 2016 2 次提交
  6. 01 3月, 2016 8 次提交
  7. 27 2月, 2016 5 次提交
    • A
      PR comments · bd3dfede
      Andy Gocke 提交于
      bd3dfede
    • A
      Always use an absolute path for keyfile with public sign · 67a9fd89
      Andy Gocke 提交于
      Right now there are two code paths for signing using a keyfile:
      
      1) Full & delay signing implemented using a strong-name provider, which
         calls into the CLR when necessary to do signing.
      2) Public signing, which extracts the key directly from the file and
         embeds it manually into the assembly using only portable code.
      
      The tricky part is that (1) also implements a bunch of legacy semantics
      on how to resolve the key file from various search paths, since the key
      file can also be specified via an attribute.
      
      This behavior is already deprecated, so rather than implement the
      complicated file resolution for public sign as well, this PR changes the
      command line compilers to always produce an absolute path for the key
      file before passing it to CompilationOptions. CreateCompilation now also
      has a check to enforce that CryptoKeyFile is an absolute path when
      PublicSign is set.
      
      Fixes #8360.
      67a9fd89
    • T
    • T
      lock files · edcbe448
      Tomas Matousek 提交于
      edcbe448
    • T
      46a2b9ed
  8. 25 2月, 2016 6 次提交
  9. 24 2月, 2016 3 次提交
  10. 23 2月, 2016 3 次提交
  11. 20 2月, 2016 4 次提交
  12. 19 2月, 2016 2 次提交