- 02 11月, 2016 2 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 31 10月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
-
- 30 10月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 29 10月, 2016 1 次提交
-
-
由 Jb Evain 提交于
-
- 28 10月, 2016 3 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 Jared Parsons 提交于
-
由 Ravi Chande 提交于
-
- 27 10月, 2016 1 次提交
-
-
由 Heejae Chang 提交于
for now, serialize solution and its related data creation to reduce allocations
-
- 26 10月, 2016 3 次提交
-
-
由 Paul Vick 提交于
-
由 Paul Vick 提交于
Cache in CodeLens service
-
由 Jared Parsons 提交于
-
- 25 10月, 2016 11 次提交
-
-
由 Paul Vick 提交于
-
由 Paul Vick 提交于
-
由 CyrusNajmabadi 提交于
-
由 Omar Tawfik 提交于
-
由 Ravi Chande 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 Ravi Chande 提交于
Signature help improvements for C# tuples (renamed to work around jenkins issues)
-
由 Ravi Chande 提交于
-
-
由 CyrusNajmabadi 提交于
Sort same-named NavTo items to better ensure the topmost results are more in line with what the user wants.
-
- 24 10月, 2016 8 次提交
-
-
由 Jared Parsons 提交于
This should either be defined globally or not at all. Repeating all the logic on a local level is just wasted time.
-
由 Jared Parsons 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 22 10月, 2016 4 次提交
-
-
由 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.
-
由 Heejae Chang 提交于
implements IProjectCacheHostService in OOP.
-
由 Heejae Chang 提交于
adding more cancellation
-
由 Paul Vick 提交于
-
- 21 10月, 2016 5 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
-
由 CyrusNajmabadi 提交于
Remove SuppressionSuggestionAction. It is not needed since we have SuggestedActionWithNestedActions.
-