Revert Linq Version change 4.1.2.0 → 4.2.0.0 *no merge*#14479
Revert Linq Version change 4.1.2.0 → 4.2.0.0 *no merge*#14479JonHanna wants to merge 1 commit intodotnet:masterfrom
Conversation
| <PropertyGroup> | ||
| <OutputType>Library</OutputType> | ||
| <AssemblyVersion>4.2.0.0</AssemblyVersion> | ||
| <AssemblyVersion>4.1.2.0</AssemblyVersion> |
There was a problem hiding this comment.
This line was added in #13726. Maybe removing will fix the failures?
| <ProjectGuid>{CA488507-3B6E-4494-B7BE-7B4EEEB2C4D1}</ProjectGuid> | ||
| <AssemblyName>System.Linq</AssemblyName> | ||
| <AssemblyVersion>4.2.0.0</AssemblyVersion> | ||
| <AssemblyVersion>4.1.2.0</AssemblyVersion> |
There was a problem hiding this comment.
This line was also added in #13726. Maybe removing will fix the failure?
|
I'm guessing |
0fcbc4a to
00b5c45
Compare
|
It did. I can build locally if I change the reference in System.Linq.Tets.csproj from referencing ..\pkg\System.Linq.pkgproj to referencing ..\src\System.Linq.csproj. What further implications there? |
|
Have you tried reverting the change to packageIndex.json? I didn't see it in the diff here. |
00b5c45 to
0cb0dfb
Compare
|
Oh for goodness sake. I did, but then committed from too deep a directory and it didn't get included 😊 |
|
It would seem some change to layout/Microsoft.Private.CoreFx.NETCoreApp/Microsoft.Private.CoreFx.NETCoreApp.pkgproj or rather something(s) it pulls in needs to be changed. @ericstj ? |
|
None of these are related to the index. These are all problematic. Those errors are occurring when I do a closure walk of the final output. These are ref-def mismatches in the final package set that will cause runtime issues. They're happening because each of these libraries is building against the old packages. We could fix them all by adding p2p references but that is going to be painful. I'm tempted to leave this as it is. If we want to make this change that will be much easier once dev/eng work is done. |
This is failing for me locally, but a comment by @ericstj leads me to suspect maybe that is to be expected. It certainly shouldn't be merged until CI is definitely cleared though.