- 10 3月, 2018 3 次提交
-
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
This moves Roslyn to use the 2.1 SDK. This may appear to be moving the SDK version backwards from 2.2 to 2.1. In reality though it is a move forward. There was a brief time when the SDK switched their versions to 2.2 before reverting back to 2.1. Roslyn took a dependency on SDK in that small window. More details available here: https://github.com/dotnet/announcements/issues/57
-
由 Dustin Campbell 提交于
Adjust indent block operations used for VB smart indent in argument lists
-
- 09 3月, 2018 23 次提交
-
-
由 Tomáš Matoušek 提交于
* Extract common code to a helper method
-
由 Dustin Campbell 提交于
Add unit test that properly covers scenario where the first argument on a line is not the first token and is split across multiple lines
-
由 Shyam-Gupta 提交于
Merge dev15.6.x to dev15.7.x
-
由 Jared Parsons 提交于
Enable C# emit tests on CoreClr
-
由 Dustin Campbell 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
This conditions the use of SigningTestHeplers to only be in the net461. In the long term this type needs to be changed to be portable friendly. Filed the following bug to track https://github.com/dotnet/roslyn/issues/25228
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
- Fixed build break in the DevDivInsertionFiles - Fixed a couple of test failures
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
Key problem with the tests is they were being run in parallel. This is due to using CoreClr which doesn't respect our .config based options. Also fixed bad uses of Thread.Abort in the try finally tests which were causing resource cleanup issues 147 failures remaining to handle
-
由 Jared Parsons 提交于
This updates the CoreClr test infrastructure to include verifying the metadata signaturse of the emitted code. There is not 100% parity due to the inability to read custom attribute data on parameters, fields, etc ... But that covers only a small number of test cases. Destructor tests now passing.
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
Needed the split between the netstandand and desktop version of the reference to be more explicit.
-
由 Jared Parsons 提交于
The ability to verify IL is presently a runtime specific operation. Moved the logic to enforce the test conforms to the specified behavior into the runitme layers.
-
由 Jared Parsons 提交于
-
- 08 3月, 2018 9 次提交
-
-
由 Dustin Campbell 提交于
Visual Basic argument lists (and other parenthesized lists, like parameter lists and type parameter lists), have specialized smart indent behavior. Essentially, arguments after the first argument in a list are indented to the same position as the first argument. Consider the following code. ``` VB Sub M() Console.WriteLine("{0} + {1} = {2}", 19, 23, 19 + 23) End Sub ``` If the user presses ENTER before the second argument (19), the indentation looks like so. ``` VB Sub M() Console.WriteLine("{0} + {1} = {2}", 19, 23, 19 + 23) End Sub ``` However, this can cause indentation issues if the user wants to ident all subsequent arguments differently. Consider the following scenario. ``` VB Sub M() Console.WriteLine("{0} + {1} = {2}", 19, 23, 19 + 23) End Sub ``` Now, if the user presses ENTER before the third argument (23), the indentation of the first argument will be used, even though the user had indented the second argument differently: ``` VB Sub M() Console.WriteLine("{0} + {1} = {2}", 19, 23, 19 + 23) End Sub ``` This problem occurs because a single indent block operation is created for the whole argument list using the indentation of the first argument. This change fixes the issue by creating multiple indent block operations using the indentation of the first argument, and the indentation of any argument that appears on a different line.
-
由 Tomáš Matoušek 提交于
-
由 Tomáš Matoušek 提交于
* Refactor Windows PDB writer
-
由 Kevin Pilch 提交于
Remove NFW causing delays
-
由 Jason Malinowski 提交于
Move checking of structure-options to a common location (so it will be picked up by all roslyn languages).
-
由 Tomáš Matoušek 提交于
* Move common parts of Microsoft.CSharp.Core.targets and Microsoft.VisualBasic.Core.targets to Microsoft.Managed.Core.targets
-
由 Tomáš Matoušek 提交于
-
由 Tomáš Matoušek 提交于
-
由 Tom Meschter 提交于
Add a comment to make it clear that we don't expect other projects to still be referencing the project being `Disconnect`ed, and why we're protecting against it.
-
- 07 3月, 2018 5 次提交
-
-
由 Fred Silberberg 提交于
Merge 15.7.x features/compiler work into the dev15.7.x
-
由 Tom Meschter 提交于
Remove a non-fatal Watson report that was triggering frequently and causing UI delays. We expected that all references to a project would be removed before the project itself was unloaded, and this report was added to help us diagnose the rare occasion when that did not occur. It turns out that it happens quite frequently: when a solution closes, when a project changes externally and needs to be reloaded, and when a project is deleted from the solution. We're getting a lot more of these events than expected, and worse, collecting the Watson data sometimes causes long pauses in the UI. We do not have a concrete plan for dealing with the underlying issue, but the data we've already collected from these reports demonstrates the scope of the problem and collecting more won't help at this point. Since the collection itself is causing problems, it's time to just remove it.
-
由 Heejae Chang 提交于
* enable logAnalyzerExecutionTime on IDE so that we can start track analyzer perf * removed unnecessary ICodeAnalysisDiagnosticAnalyzerExecutor interface. it was added when OOP is first introduced to make sure VS.Next dll won't get loaded to VS process if OOP is not enabled. when it is enabled by default, rather than removing the interface, implementation just moved down to feature layer to reduce code churn. now, I am properly removing unnecessary abstraction. * take Executor out of test MEF composition * added IRemoteDiagnosticAnalyzerService interface * made initial version working. * added tests * add tracking for inproc only analyzers * pass in diagnostic analyzer service * added open file performance tracking as well. * added PII test * dont hash analyzerId when it is reported by internal user * added link to LOF wiki * made blame to track open files as well. * forgot to add return in if statement * reduce threshold to 100ms decide to start from lower threshold and then iterate rather than start from higher threshold * added a way to log real time perf data in local machine with explicit option which can be used to train formula later * addressed ivan's feedbacks * renamed to ExpensiveAnalyzerInfo * addressed PR feedbacks * more renames * addressed PR feedbacks. renamed as much as I can find. * listener can be null in unit test * addressed PR feedbacks
-
由 Martin Strecker 提交于
Return FormattableString for BoundTupleExpression.Display/BoundStackAllocArrayCreation.Display and allow FormattableString in DiagnosticInfo.Arguments.
-
由 Shyam-Gupta 提交于
Updating nuget prerelease versions
-