Skip to content
This repository has been archived by the owner on Aug 2, 2023. It is now read-only.

Removing RuntimeFrameworkVersion and the workaround added in PR #1702. #1735

Merged
merged 7 commits into from
Sep 13, 2017

Conversation

ahsonkhan
Copy link
Contributor

@ahsonkhan ahsonkhan commented Aug 30, 2017

With the latest packages, we can remove the previously added workaround in PR #1702.

This will resolve the errors we see here (#1703) like:
error CS0012: The type 'ValueType' is defined in an assembly that is not referenced. You must add a reference to assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. [D:\j\workspace\windows_nt_de---4b678204\tests\System.Binary.Tests\System.Binary.Tests.csproj]

https://ci.dot.net/job/dotnet_corefxlab/job/master/job/windows_nt_debug_prtest/649/

However, the new packages reveal a new issue that needs to be resolved: https://github.com/dotnet/corefx/issues/23656

Do not merge until the above issue has been resolved.

cc @shiftylogic, @KrzysztofCwalina

@ahsonkhan
Copy link
Contributor Author

@dotnet-bot test this please

@ahsonkhan
Copy link
Contributor Author

This PR is superseded by #1736.

Keeping it open for now to make sure tests still pass when targeting netcoreapp2.0. I will close this PR once #1736 gets merged.

@ahsonkhan
Copy link
Contributor Author

Since #1736 is still blocked on new cli, I will merge this change in so we can get the latest changes from System.Memory/etc.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Using latest System.Memory package with netcoreapp2.0 fails due to S.N.V depenedency
3 participants