- 10 2月, 2016 22 次提交
-
-
由 Tomáš Matoušek 提交于
Fix DiaSymReader nuget version string calculation
-
由 David Kean 提交于
Add support for paths with spaces in cibuild
-
由 Gen Lu 提交于
Replacing unreachable exception with no-op in OperationVisitor
-
由 Tomas Matousek 提交于
-
由 Manish Vasani 提交于
Address performance issues in the AnalyzerManager reported at…
-
由 David Kean 提交于
Stop deploying extension in BuildAndTest.proj
-
由 Gen Lu 提交于
-
由 Gen Lu 提交于
-
由 Charles Stoner 提交于
Ignore accessors in SetMetadataName
-
由 Balaji Krishnan 提交于
Change how we format on certain commit chars from completion. Fixes #7768, #8228
-
由 David Kean 提交于
Fixes #8498 2ed22626 caused CIBuild's to start deploying extensions because properties are not inherited by nested MSBuild instances. Actually pass down DeployExtension=false.
-
由 David Kean 提交于
-
由 Charles Stoner 提交于
-
由 Manish Vasani 提交于
Address performance issues in the AnalyzerManager reported at https://github.com/DotNetAnalyzers/StyleCopAnalyzers/issues/2078#issuecomment-181150995: 1. Replace use of ConcurrentDictionaries with Dictionary + lock. 2. Avoid unncessary ToImmutableArray invocations. I also fixed up a subtle race condition in CompilationAnalysisValueProvider.TryGetValue for my last PR (see https://github.com/dotnet/roslyn/pull/8375/files#r52127390).
-
由 Tomáš Matoušek 提交于
Temporarily skip one more PDB test
-
由 Tomas Matousek 提交于
-
由 Tomas Matousek 提交于
-
由 Balaji Krishnan 提交于
Now that I have changed the flow for formatting here, the formatter could return no changes. In those cases, don't update the document.
-
由 Jared Parsons 提交于
-
由 Tomáš Matoušek 提交于
Change version of Microsoft.DiaSymReader to 1.0.7 (release)
-
由 Tomáš Matoušek 提交于
Update to the latest copy of SRM signature reader
-
由 Tomáš Matoušek 提交于
Read Portable PDB directly in EEs instead of thru ISymUnmanagedReader
-
- 09 2月, 2016 18 次提交
-
-
由 Jared Parsons 提交于
Update README for determinism job
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
Enable determinism job in Jenkins
-
由 Tomas Matousek 提交于
-
由 Tomas Matousek 提交于
-
由 Balaji Krishnan 提交于
..chars from completion. We used to call the formatting service from the completion list with the span equal to that of the text that we inserted, in all cases. This may not be the right approach in all cases and that is manifested when we are formatting for a typed char that happens to be the trigger character for the formatter as well. In such cases we must find the right span to give to the formatter, or in other words, the span the formatter would have come up with if it were triggered first for the typed char. We do this by simply invoking the appropriate formatting service API and giving it the typed char and its position, which lets the formatting service to compute the appropriate span. We do this only when the completion's commit char is also a trigger for formatting. In other cases, we continue taking the existing code path of formatting by giving it a known span. Fixes #7768, #8228
-
由 Tomas Matousek 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
Deterministic Builds
-
由 Charles Stoner 提交于
Remove unused constants from VisualBasicCompilationOptions
-
由 Matt Mitchell 提交于
Update config to match new versions of DSL/ghprb
-
由 Matt Mitchell 提交于
-
由 Charles Stoner 提交于
-
由 Artur Spychaj 提交于
Fix EnC issue with out of sync DocumentId
-
由 Jared Parsons 提交于
-
由 Andy Gocke 提交于
Turn off extension deploy everywhere
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-