This repository was archived by the owner on Jan 23, 2023. It is now read-only.
[release/2.1] Lock Vectors reference assembly to 4.1.3.0 and don't OOB it on netcoreapp2.0#29182
Merged
ericstj merged 1 commit intodotnet:release/2.1from Apr 20, 2018
Merged
Conversation
…eapp2.0 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.
weshaggard
reviewed
Apr 18, 2018
| <PropertyGroup> | ||
| <PackageConfigurations> | ||
| netstandard1.0; | ||
| net45; |
Member
There was a problem hiding this comment.
do we need a net45 and net46?
Member
Author
There was a problem hiding this comment.
Yes, in net45 we need a versioned reference that's all typedefs. In net46 we need a versioned reference that has some typeforwards.
weshaggard
approved these changes
Apr 18, 2018
ericstj
changed the title
Member
Author
|
Test Linux x64 Release Build |
This was referenced Apr 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 roll forward: 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.
Fixes #29162