| Age | Commit message (Collapse) | Author |
|---|
|
* Adds WebAssembly OsGroup and wasm ArchGroup.
* Build System.Native for WebAssembly
|
|
|
|
to be set incorrectly. (#29640)
|
|
Issue #29249
|
|
Even though the tools know about netcoreapp2.2 we
don't need to care about testing it in the release/2.1
branch which is focused on shipping netcoreapp2.1
|
|
Detect source-build via DotNetBuildFromSource instead of
DotNetBuildOffline which is set for the tarball build.
|
|
The alpine 3.6 builds have been replaced with the more generic
linux-musl builds so removing them.
|
|
We're walking the closure of packages that build on top of netcoreapp2.1. Those build using live references but the current package testing infrastructure tests against an LKG framework package. As a result when we bump reference versions every package will see a break until we get an updated LKG with the new reference assemblies.
Once we have a new Microsoft.NETCore.App we can remove this closure exception.
|
|
previous frameworks when API or type location changes
Now that roll forward is supported we must version our assemblies when surface area changes or when types are moved.
I did a scan of all assemblies that ship an implementation for netcoreapp2.0, have a version >= the version inbox,
and the implementation exposes different API or has moved types.
|
|
rc1-26419-03, rc1-26419-03, rc1-26419-02, servicing-26419-02, respectively (release/2.1) (#29185)
* Update BuildTools, CoreClr, CoreFx, CoreSetup, Standard to rc1-02719-01, rc1-26419-03, rc1-26419-03, rc1-26419-02, servicing-26419-02, respectively
* Fix ingestion of same-day NETCore.App package
Workaround issue where a local build of packages will have a lower version
than the closure of NETCore.App
|
|
|
|
* Ensure we use a unique path to package test semaphore
* Use Rid in semaphore filename instead of path
|
|
ProjectNTfsTestILC to preview3-02703-02, preview3-26403-06, preview3-26403-04, preview3-26403-03, beta-26403-00, beta-26403-00, respectively (master) (#28742)
* Update BuildTools, CoreClr, CoreFx, CoreSetup, ProjectNTfs, ProjectNTfsTestILC to preview3-02703-02, preview3-26403-06, preview3-26403-04, preview3-26403-03, beta-26403-00, beta-26403-00, respectively
* Adding suppresion for package downgrade on Microsoft.NETCore.Platforms
|
|
This target was only really for my testing and it accidentally made it to the final merge, so I'm reverting that piece now.
|
|
* Adding test execution to the allConfigurations leg
* Changing the root of tests to avoid long path issues
* Excluding NuGetFallbackFolder
* Test
* Fixing exclude so that NuGetFallbackFolder doesn't get copied
|
|
* Fix allocated Encoding memory initialization
We allocate native memory using GlobalHAlloc which usually doesn’t zero out the allocated memory and that cause a problem when using this memory. We fixed similar issue before in SBCS but looks we missed the DBCS one.
* Use Unsafe.InitBlockUnaligned
* remove un-needed empty line
* remove space
* Include System.Runtime.CompilerServices.Unsafe to inbox packag
* fix package build breaks
|
|
* Bump System.Data.SqlClient assembly version to 4.4.0.
Add UAP build configuration to SqlClient.
* Add build config for uap10.0.16299.
* Re-add uap to sqlclient package config.
|
|
|
|
Fix package testing infrastructure and fix issues.
|
|
* Support musl-libc based linux RIDs
- Add `linux-musl` RID
- Set `alpine`'s parent to `linux-musl`
- Add `alpine.3.7` to the graph
- Fix up `android` to inherit from `unix` while we are here
Fixes https://github.com/dotnet/core-setup/issues/3817
* Change linux-musl to be parented to linux.
* Reparent android RID to linux.
|
|
runtime-dependencies
|
|
|
|
|
|
Also continue on error.
|
|
|
|
We were skipping it because the condition was evaluating before references were resolved.
Conflict resolution was also knocking out files because we weren't setting SelfContained to turn off the platform manifest.
|
|
In netcoreapp2.0 the types in CoreLib were experimental and should not be exposed by System.Memory.
|
|
We need to account for source-build which sets the
OfficialBuildId property to replicate the official builds,
so we also look at the DotNetBuildOffline property to
determine that we should still build the all the packages.
|
|
release mode (#28608)
|
|
|
|
Exclude these from testing
|
|
|
|
|
|
System.Buffers ref to previously shipped version (#28428)
* Break netcoreapp20 build configuration from System.Buffers
* Build buffers with inbox frameworks using placeholders
* Update Compatibility pack System.Security.Cryptography.Cng to live prerelease dependency
* Update Compatibility Validation project and script to be able to restore for 2.1 and to include ASP.NET for ApiCatalog
* Merge conflicts and fix configurations to have ref harvested for all configurations
* Add netfx configuration to ref project for netfx vertical
* Remove not necessary build configurations
* PR Feedback
|
|
|
|
Add Xamarin placeholders for System.Memory package
|
|
|
|
|
|
|
|
* Update UAP targeting pack
To fix the flow from CoreCLR and CoreFX into TFS, update the targeting pack with a version of System.Private.CoreLib that has an updated signature for Stream.WriteAsync. This should be sufficient to re-enable uapaot builds so we can get a new set of uap packages.
* Revert "Disable uapaot builds on several projects"
This reverts commit ebe14686a89d26d1d34d359f7a636d6e9a36a624.
|
|
* 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
|
|
|
|
SystemEvents
|
|
This was needed to get through the change of Stream.WriteAsync's return type from Task to ValueTask.
|
|
* Build uapaot System.Numerics.Vectors
With `Vector<T>` now residing in System.Private.CoreLib, directly reference System.Private.Corelib instead of contracts just like netcoreapp does.
Add uapaot flavor since System.Private.CoreLib has a different strong name key on that platform.
* Make EnsureExtendedPrefixOverMaxPath available to UAP
Add the helper method `System.IO.PathInternal.EnsureExtendedPrefixOverMaxPath` to Common\src\System\IO\PathInternal.Windows.cs. It was previously not visible to UAP since Common\src\CoreLib\System\IO\PathInternal.Windows.cs is not included in UAP compilation.
* Keep SocketsHttpHandler out of UAP builds
SocketsHttpHandler is not supported in uap and is currently leaking into UAP builds since they've been disabled for a few weeks. Adjust the contract so it's not available to UAP, and clean the implementation assembly so SocketsHttpHandler internals don't leak out into HttpClientHandler.Core.cs.
* Fix GetAddrInfoExSupportsOverlapped UAP build break
`System.Net.NameResolutionPal.GetAddrInfoExSupportsOverlapped` uses LoadLibraryExW which is not compatible with UAP (which only supports LoadLibrary of DLLs within a container). Refactor the helper so UAP returns false.
* Revert "Disable UAP legs per #26802 (#26822)"
This reverts commit 120dce456a90df9982797d6c94eaaababd3e00d1.
* Revert "Disable UAP configurations in all configurations build"
This reverts commit 2202b4fd49ace58876763903f43cf27b2275c10a.
* Revert "Disable UAP official builds (#26871)"
This reverts commit ef79caf14cd922c8aa1a9aa280cbe503fdce26aa.
- Baseline the ApiCompat and GenFacades failures in System.Runtime.Extensions and System.Threading.ThreadPool.
- Adjust naming of files to match branch conventions
- Fix up some configuration issues with uap packaging. The CoreFX.Private.TestUtilities packaging needs updated build tools which can map between uwp6.0 and netstandard2.0.
- ifdef out Thread.GetCurrentProcessorId until we get a new System.Private.CoreLib.
|
|
Add support for queuing a stable package build
|
|
|
|
This change supports building corefx packages as stable by
passing in the StabilizePackageVersions=true property.
This does edit the package index in-place but that shouldn't
cause any problems for official builds are the only onces that
might do this. After we ship a stable set of packages the stable
versions should be commited to the repo in the package index.
There are a few scenarios:
1. Neither StabilizePackageVersions or PackageVersionStamp set
- Default dev state and all packages will have the prerelease label
that is committed in the repo and a build number.
2. StabilizePackageVersions=false, PackageVersionStamp='label'
- All packages will have prerelease label 'label' and build number
3. StabilizePackageVersions=true, PackageVersionStamp='label'
- Packages not marked BlockStable will have prelease label 'label'
and no build number
- BlockStable packages will have a prelease label 'label' and no build
number
4. StabilizePackageVersions=true, PackageVersionStamp=''
- Packages not marked BlockStable will not have a prelease label
or build number, and thus have a stable version.
- BlockStable packages will have the prelease label commited in the
repo and no build number
|
|
- Remove System.Runtime.Intrinsics from Microsoft.NETCore.App.
- Rename to System.Runtime.Intrinsics.Experimental
- Create a standalone nupkg.
|
|
* Add TestUtilities pkgproj and builds files
* Remove UAP Support
* Mark as not stable
* Remove IsNetCoreApp property
* Add netcoreapp2.0 definition
* Fix Indentation
|
