- 16 6月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 15 6月, 2017 5 次提交
-
-
由 En-Shuo Hsu 提交于
Merge master to dev15.6
-
由 Ravi Chande 提交于
Skip repl VSI tests
-
由 Jason Malinowski 提交于
Log telemetry if we see ITextBufferEdit.Apply() throwing exceptions
-
由 Ravi Chande 提交于
Failure tracked by https://github.com/dotnet/roslyn/issues/20219
-
由 Jared Parsons 提交于
Looks like there is still fall out from the licensing issue. VS integration tests still failing at 100% due to a timeout issue. Change them to not run by default while we look into this. Can still be run manually for testing with test vsintegration please
-
- 14 6月, 2017 3 次提交
-
-
由 Ivan Basov 提交于
-
由 Jared Parsons 提交于
Move language settings after SDK import
-
由 Jared Parsons 提交于
The new SDK unconditionally sets a number of MSBulid properties including many that we depend on in Roslyn. This is a break from the old MSBuild behavior which respected initial values. https://github.com/dotnet/sdk/issues/752 The behavior in 2.0 is changing to go back to the old model of respecting initial values. Roslyn though continues to often use the SDK installed with Visual Studio. That can be a variety of values from 2.0 prebuilds, to various drops of 1.0. As a result the success / failure of our build can depend a lot on which version of VS is installed and by consequence which new SDK comes with it. Subtle differences in the SDK can change the values we end up compiling with in our project. We've been guarding against this by directly re-setting values we knew to be overidden in some version of the SDK. Now though I'm worried this isn't an adequete solution for the following reasons. - Just this week I got new warnings in the build by using a new VS - The Microbuild lab is aggressively grabbing new builds of VS which means the VS SDK is also potentially changing. After some thought I decided to simply move all of our langauge specific settings after we import the core targets. Given that we unconditionally set the values it becomes irrelevant what the SDK does or does not respect.
-
- 13 6月, 2017 7 次提交
-
-
由 CyrusNajmabadi 提交于
Allocate less while performing classification.
-
由 CyrusNajmabadi 提交于
Improve 'Initialize Parameter' so it works with members that don't have their bodies written yet. Fixes #19956
-
由 CyrusNajmabadi 提交于
Be resilient to running with System.IEquatable can not be found. Fixes #20158
-
由 CyrusNajmabadi 提交于
Fix race with boosting OOP priority. Also, ensure FindRef calls are boosted.
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 11 6月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
Add SyntaxGenerator support for Tuples.
-
- 10 6月, 2017 17 次提交
-
-
由 En-Shuo Hsu 提交于
Merge master to dev15.6
-
由 Julien Couvreur 提交于
-
由 Kevin Pilch 提交于
[Perf] Optimize IsOrContainsAccessibleAttribute
-
由 Heejae Chang 提交于
-
由 Kevin Pilch 提交于
Force load projects that failed design time builds, not ones that opt out of LSL
-
由 Heejae Chang 提交于
no explicit workspace cache on code lens since FAR has its own cache …
-
由 CyrusNajmabadi 提交于
-
由 Manish Vasani 提交于
Remove strong reference to AnalyzerOptions in the analyzer manager ex…
-
由 CyrusNajmabadi 提交于
-
由 Jared Parsons 提交于
Track down NuGet cache corruption
-
由 Brett V. Forsgren 提交于
Revert "allow waiters to be consumed from internal VS tests"
-
由 Tomáš Matoušek 提交于
Refactor tests
-
由 Manish Vasani 提交于
Add a unit test to ensure that analyzer execution does not leak solution instances from preview workspace.
-
由 Jared Parsons 提交于
This change should help us pin down why we are seeing NuGet cache corruption issues in our Jenkins job. It adds a check to three places in our script: - Start - Post restore - End Depending on when this check fails it should give us a better picture of where the corruption is occuring. https://github.com/dotnet/roslyn/issues/19882
-
由 Brett V. Forsgren 提交于
-
由 Jason Malinowski 提交于
Hack around PublicAPI item group support in the new project system
-
由 Manish Vasani 提交于
Move Roslyn assemblies to consume newer OptimizationData
-
- 09 6月, 2017 6 次提交
-
-
由 Jason Malinowski 提交于
This is a workaround for dotnet/project-system#2160 where AdditionalFileItemNames isn't quite behaving correctly with the IDE. This can be reverted once that bug is fixed.
-
由 Heejae Chang 提交于
-
由 Julien Couvreur 提交于
-
由 Dustin Campbell 提交于
Fix completion in AdhocWorkspace
-
由 Vladimir Sadov 提交于
Prevent in-place optimization of struct construction when ctor has non-byval parameters .
-
由 Andy Gocke 提交于
This reverts commit 8a1ca479 and moves publish earlier in the build pipeline (before signing) to prevent published binaries from overwriting already built and signed binaries.
-