1. 24 6月, 2016 1 次提交
  2. 23 6月, 2016 1 次提交
  3. 22 6月, 2016 1 次提交
  4. 06 6月, 2016 1 次提交
  5. 02 6月, 2016 2 次提交
    • T
      Compilation: use System.Object from target corlib (#8507) (#11708) · 0d0d8677
      Tomáš Matoušek 提交于
      * Tests: fix minasync Task<T> to derive from Task
      
      * Tests: provide MinAsyncCorlibRef
      
      This combines the async features of minasync with mincorlib to produce
      a minimum unversioned corlib with async stubs.
      
      * Compilation: use System.Object from target corlib
      
      When creating a script compilation without an explicit return type,
      System.Object was being resolved via reflection from the host.
      
      This resulted in an implicit dependency of a script compilation on the
      host corlib, even if a different corlib was specified as a reference
      for the compilation (e.g. Xamarin.iOS).
      
      Fix this by using System.Object as defined in the corlib resovled
      for the compilation.
      0d0d8677
    • A
      Compilation: use System.Object from target corlib (#8507) · c0738262
      Aaron Bockover 提交于
      * Tests: fix minasync Task<T> to derive from Task
      
      * Tests: provide MinAsyncCorlibRef
      
      This combines the async features of minasync with mincorlib to produce
      a minimum unversioned corlib with async stubs.
      
      * Compilation: use System.Object from target corlib
      
      When creating a script compilation without an explicit return type,
      System.Object was being resolved via reflection from the host.
      
      This resulted in an implicit dependency of a script compilation on the
      host corlib, even if a different corlib was specified as a reference
      for the compilation (e.g. Xamarin.iOS).
      
      Fix this by using System.Object as defined in the corlib resovled
      for the compilation.
      c0738262
  6. 21 5月, 2016 3 次提交
  7. 28 4月, 2016 2 次提交
  8. 22 4月, 2016 1 次提交
  9. 21 4月, 2016 2 次提交
  10. 20 4月, 2016 1 次提交
  11. 16 4月, 2016 1 次提交
  12. 07 4月, 2016 1 次提交
  13. 02 4月, 2016 1 次提交
  14. 29 3月, 2016 1 次提交
  15. 17 3月, 2016 1 次提交
  16. 09 3月, 2016 2 次提交
  17. 05 3月, 2016 1 次提交
  18. 03 3月, 2016 1 次提交
  19. 01 3月, 2016 1 次提交
  20. 25 2月, 2016 1 次提交
  21. 14 11月, 2015 1 次提交
    • A
      Add support for public sign to csc · ca61bad2
      Andy Gocke 提交于
      Sometimes called "fake sign" or "OSS sign" public signing is including
      the public key in an output assembly and setting the "signed" flag, but
      not actually signing the assembly with a private key. This is useful for
      open source projects where people want to build assemblies which are
      compatible with the released "fully signed" assemblies, but don't have
      access to the private key used to sign the assemblies. Since almost no
      consumers actually need to check if the assembly is fully signed, these
      publicly built assemblies are useable in almost every scenario that the
      fully signed one would be used in.
      
      This PR implements support only for C# -- VB will be added soon. If
      being used at the command line, the /publicsign flag can be passed to
      csc and the /keyfile flag can specify the public key. Unlike fully
      signing, a full key pair encoded in the SNK file format is not currently
      supported. When using /publicsign, just the public key must be in the
      /keyfile file.
      
      When using the API, the public key can be passed directly using the
      CryptoPublicKey CompilationOption.
      ca61bad2
  22. 04 11月, 2015 1 次提交
  23. 31 10月, 2015 1 次提交
  24. 27 10月, 2015 1 次提交
  25. 20 10月, 2015 1 次提交
  26. 16 10月, 2015 1 次提交
  27. 14 10月, 2015 1 次提交
  28. 07 10月, 2015 1 次提交
  29. 30 9月, 2015 1 次提交
  30. 25 9月, 2015 1 次提交
  31. 17 9月, 2015 1 次提交
    • M
      Add a new CompilationOption "ReportSuppressedDiagnostics" to enable reporting... · 18aabe22
      Manish Vasani 提交于
      Add a new CompilationOption "ReportSuppressedDiagnostics" to enable reporting compiler diagnostics suppressed in source. Note that the command line compilers will report such suppressed diagnostics in the SARIF errorlog file but not on the console output.
      
      This new compilation option was approved by the design team.
      
      Fixes #5216
      18aabe22
  32. 15 9月, 2015 1 次提交
  33. 11 9月, 2015 2 次提交
    • M
      Emit "isSuppressedInSource" boolean property for diagnostics in the ErrorLog... · a3b4dd49
      Manish Vasani 提交于
      Emit "isSuppressedInSource" boolean property for diagnostics in the ErrorLog file and report suppressed analyzer diagnostics in the error log.
      a3b4dd49
    • M
      Initial work for "Disconnected baselining" scenario: · 08b9efdc
      Manish Vasani 提交于
      1. CompilationWithAnalyzers can now report analyzer diagnostics with source suppressions (pragma/SuppressMessageAttribute). This will eventually allow us to surface diagnostics with source suppressions in the error list. Note that the behavior of command line compilers and all the GetDiagnostics APIs is unchanged, only the compiler analyzer will report diagnostics with source suppressions.
      
      2. Add FixAll support for Suppression code fixes. Light bulb suppression fixes now show the "Fix all occurrences" options for Document/Project/Solution. This change adds the basic functionality to bulk suppress diagnostics. This will eventually be consumed for baselining all/selected diagnostics from error list/solution explorer.
      
      3. Simplify the Suppression light bulb menu to remove the option to add a local SuppressMessageAttribute. The only options now are to suppress in source (pragma) or suppressions file (assembly level SuppressMessageAttribute).
      08b9efdc