1. 31 10月, 2020 1 次提交
  2. 24 10月, 2020 1 次提交
  3. 20 10月, 2020 1 次提交
  4. 14 10月, 2020 1 次提交
  5. 13 10月, 2020 1 次提交
  6. 09 10月, 2020 1 次提交
  7. 08 10月, 2020 1 次提交
  8. 06 10月, 2020 1 次提交
  9. 26 9月, 2020 1 次提交
    • C
      Put generated files to disk: (#47047) · de348c5a
      Chris Sienkiewicz 提交于
      * Put generated files to disk:
      - Add new command line param 'GeneratedFilesOut'
      - Route new param through tasks with defaults
      - Write out generated files when requested to do so
      - Rationalize post generation to avoid uncesseary work
      - Add Tests for targets and emit
      - Add test to track the fact that we can overwrite files on windows in SxS cases
      de348c5a
  10. 22 9月, 2020 3 次提交
  11. 19 9月, 2020 1 次提交
  12. 17 9月, 2020 3 次提交
  13. 12 9月, 2020 1 次提交
  14. 11 9月, 2020 1 次提交
  15. 10 9月, 2020 1 次提交
  16. 03 9月, 2020 1 次提交
    • F
      PR Feedback: · 7ae08971
      Fredric Silberberg 提交于
      * Handle additional cases of Main and ModuleInitializer methods
      * Simplify UnmanagedCallersOnlyAttributeData
      * Reword errors and add additional clarifying error for delegate conversions.
      * Add additional suggested test cases.
      7ae08971
  17. 01 9月, 2020 1 次提交
  18. 31 8月, 2020 1 次提交
  19. 29 8月, 2020 1 次提交
  20. 27 8月, 2020 4 次提交
  21. 26 8月, 2020 1 次提交
  22. 24 8月, 2020 1 次提交
  23. 22 8月, 2020 1 次提交
  24. 21 8月, 2020 3 次提交
    • F
      Correct test errors and add Title entries. · 3b51a616
      Fredric Silberberg 提交于
      3b51a616
    • F
      Warn when using a static class in an interface param or return · 16d7fec0
      Fredric Silberberg 提交于
      The native compiler had a bug here that permitted static classes to be used in parameter or return types for methods defined in an interface. We will now warn about doing this when warning waves are on.
      16d7fec0
    • F
      Initial errors on UnmanagedCallersOnly · db634b01
      Fredric Silberberg 提交于
      We now error when a signature that is not compatible with UnmanagedCallersOnly is used. Specifically, these requirements are:
      * The method must be static.
      * The method must be ordinary, or a local function.
      * The method must use only unmanaged types in its parameters and return type.
      * The set of valid types passed to the `CallConv` property is the same as the set of types considered calling convention modifiers for function pointers.
      db634b01
  25. 19 8月, 2020 2 次提交
  26. 18 8月, 2020 2 次提交
  27. 14 8月, 2020 2 次提交
  28. 10 8月, 2020 1 次提交
    • M
      Add a new command line switch to skip analyzer execution · 3afe7a8d
      Manish Vasani 提交于
      Fixes #40926
      
      This support was added to `Microsoft.CodeAnalysis.targets` (ships with VS) in VS2019 16.5:
      https://docs.microsoft.com/en-us/visualstudio/code-quality/disable-code-analysis?view=vs-2019.
      
      However, the MSBuild property is not respected from 'dotnet' builds where this targets file is not imported (see https://github.com/dotnet/roslyn/issues/40926#issuecomment-574506716 for details).
      
      This change moves the skip analyzers logic down to `Microsoft.Managed.Core.targets` and core compiler layer so it is respected for all builds. As per offline discussions with Jared and Chris, we can no longer skip analyzer execution from MSBuild by removing the "Analyzer" items as these can include source generators, which should never be skipped (at least there are no current scenarios where we want to skip generators). Hence, we are adding a new command line compiler switch `/skipAnalyzers`, optionally followed by a `+` or `-`, to allow skipping analyzers.
      
      I verified the end-to-end functionality works fine by locally building `Microsoft.Net.Compilers.Toolset.Package` NuGet package and referencing it in a project.
      3afe7a8d