1. 31 12月, 2016 1 次提交
  2. 29 12月, 2016 3 次提交
  3. 28 12月, 2016 1 次提交
  4. 10 12月, 2016 2 次提交
  5. 11 11月, 2016 1 次提交
  6. 10 11月, 2016 2 次提交
  7. 08 11月, 2016 1 次提交
  8. 05 11月, 2016 1 次提交
  9. 04 11月, 2016 4 次提交
  10. 02 11月, 2016 1 次提交
  11. 31 10月, 2016 1 次提交
  12. 28 10月, 2016 1 次提交
  13. 22 10月, 2016 1 次提交
    • J
      TLDR: artifacts are going to move around in Binaries\Debug and the directory... · b9ba3e9e
      Jared Parsons 提交于
      TLDR: artifacts are going to move around in Binaries\Debug and the directory is going to get a lot bigger.
      
      At a high level build projects can be classified into three categories based on how they write output:
      
      - incorrect: a given output path is written to more than once with different contents
      - less correct: a given output path is written to more than once but always with the same content
      - correct: a given output path is written to exactly once
      
      Today the roslyn build is decidedly “incorrect” as pretty much every file is written directly into Binaries\Debug. This means it ends up writing pretty much every Visual Studio SDK DLL twice: once for Dev14 and once for Dev15. For example at various points in the build Binaries\Debug\Microsoft.VisualStudio.Text.Data.dll may refer to Dev14 and at others it’s Dev15. If this seems like a scary proposition for a build that’s because it is indeed scary and it has real consequences. By now pretty much everyone on the team has hit the build race condition that is dragging down our PRs.
      
      The general fix here is to move build outputs into separate directories. Instead of building to $(Configuration) projects now build into say $(Configuration)\Exes\$(MSBuildProjectFileName). This will have a substantial increase in the size of Binaries. We will be looking into ways to reduce that. In the short term though build stability far outweighs the size increase.
      
      This change takes us most of the way to "correct". There are several places I had to compromise in order to get this initial change in:
      
      - UnitTests still build to a common output folder (one for Dev14, another for Dev15). Pulling unit tests apart is going to take a bit of work.
      - Every project has a <RoslynProjectType> entry. This will go away in the future for most projects. It's temporarily needed so I can fix roslyn-internal in parallel without taking down the build.
      - VSL.Imports.targets is messy. Unavoidable for now due to the above. It will get cleaner as I iterate on this.
      
      None of these are relevant to the underlying race condition. Hence it's okay to push them off.
      b9ba3e9e
  14. 17 8月, 2016 1 次提交
    • J
      Remove ImportGroup · 9f431374
      Jared Parsons 提交于
      The ImportGroup element is just noise.  It was also used very inconsistently in the repo and often within the same project file.  Just remove it.
      9f431374
  15. 05 8月, 2016 1 次提交
  16. 02 8月, 2016 1 次提交
    • J
      Remove many of the dependency projects · 585d3d19
      Jared Parsons 提交于
      The dependency projects serve a few purposes:
      
      - Help ensure package unity by serving as a single place for a NuGet reference.
      - Make NuGet updates simple by having a single place to change.
      - Grouping together related packages to make it easy to take a dependency on say Visual Studio editor.
      
      The first two points are largely obsolete now that our project.json references are strictly validated on every build and have a single update mechanism.  This meant a lot of our depnedency projects were just making Roslyn.sln bigger.
      
      As such I went through and deleted all of them which had only 1 or 2 project.json entries.  I left the VS ones which tend to group 10+ references together.  They are still serving a valid "reference VS" purpose.
      585d3d19
  17. 30 7月, 2016 1 次提交
    • H
      porting OOP to preview 4 branch · c141605a
      Heejae Chang 提交于
      changes include
      make SourceText::GetChecksum and AnalyzerTelemetry contructor public.
      
      added MustRunInProc in IBuiltInAnalyzer and some clean up around serializing Solution/Project/DocumentId and how DocumentState is exposed.
      
      simplified temporary storage service's temporary storage management and added ability to attach to existing temporary storage
      
      solution checksum and serialization service.
      
      added remote host client
      - this gives an ability for host (vs) to talk to remote host (service hub)
      
      rename and moving files between feature/workspace layers
      - only real change is having ICompilerDiagnosticAnalyzer interface which can either have inproc implementation or out of proc implementation.
      - inproc is needed since diagnostics are in feature layer and one who uses feature layer out side of VS host need an implementation.
      
      added RemoteWorkspace
      - RemoteWorkspace has host agnostic implementation of roslyn features/services/workspace that will run in remote host
      
      added service hub component and setup project for service hub
      - service hub component is basically thin layer that deals with converting data to pass in to RemoteWorkspace
      
      made devdiv insertion tool to ignore servicehub related files
      
      support byte and char array natively in ObjectReader/Writer
      c141605a
  18. 27 7月, 2016 1 次提交
  19. 21 7月, 2016 1 次提交
    • M
      Enable building and (some) testing on machines with only Dev15 Preview 3 installed (#12586) · 6ba2346b
      Manish Vasani 提交于
      * Enable building and testing on machines with only Dev15 Preview 3 installed
      
      1. Auto-detect the VS common tools path
      2. Convert analyzer samples to import Roslyn targets
      3. Ensure dependencies are copied to the output directory
      4. Workaround: Use local Microsoft.Net.Compilers.props until we move to a compiler toolset with https://github.com/dotnet/roslyn/commit/05c12ebfcdd08a02dbceded5327a8da7a7df23be
      5. Replace references to Microsoft.VisualStudio.ComponentModelHost.dll (VisualStudioReferenceAssemblyVersion) with a nuget reference to RoslynDependencies.Microsoft.VisualStudio.ComponentModelHost
      6. Add nuget references to Roslyn.Microsoft.Build, Roslyn.Microsoft.VisualStudio.ExtensionManager, RoslynDependencies.Microsoft.VisualStudio.Diagnostics.PerformanceProvider and RoslynDependencies.Microsoft.VisualStudio.CodeAnalysis.Sdk.UI.
      
      * Remove workaround now that new NuGet packages have been uploaded to nuget.org
      
      * Remove preprocessor directive MSBUILD12 and its references
      6ba2346b
  20. 30 6月, 2016 1 次提交
  21. 24 6月, 2016 1 次提交
  22. 26 5月, 2016 1 次提交
  23. 21 5月, 2016 1 次提交
    • M
      Move Roslyn to newer toolset packages (#10312) · 40e2a0c8
      Manish Vasani 提交于
      * Move Roslyn to newer toolset packages
      
      1. Move to 1.2.1 compiler toolset package.
      2. Move to 1.2.0-beta1 analyzer packages.
      3. Turn on IOperation feature flag for all projects as the new analyzer packages have IOperation based analyzers.
      
      * Use the Roslyn wide default CA rulesets for newly added samples project.
      
      * Fix couple of test projects to use the Roslyn wide rulesets for code analysis.
      
      * Move to analyzers 1.2.0-beta2 packages (multiple fixes and enhancements to Roslyn diagnostic analyzers)
      
      * Revert accidental file mode changes.
      
      * Move shipped implicit constructors to public API shipped files.
      
      Fixes #11446
      40e2a0c8
  24. 13 5月, 2016 1 次提交
  25. 30 4月, 2016 1 次提交
  26. 21 4月, 2016 2 次提交
  27. 20 4月, 2016 2 次提交
  28. 29 3月, 2016 1 次提交
  29. 02 3月, 2016 1 次提交
  30. 24 2月, 2016 1 次提交
  31. 20 1月, 2016 1 次提交