1. 18 4月, 2015 1 次提交
  2. 17 4月, 2015 1 次提交
  3. 07 3月, 2015 2 次提交
  4. 14 1月, 2015 1 次提交
  5. 07 1月, 2015 1 次提交
  6. 24 12月, 2014 2 次提交
    • A
      Simplify updating LKG compiler & analyzers by introducing "global" NuGet references · 9ee65cac
      angocke 提交于
      This changeset introduces the concept of a "global" nuget package. The references to the NuGet packages are inserted into the Open VSL.Settings.targets file, which is imported into every project in Roslyn. This ensures that every project automatically gets these "global" packages. (changeset 1386548)
      9ee65cac
    • T
      Updates System.Collections.Immutable and System.Metadata.Reader to versions... · e8be04b7
      TomasMatousek 提交于
      Updates System.Collections.Immutable and System.Metadata.Reader to versions 1.1.33-beta and 1.0.18-beta, respectively.
           Updates VSMEF to the latest build from VSPRO_1.
      
           A few code fixes:
           - ImmutableArrayInterop is gone
             - in product we used in a couple of places where we now just create a copy of the byte[] (MetadataWriter)
             - test infrastructure uses a workaround with explicitly laid out union to avoid copies of large metadata blobs
           - EditorTestApp class was incorrectly importing MEF components resulting in a cycle. The new VSMEF reports such errors. (changeset 1385613)
      e8be04b7
  7. 17 10月, 2014 1 次提交
  8. 16 10月, 2014 1 次提交
  9. 11 10月, 2014 1 次提交
    • T
      Remove duplicate package references. · 8fef5b5d
      tmeschter 提交于
      When our projects were last updated to a newer version of Microsoft.Net.ToolsetCompilers, NuGet didn't replace the old version--it just put the new version next to it. Every project ended up referencing both versions, and which set of compiler binaries "won" depended on the order they appeared in the project file. So different projects built with different compilers.
      
      This change strips out all references to the old version. (changeset 1352054)
      8fef5b5d
  10. 10 10月, 2014 1 次提交
  11. 07 10月, 2014 1 次提交
    • J
      Make much of the Workspaces layer Portable. · e76a29a4
      jasonmalinowski 提交于
      This change splits the Workspaces layer into two parts, mirroring the Portable/Desktop split that the compilers did. The core parts of the Workspaces layer (managing documents and projects, formatting, some refactoring, code fixes) is kept in the portable subset, with a few non-portable pieces remaining, notably MSBuild support.
      
      This change has a major impact on how MEF now works in Roslyn. Traditional MEF (“MEFv1”) is not portable, and so we must move the Workspaces layer over to using the Microsoft.Composition NuGet package (“MEFv2”) which is. The APIs are distinct in that each has its own namespace, but the concepts are more or less identical. It requires some care though: the workspaces layer is simple in that it only references MEFv2, but higher layers have to reference both versions to use metadata attributes. Exports using metadata attributes from the editor (say, ContentTypeAttribute) must use MEFv1 attributes to export, whereas exports for the workspaces layer must use MEFv2 attributes. The rule is subtle and yet simple, and so a diagnostic is provided which catches any offenses to prevent confusion.
      
      This also has some impact in how we create MEF hosts: if you wish to host just the base workspaces layer, we can use MEFv2 to compose everything. The HostServices implementation (MefV1HostServices) that consumes a MEFv1 ExportProvider. If you’re in Visual Studio, you can use this implementation to get the full set of host services provided in Visual Studio.
      
      Otherwise, most of the changes in here are minor: we react to some APIs that have been moved/renamed in the portable subset we are targeting, and also align our various exception helper utilities with the compiler’s precedent. (changeset 1349276)
      e76a29a4
  12. 25 9月, 2014 1 次提交
  13. 10 9月, 2014 1 次提交
  14. 08 7月, 2014 1 次提交
  15. 20 6月, 2014 1 次提交
  16. 28 3月, 2014 2 次提交
  17. 27 3月, 2014 1 次提交
  18. 23 3月, 2014 2 次提交
  19. 22 3月, 2014 1 次提交
  20. 21 3月, 2014 1 次提交
  21. 19 3月, 2014 1 次提交