| Age | Commit message (Collapse) | Author |
|---|
|
|
|
(#29182)
System.Numerics.Vectors was made inbox in netcoreapp2.0, we were still allowing distribution
in the package, however the package was applying the netstandard2.0 implementation to
netcoreapp2.0.
Now that we've disabled oobing the netcoreapp2.1 build (since many types were moved into
corelib) it no longer makes sense for us to mantain the ability to oob the netcoreapp2.0 build.
Doing so not only degrades the inbox version (by not using the framework's MathF
implementation) but also creates type-unfication issues on rollforward: app targets 2.0
carries OOB copy of Vectors with higher version than 2.1, rolls forward to 2.1 and host will
use the OOB copy, no longer unifying to the types in corelib.
|
|
Merge at sha d1d5135ef69f0b64001694d93a6a9fc4cd23d23b
Merge conflicts were only in dependency versions which
should get reset after the next build. Also reset
PrereleaseLabel back to preview2 for the release/2.1 branch
|
|
* Produce Windows PDBs when building for netfx and in a Windows OS
* Use TargetGroup and RunningOnUnix instead
|
|
|
|
* Updating the package index for UAP and updating buildtools
* Having System.Reflection.DispatchProxy crosscompile for uap RS3
* Updating buildtools and fixing PR feedback
* Re-add support for uap to the assemblies that already had a netcoreapp2.0 config for Windows
|
|
tests added for span overload for path Apis
|
|
This feature is not shipping in 2.1.
|
|
|
|
Contributes to https://github.com/dotnet/corefx/issues/6185.
|
|
The flag indicates that the runtime supports default implementation of interfaces.
Since this is a prerelease feature that is not complete yet (and we don't want to accidentally ship it), the flag is keyed off a newly added `IsPrerelease` property. This property is expected to be flipped to `false` in release branches.
This corresponds to dotnet/coreclr#15358.
|
|
Updating URL to point to the new main feed
|
|
Add blob feed as a restore source
|
|
|
|
This makes us uniform. Allows VSCode (which does not suport MSPdbs) use on Windows.
|
|
|
|
Workaround https://github.com/NuGet/Home/issues/4094
|
|
|
|
(#24461)
|
|
* Use stackalloc directly into Span
We have a few places in corefx where we were stackalloc'ing into a temporary pointer and then creating a Span from that. Now that we're using a C# compiler which supports stackalloc'ing directly into span, use that feature instead.
* Address PR feedback
|
|
* Updating corefx to use new roslyn compiler
* Updating to new version of the compiler and use the switch so tests pass on desktop
* Fix System.Reflection.Metadata tests
|
|
This change disables syncing and binplacing of test framework when the
-BuildTests option passed to build.sh or sync.sh is set to false.
This is helpful when bootstrapping a new platform where the core-setup
is not built yet and so the Microsoft.NETCore.DotNetHost and
Microsoft.NETCore.DotNetAppHost packages that are required for the
test running don't exist yet.
|
|
BuildConfiguration (#23633)
* With this change we will have the next behavior when building/running tests:
-When building the tests we will still bin place the test assets to the OutputDirectory (corefx\bin\OSGroup.Configuration\TestProject\TargetGroup/)
-When running the tests we will bin place the tests assets to this new TestPath which will be the TestPath. This new path will be the test's working directory where we will bin place the RunTests.cmd and necessary dependencies in tests.targets. Also the testResults.xml will be found here after the test execution.
-TestPath is set to be bin/tests/<TestProject>/<BuildConfiguration>/ (i.e corefx\bin\tests\System.Collections.Immutable.Tests\netcoreapp-Windows_NT-Debug-x64) in dir.props
-This TestPath will be added to the BinPlaceDir in FrameworkTargeting.targets when BinPlaceTest is set to true. Then in the BinPlaceFiles target the test assets will be hardlinked to the TestPath.
This will isolate every test execution per build configuration and will allow people to run the same test project for all of the supported configurations on the same repo without having to clean the repo.
|
|
Now that we've shipped the NETStandard support package we will no longer build its content
from `master`.
It will be serviced from the `release/2.0.0` branch and the only netfx builds in `master` will
correspond to package content.
|
|
* Turn on setting GIT URL in File Version
This turns on tagging each CoreFX DLL built GitHub URL
of the source code that was used to build it.
You now get something that looks like the folloiwng when you do a filever -v
ProductVersion 4.6.25612.0 @BuiltBy: vancem-VANCEM4 @SrcCode: https://github.com/dotnet/corefx/tree/a329e252594f375348a8f06a3675606f5c03ce3f
Note that most of the work for this is in the buildtools, this simlpy sets the GitHubRepositoryName variable that turns it on.
* Fixed typo
* UPdate to latest build tools
|
|
|
|
Move the RID calculation to the common dir.props file.
Compute a ToolRuntimeRID to be used for assets that need to run as part of the tools infrastructure to build things.
Compute PackageRID which will be used as the target RID for the assets that are being built.
Make sure both ToolRuntimeRID and PackageRID honor both a specific and a portable RID.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This change mostly deals with moving Tools-Override and CoreFxTools
task library to BuildTools and consuming them from there instead.
|
|
We only need the ref and source to build for net462 and net47.
Building the tests for this is incorrect since most of the time we'd end
up rebuilding and rerunning the exact same tests on the exact same
machine wide framework multiple times. In the rare event that the
tests cross-compiled its still incorrect since the machine-wide
framework is still the same.
|
|
We need to support differing ref/impl per version of desktop until it
adds inbox support for ns2.0.
To do this I've made the netfx build also build for net462 and net47.
Then I've moved the files into framework-specific folders for each TFM.
For a given TFM it will prefer the files in its own folder then fallback
to the previous TFM if it doesn't have that file.
|
|
supported officially.
|
|
|
|
This package is a support package for NETStandard2.0 on .NET 4.6.1.
|
|
Updates how we define which key an assembly uses
|
|
|
|
Now instead of Use*Key a project can instead define the assembly key
in the project (genreally the common dir.pops for a project) using
the AssemblyKey property. The accepted values are Open, ECMA, MSFT,
Test.
This change allows for a repo to set the default key they want to use
for projects. In corefx we have switched the default to use the Open
key instead of the old BuildTools default of MSFT key.
As part of this update we are explicitly setting the AssemblyKey in
all the library projects (although it is really only necessary for
projects that aren't the default).
Also with this change we are updating all the new libraries that have
not yet shipped stable (compared to our 1.1 release) and making them
use the Open key. Which means that for prerelease dependencies there
might be some binary breaking changes to consume.
The following libraries ahven't shipped so there key is being
changed from MSFT to Open:
Microsoft.XmlSerializer.Generator
System.CodeDom
System.Configuration.ConfigurationManager
System.Data.Odbc
System.DirectoryServices
System.DirectoryServices.AccountManagement
System.DirectoryServices.Protocols
System.IO.Ports
System.Json
System.Memory
System.Net.HttpListener
System.Net.Mail
System.Net.ServicePoint
System.Net.WebClient
System.Net.WebProxy
System.Private.Xml
System.Private.Xml.Linq
System.Security.Cryptography.Xml
System.Security.Permissions
System.Transactions.Local
System.Web.HttpUtility
|
|
Move ILLink alpine workaround after RuntimeOS is set
|
|
|
|
Disable illink on alpine
|
|
The Alpine CLI was hacked together with the wrong bits for the shared
framework. It used 1.0 assemblies and put them in the 1.1 folder.
As a result this 1.1 targeting app fails to bind when it hits an
assembly (System.Xml.ReaderWriter) that was different.
Workaround it temporarily by turning off illink for alpine.
|
|
(#17975)
* Change netfx vertical test bin placing and execution to be able to have runs in helix
|
|
|
|
Enable sending uapaot test runs to Helix
|
|
* Enable UAP runs on Core* binaries.
|
