- 02 4月, 2020 6 次提交
-
-
由 David Barbet 提交于
-
由 David 提交于
-
由 David 提交于
Add Razor LSP client to activate in non-liveshare scenarios and only …
-
由 Allison Chou 提交于
Fix parameter code refactoring provider crash
-
由 Andy Gocke 提交于
Fixes #42396
-
由 Jared Parsons 提交于
Fix EditorFeatures2 flakiness
-
- 01 4月, 2020 34 次提交
-
-
由 David Poeschl 提交于
Improve completion's type inference for parameters of lambdas being passed as arguments
-
由 Jared Parsons 提交于
Work around for #42982
-
由 msftbot[bot] 提交于
Merge master to master-vs-deps
-
由 David Barbet 提交于
-
由 CyrusNajmabadi 提交于
Do not offer to simplify ToString on ref structs
-
由 Sam Harwell 提交于
Convert RemoveUnnecessaryCastTests to the new test framework
-
由 Tomáš Matoušek 提交于
* Harden Add/WithProjectReferences more * Feedback
-
由 msftbot[bot] 提交于
Fix 'use explicit type' with ref variables.
-
由 Manish Vasani 提交于
Ensure that the public GetOption API returns the public CodeStyle opt…
-
由 Jared Parsons 提交于
-
由 Allison Chou 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Gen Lu 提交于
Fix import completion for extension methods declared in conflicting types
-
由 Jared Parsons 提交于
The EditorFeatures2 flakiness was being caused by two separate issues. The first underlying problem is a simple bug in async completion. This issue is being tracked by the VS editor team here https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1091056 The second issue is how the Roslyn test framework handles unexpected extension exceptions. It was using a `FailFast` call when this happened vs. using `Assert.Fail` or similar. The reason being that at the point the unexpected exception is detected using `Assert.Fail` isn't effective because the editor is going to catch and swallow all exceptions. The `FailFast` is the only way to guarantee that the test will fail. The downside to `FailFast` though is that it doesn't produce actionable information. The xUnit process will simply exit with no stack trace, failure message, etc .... just a fail fast error code. This makes failures like this incredibly hard to track down. To fix this the `TestExtensionErrorHandler` will now store the unexpected `Exception` object and the containing workspace will look for it and fail the test in `Dispose`. This will reliably fail the tests that use `TestWorkspace` in this manner. closes #42586
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 Sam Harwell 提交于
-
由 jnm2 提交于
-
由 msftbot[bot] 提交于
Improve diagnostics for incorrect test configuration
-
由 msftbot[bot] 提交于
Merge master to master-vs-deps
-
由 CyrusNajmabadi 提交于
-
由 Gen Lu 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Gen Lu 提交于
Update src/Features/Core/Portable/Completion/Providers/ImportCompletionProvider/ExtensionMethodImportCompletionHelper.cs Co-Authored-By: NCyrusNajmabadi <cyrus.najmabadi@gmail.com>
-
由 Cyrus Najmabadi 提交于
-
由 Joey Robichaud 提交于
-
由 Sam Harwell 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Joey Robichaud 提交于
Use the Trivial temporary storage service on non-windows platforms
-
由 Manish Vasani 提交于
-
由 David Poeschl 提交于
Co-Authored-By: NCyrusNajmabadi <cyrus.najmabadi@gmail.com>
-
由 David Poeschl 提交于
Co-Authored-By: NCyrusNajmabadi <cyrus.najmabadi@gmail.com>
-
由 Chris Sienkiewicz 提交于
Merge Features/source generators to master
-