[WIP] Use PackageReferences in libraries #34893
Conversation
|
Tagging @ViktorHofer as an area owner. If you would like to be tagged for a label, please notify danmosemsft. |
ViktorHofer
changed the title
| <SystemDiagnosticsDebugVersion>4.3.0</SystemDiagnosticsDebugVersion> | ||
| <SystemDiagnosticsTracingVersion>4.3.0</SystemDiagnosticsTracingVersion> | ||
| <SystemDynamicRuntimeVersion>4.3.0</SystemDynamicRuntimeVersion> | ||
| <SystemMemoryVersion>4.5.3</SystemMemoryVersion> |
There was a problem hiding this comment.
Looks like these aren't the newest versions /cc @joperezr
There was a problem hiding this comment.
That's correct, they aren't. How did you get these reference numbers @ViktorHofer? From looking at Darc, it seems like release/2.1 branch in corefx (where System.Memory is built and shipped) doesn't have a default channel any longer, which would explain why we didn't get the new one if we used dependency flow. I would suggest two things: one is to update that channel to have all serviced package versions from 2.1, and the other one is to run my validation task somewhere in the build to make sure that these package versions are still the latest.
ghost
locked as resolved and limited conversation to collaborators
Contributes towards #31844 and #31872.
Unsure what we should do with .NET Framework testing. Still build the testhost or switch to a "self-contained" mode.
cc @ericstj @safern @Anipik