1. 09 7月, 2015 1 次提交
  2. 05 6月, 2015 1 次提交
  3. 02 6月, 2015 1 次提交
    • M
      Symptom: Fix all not available when providing more than one code fix · b5c0889d
      Manish Vasani 提交于
      User scenario: A CodeFixProvider that supports fix all occurrences code fix, gets FixAll support in IDE if it registers a single code action, but disappears as soon as fixer registers multiple code actions.
      
      Reason: A CodeFixProvider that intends to support fix all occurrences must classify the registered code actions into equivalence classes by assigning it an explicit, non-null equivalence key which is unique across all registered code actions by this fixer. This enables the FixAllProvider to fix all diagnostics in the required scope by applying code actions from this fixer that are in the equivalence class of the trigger code action.
      The analyzer added by this change catches violations of this requirement in the code actions registered by a CodeFixProvider that supports FixAllProvider.
      
      Fixes #2864
      b5c0889d
  4. 18 4月, 2015 1 次提交
  5. 17 4月, 2015 1 次提交
  6. 27 3月, 2015 1 次提交
  7. 24 3月, 2015 2 次提交
  8. 07 3月, 2015 2 次提交
  9. 13 2月, 2015 1 次提交
  10. 14 1月, 2015 2 次提交
  11. 24 12月, 2014 3 次提交
    • 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
    • J
      This makes the following changes to the VBCSCompiler Process · 73f88cde
      jaredpar 提交于
           1. Removes the shared state and locks in favor of a more event driven style model.  Values which were previously represented as writes to shared state are now represented as Task<T> values.  The server will create the necessary Task values for the given state of the server, wait on any of them to complete and then handle them in a defined order.  This eliminates a couple of remaining race condition in the server.
      
           2. In the case of a client disconnect the server will initiate a soft shutdown.  It will accept no new connections but wait for the remaining connections to complete processing before terminating the process.
      
           There is no fear of state corruption here.  The goal is parity with the native command line compiler.  If the user kicked off an expensive compilation they could terminate it with Ctrl+C and free up machine resources (or simply stop the compiler from repeatedly page faulting the machine).  Roslyn needs to mimic this behavior as best as possible with VBCSCompiler.
      
           To be clear: this allows the server to complete while the compiler is still compiling code.  It will only do so for connections which were severed by the client disconnecting from the named pipe.
      
           3. In the case of an exception serving the compilation task the server will log the error and terminate itself immediately via Environment.Exit.  Such an exception represents a flaw in the compiler itself and we can make no guarantees about the state of shared data in the compiler.  Hence we terminate all existing task
      
       (changeset 1383458)
      73f88cde
  12. 04 12月, 2014 1 次提交
    • J
      Clean up unnecessary StyleCop inclusion and fix packages.config. · d07164b7
      jasonmalinowski 提交于
      We had a number of projects that included the StyleCop NuGet package only to also disable StyleCop. We also had some projects that were referencing assemblies out of packages but didn't say so in packages.config, or had stuff in packages.config not reflected in the actual project file. (changeset 1378738)
      d07164b7
  13. 07 11月, 2014 1 次提交
  14. 17 10月, 2014 1 次提交
  15. 16 10月, 2014 1 次提交
  16. 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
  17. 10 10月, 2014 1 次提交
  18. 25 9月, 2014 1 次提交
  19. 10 9月, 2014 2 次提交
  20. 26 7月, 2014 1 次提交
  21. 08 7月, 2014 1 次提交
  22. 20 6月, 2014 1 次提交
  23. 22 4月, 2014 1 次提交
  24. 28 3月, 2014 2 次提交
  25. 27 3月, 2014 2 次提交
  26. 26 3月, 2014 1 次提交
  27. 23 3月, 2014 2 次提交
  28. 22 3月, 2014 1 次提交
  29. 21 3月, 2014 1 次提交
  30. 19 3月, 2014 1 次提交