You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently upgrading roslyn bits for dotnet/razor is a manual process and it used to be a straightforward upgrade as seen in #8443. In contrast dotnet/runtime has it automatically using bot to upgrade dotnet/runtime#85460
The PR #8492 made changes to add explicit dependencies and explicit properties that match those dependencies into the repo. This is required for source-build to work correctly.
Currently getting the dependencies and resolution aren't very straightforward and upgrading roslyn bits causing version downgrades, needs further investigation.
Dependencies can be easily upgraded using darc. Here's a command that would make the necessary changes in all required files, i.e. Version.details.xml and Versions.props:
Regarding package downgrade - this would be unrelated to the changes I made for source-build. Every package upgrade could cause a conflict with versions of transitive dependencies. The fix usually requires updating the version of the offending dependency. Here's an example of a fix for a similar issue I recently did: microsoft/vstest@37acc70
Currently upgrading roslyn bits for dotnet/razor is a manual process and it used to be a straightforward upgrade as seen in #8443. In contrast dotnet/runtime has it automatically using bot to upgrade dotnet/runtime#85460
The PR #8492 made changes to add explicit dependencies and explicit properties that match those dependencies into the repo. This is required for source-build to work correctly.
Currently getting the dependencies and resolution aren't very straightforward and upgrading roslyn bits causing version downgrades, needs further investigation.
cc @NikolaMilosavljevic
The text was updated successfully, but these errors were encountered: