- 04 2月, 2020 4 次提交
-
-
由 Julien Couvreur 提交于
Rename from IncludeNonNullableReferenceTypeModifier to IncludeNotNullableReferenceTypeModifier (#41332)
-
由 Tomáš Matoušek 提交于
* Set TEMP environment variable to $TempDir on CI machines https://github.com/dotnet/arcade/pull/4744 reverted setting the variable in `tools.ps1` due to issues it caused in other repos.
-
由 Manish Vasani 提交于
Stop Simplifier.ReduceAsync removing empty arg lists from delegates
-
由 Allison Chou 提交于
Fix for Visual Studio crashes when adding a parameter to a function
-
- 01 2月, 2020 8 次提交
-
-
由 Tomáš Matoušek 提交于
* Fix Pythia pooled objects wrappers * Fix RPC
-
由 Sam Harwell 提交于
Fix issues in MetadataAsSource XML documentation comment conversion
-
由 Allison Chou 提交于
-
由 Allison Chou 提交于
-
由 Sam Harwell 提交于
Make ValueText return empty instead of null
-
由 Jared Parsons 提交于
Target netcoreapp3.1
-
由 Allison Chou 提交于
-
由 David Poeschl 提交于
Name suggestions don't contain suggestions starting with a digit.
-
- 31 1月, 2020 27 次提交
-
-
由 dotnet-maestro[bot] 提交于
* Update dependencies from https://github.com/dotnet/arcade build 20200129.8 - Microsoft.DotNet.Arcade.Sdk - 5.0.0-beta.20079.8 * Update dependencies from https://github.com/dotnet/arcade build 20200130.4 - Microsoft.DotNet.Arcade.Sdk - 5.0.0-beta.20080.4
-
由 Gen Lu 提交于
Remove some test input to reduce execution time
-
由 Sam Harwell 提交于
Closes #41304
-
由 Sam Harwell 提交于
Fix export provider factory caching
-
由 Tomáš Matoušek 提交于
-
由 Gen Lu 提交于
-
由 Sam Harwell 提交于
-
由 Tomáš Matoušek 提交于
-
由 Jason Malinowski 提交于
Speed up TempPECompiler
-
由 Jason Malinowski 提交于
This API has always accepted null as a shortcut for an empty array, so this annotates it accordingly.
-
由 Jared Parsons 提交于
Had to clean up a few nullable annotations now that we are compiling agaist `netcoreapp3.1` and hence get the full value of the framework annotations. This is also problematic though because there are now two places where the compiler can see nullable attributes that are directly used by the developer. For example `NotNullWhenAttribute`. This is both defined in our assemblies for non-netcoreapp target frameworks and provided by the SDK when targeting `netcoreapp3.1`. This causes a problem for assemblies which have the following characteristics: 1. Target `netcoreapp3.1` 1. Reference an assembly targeting `netstandard2.0` which uses our nullable attributes definition 1. Has IVT into (2) above These properties essentially define all of our unit test assemblies. In that environment it's not possible to use nullable attributes in code because the compiler can't disambiguate which definition of `NotNullWhenAttribute` to use. This meant I had to temporarily remove a few attributes until we can complete #40766.
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 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.
-
由 Jared Parsons 提交于
-
- 30 1月, 2020 1 次提交
-
-
由 David Wengier 提交于
-