- 19 2月, 2020 1 次提交
-
-
由 Tomáš Matoušek 提交于
* Clean up string resources, use Arcade resx generator * CodeLens resources * Use NET20 instead of NETFX20
-
- 14 2月, 2020 1 次提交
-
-
由 Adeel Mujahid 提交于
-
- 13 2月, 2020 1 次提交
-
-
由 Charles Stoner 提交于
-
- 12 2月, 2020 1 次提交
-
-
由 Yair Halberstadt 提交于
-
- 31 1月, 2020 6 次提交
-
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
The TPA now considers the output directory as a trusted place for loading assemblies. To the point it will prefer certain DLLs in the output directory over equal ones that ship with the runtime. This broke a number of VB tests here because we unconditionally referenced the desktop version of Microsoft.VisualBasic. This got copied to the output directory, included in the TPA and hence loaded during test execution. This breaks tests because they require the .NET Core version of Microsoft.VisualBasic. Conditioned the reference to be desktop only so it's not present on our .NET Core builds
-
由 Jared Parsons 提交于
Decided to remove the property based approach to specifying a target framework to just specifying `netcoreapp3.1` directly. The reason for this is the following: The advantage of the property is it makes it "easy" to change to a new target framework in the future. That benefit is actually pretty minimal. A simple find and replace operation is **extremely** effective in our code base (it's less key strokes than this message). Hence the benefit is minimal. The downside of the property is that our code doesn't look like customer code. Or rather it diverges from the practices that we publish. In general I prefer to keep our code as standard as possible unless there is a good reason to deviate. There just doesn't seem to be one here.
-
由 Jared Parsons 提交于
-
-
由 Jared Parsons 提交于
Change Roslyn to target netcoreapp3.1 when building .NET Core assets. Previously the code targetted a mix of netcoreapp2.1 and netcoreapp3.0. The mix is due to default interfaces only being supported on netcoreapp3.0 and hence our testing needed to use that. Yet at the same time we were required to ship the compiler in SDKS that targetted netcoreapp2.1. Now we can universally target netcoreapp3.1.
-
- 29 1月, 2020 2 次提交
-
-
由 Julien Couvreur 提交于
-
由 Tomáš Matoušek 提交于
* Move "is telemetry allowed" flag to DiagnosticAnalyzerInfoCache * Clean up DiagnosticService * Fixes * Remove analyzer exception telemetry reporting. * Remove reporting analyzer exceptions from SupportedDiagnostics. The diagnostics will be reported when the compiler runs the analyzer on the compilation. * Remove unused parameter * Clean up analyzer telemetry reporting. * Test fixes * Feedback
-
- 25 1月, 2020 1 次提交
-
-
由 AlekseyTs 提交于
Fixes #41207.
-
- 23 1月, 2020 1 次提交
-
-
由 Jonathon Marolf 提交于
-
- 16 1月, 2020 1 次提交
-
-
由 Jared Parsons 提交于
-
- 14 1月, 2020 1 次提交
-
-
由 Julien Couvreur 提交于
-
- 10 1月, 2020 4 次提交
-
-
由 Rikki Gibson 提交于
-
由 Rikki Gibson 提交于
-
由 Rikki Gibson 提交于
This reverts commit 6b22ff18.
-
由 Rikki Gibson 提交于
-
- 01 1月, 2020 1 次提交
-
-
由 Neal Gafter 提交于
Relates to #375
-
- 13 12月, 2019 1 次提交
-
-
由 Tomáš Matoušek 提交于
-
- 31 10月, 2019 1 次提交
-
-
由 AlekseyTs 提交于
Respect filterTree and filterSpanWithinTree while collecting diagnostics for misplaced doc comments. (#39525) Fixes #39315.
-
- 30 10月, 2019 1 次提交
-
-
由 AlekseyTs 提交于
Move optimization around use of Nullable type in Boolean Expressions into LocalRewriter and eliminate invalid optimization. (#38802) * Move optimization around use of Nullable type in Boolean Expressions into LocalRewriter and eliminate invalid optimization. Fixes #38305. The goal of optimization is to eliminate the need to deal with instances of Nullable(Of Boolean) type as early as possible, and, as a result, simplify evaluation of built-in OrElse/AndAlso operators by eliminating the need to use three-valued Boolean logic. The optimization is possible because when an entire Boolean Expression is evaluated to Null, that has the same effect as if result of evaluation was False. However, we do want to preserve the original order of evaluation, according to language rules. * Fix an old bug masked by #38305. * Fix an old bug masked by #38305. * More fixes fo old bugs masked by #38305, plus optimizations that wouldn't be performed by compiler. * PR feedback
-
- 15 10月, 2019 1 次提交
-
-
由 Ivan Basov 提交于
-
- 08 10月, 2019 2 次提交
-
-
由 Charles Stoner 提交于
-
由 Neal Gafter 提交于
Fixes #24737
-
- 04 10月, 2019 1 次提交
-
-
由 nnpcYvIVl 提交于
-
- 01 10月, 2019 1 次提交
-
-
由 Charles Stoner 提交于
-
- 27 9月, 2019 1 次提交
-
-
由 Adam Speight 提交于
-
- 26 9月, 2019 1 次提交
-
-
由 nnpcYvIVl 提交于
Spelling fix
-
- 24 9月, 2019 1 次提交
-
-
由 Charles Stoner 提交于
-
- 19 9月, 2019 1 次提交
-
-
由 AlekseyTs 提交于
Fixes #38711.
-
- 18 9月, 2019 1 次提交
-
-
由 nnpcYvIVl 提交于
-
- 10 9月, 2019 1 次提交
-
-
由 Tomáš Matoušek 提交于
-
- 07 9月, 2019 2 次提交
-
-
由 dotnet-bot 提交于
-
由 Tom Meschter 提交于
-
- 06 9月, 2019 1 次提交
-
-
由 AlekseyTs 提交于
Adjust inconsistent accessibility checks to properly handle protected types declared within interfaces. (#38451) Fixes #38398.
-
- 04 9月, 2019 1 次提交
-
-
由 Tom Meschter 提交于
Related to #38454. These tests fail in the CI runs for #38417 which adds translations for various resources. The problem is the test compares localized text with the original English text; this worked fine until now because the localized text wasn't yet translated, and so just happened to be the same as the English. The point of this change is to unblock #38417.
-
- 31 8月, 2019 1 次提交
-
-
由 Larry Golding 提交于
-