1. 24 1月, 2018 1 次提交
    • A
      Fix compiler server on CoreCLR and enable bootstrapping on CoreCLR build (#24239) · c1b61732
      Andy Gocke 提交于
      This PR fixes the CoreCLR compiler server on Windows and changes our bootstrap 
      build to act as a test case. The build was previously failing during pipe ownership verification
      because the required API was not available through reflection. This change
      uses the System.IO.Pipes.AccessControl API to do pipe ownership verification
      instead. However, System.IO.Pipes.AccessControl is operating system dependent 
      and thus ends up in the runtimes subdirectory next to the build task.
      Unfortunately, there is no mechanism for automatic assembly resolution
      of plugin DLLs like MSBuild tasks, so we have to implement something
      similar ourselves. This change hooks assembly resolution and, when we
      see a well-known DLL request, we redirect it to the appropriate path.
      
      Fixes #20900 and #24072
      c1b61732
  2. 20 1月, 2018 1 次提交
    • T
      Add satellite assemblies to Microsoft.NETCore.Compilers · fb3325f6
      Tom Meschter 提交于
      Add satellite assemblies for the Roslyn assemblies that we ship in
      Microsoft.NETCore.Compiler.nupkg. This includes
      Microsoft.CodeAnalysis.dll, Microsoft.CodeAnalysis.CSharp.dll,
      Microsoft.CodeAnalysis.VisualBasic.dll, and
      Microsoft.Build.Tasks.CodeAnalysis.dll.
      
      This increases the resulting .nupkg size from about 8,988KB to about
      12,000KB.
      fb3325f6
  3. 07 12月, 2017 1 次提交
  4. 22 9月, 2017 1 次提交
  5. 15 9月, 2017 1 次提交
  6. 17 6月, 2017 1 次提交
  7. 15 6月, 2017 1 次提交
    • J
      Include Git commit in our NuGet packages · 45ca8bd2
      Jared Parsons 提交于
      This change adds the git commit which produced the NuGet package to the
      description section. This makes it easy to both
      
      - Determine what source is included in a NuGet
      - Determine if a given change is included in our NuGet
      
      Lacking this only way to understand which commit produced a NuGet is to
      download the NuGet, crack open the binary and look at the version we
      embed into the PE. This allows us to see the version on the NuGet page
      itself.
      45ca8bd2
  8. 10 6月, 2017 1 次提交
  9. 09 6月, 2017 1 次提交
  10. 06 6月, 2017 1 次提交
  11. 04 6月, 2017 1 次提交
    • A
      Create a NETCore-targeted Compilers NuGet package (#19190) · 2d36e419
      Andy Gocke 提交于
      Creates a new package, Microsoft.NETCore.Compilers, which contains
      CoreCLR-compatible versions of csc and vbc compiled against the
      netcoreapp1.1 shared framework. This NuGet package can be referenced
      by any C# or VB MSBuild project as long as the `dotnet` command line
      tools and the netcoreapp1.1 framework is installed.
      2d36e419
  12. 17 5月, 2017 1 次提交
  13. 16 5月, 2017 1 次提交
  14. 25 4月, 2017 1 次提交
  15. 22 4月, 2017 1 次提交
    • A
      Create a NETCore-targeted Csc package · 16945df5
      Andy Gocke 提交于
      Creates a new package, Microsoft.NETCore.Csc, which contains a Csc
      binary compiled against the netcoreapp1.1 shared framework. This can be
      installed as a NuGet package and built using the dotnet SDK, as long as
      the netcoreapp1.1 framework is installed.
      
      This change also downgrades a few packages, like
      System.Diagnostics.FileVersionInfo, that were higher than the
      version available in netcoreapp1.1.
      
      # Conflicts:
      #	src/Compilers/VisualBasic/VbcCore/project.json
      #	src/Tools/Source/CompilerGeneratorTools/Source/BoundTreeGenerator/project.json
      #	src/Tools/Source/CompilerGeneratorTools/Source/CSharpSyntaxGenerator/project.json
      16945df5