- 15 4月, 2017 5 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 AlekseyTs 提交于
SemanticModel should cache synthesized bound statements in a separate cache in order to avoid “polluting” regular cache. (#18662) Fixes #10604. Fixes #16306.
-
由 Neal Gafter 提交于
Fixes #17921
-
由 AlekseyTs 提交于
Ensure proper handling of a line-break following an incomplete string interpolation. Fixes https://devdiv.visualstudio.com/DevDiv/_workitems?id=405887. The error recovery wasn’t including the line-break into interpolated string, yet wasn’t creating proper statement terminator token for it. The change ensures that the line-break is treated as part of the string for the purpose of the error recovery, this is what would happen if the interpolation was properly terminated with ‘}’ before the end of the line.
-
- 14 4月, 2017 23 次提交
-
-
由 Neal Gafter 提交于
Fixes #18188
-
由 Kevin Pilch 提交于
Removes control type from NavBar's accessible names
-
由 CyrusNajmabadi 提交于
Report an NFW instead of asserting when we encounter a symbol we can't roundtrip to OOP.
-
由 CyrusNajmabadi 提交于
Don't offer to convert an 'if' to a 'throw expressoin' if there is an 'else clause'
-
由 Kevin Pilch 提交于
Add back the PR template.
-
由 Charles Stoner 提交于
Include default in 'Compiler Test Plan.md'
-
由 Kevin Pilch 提交于
-
由 Kevin Pilch 提交于
-
由 CyrusNajmabadi 提交于
-
由 Charles Stoner 提交于
-
由 CyrusNajmabadi 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
This change fixes two problems in our powershell scripts 1. Removes all uses of Invoke-Expression. This commandlet doesn't do error checking on windows commands and hence can hide failures. Relpaced with Exec-Expression which properly checks both the windows command error and the powershell error 1. Reset $LastExitCode inside Exec before executing the script block. This avoids cases where previous windows command failures could carry over to a script block that didn't execute any windows commands. Powershell guidelines changed appropriately
-
由 Jared Parsons 提交于
-
由 Ravi Chande 提交于
Fix extract method test baseline
-
由 Ravi Chande 提交于
Fix CsharpCodeActions.FastDoubleInvoke flakiness
-
由 CyrusNajmabadi 提交于
Do not fully qualify type name if it would not resolve error.
-
由 CyrusNajmabadi 提交于
Classify type names, even when arity does not match.
-
由 Ravi Chande 提交于
Port BasicEndConstruct
-
由 Ravi Chande 提交于
Fix crash in implements clause completion
-
由 Ravi Chande 提交于
-
由 Ravi Chande 提交于
Fix Winforms DeleteControl tests
-
- 13 4月, 2017 12 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 Nat Ayewah 提交于
Merge dev15.2.x to master
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
Provide completion that offers the explicit-interface-type when typing new members.
-
由 Nat Ayewah 提交于
-
由 Andy Gocke 提交于
This change retargets the CSharpSymbolTest project from .NET 4.6 (which runs only on the desktop CLR) to netstandard 1.3 (which runs on both the Desktop 4.6 framework and CoreCLR). These changes are necessary to enable more test coverage on CoreCLR, which will be especially impactful when we want to test language features which are only targeted to run on CoreCLR. There are a lot of file changes in this PR but the most significant new code is in the TestExecutionContext, which is a new CoreCLR AppContext-based mechanism for running in-memory assemblies. This class is meant to have similar functionality to the existing desktop RuntimeEnvironment, but because AppDomains and AppContexts are incompatible, there are some substantial differences. Most notably, the TestExecutionContext views all assemblies next to the CoreCLR test runner (the "app base") as being shared among all test execution runs, including static variables. In contrast, the AppDomain runner only shares assemblies which are already loaded. The second notable change is a rename from CreateCompilationWithMscorlib to CreateStandardCompilation. Despite the name, the most common usage of CreateCompilationWithMscorlib was just meant to create a simple compilation. The .NET Framework mscorlib was provided as a reference because it provided most of the common types our tests need to compile against, but it wasn't particularly important which types it supplied, beyond a minimum set. Unfortunately, compiling against the .NET Framework mscorlib can introduce severe incompatibilities when trying to run the application on CoreCLR (which uses System.Runtime as its basis). This PR instead provides a new set of references (NETStandard.Library 2.0, the "standard" references) to try to provide as much compatibility as possible while also providing portability. Thus, the CreateCompilationWithMscorlib methods were renamed to CreateStandardCompilation to make it clear that no specific set of references is guaranteed when compiling against it. If that is desired, it's recommended to use the existing CreateCompilation methods to construct an explicit set of references to compile against (with all the implications that come from that).
-
由 Andy Gocke 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-