Uh oh!
There was an error while loading. Please reload this page.
Refactor wasmappbuilder's System.Text.Json reference to use a versions.props property - #70582
Conversation
… versions.props property
radical
commented
Jun 10, 2022
Why doesn't this fail for the non-source-build? Also, this needs to be tested on windows too. @lambdageek do you think this might cause any issues on windows? |
ghost
commented
Jun 10, 2022
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsThe current hardcoded version reference causes issues with source-build: Refactoring the wasmappbuilder.csproj to utilize a versions.props property for the System.Text.Json version will correct this issue.
|
radical
commented
Jun 10, 2022
Linux/AOT test failing with: |
radical
commented
Jun 10, 2022
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
lambdageek
commented
Jun 11, 2022
The issue on windows in the past was when we requested a version that was newer than what comes with the visual studio version of msbuild - which caused problems with running the task from inside VS. |
ghost
commented
Jun 28, 2022
This pull request has been automatically marked |
| <PackageReference Include="Microsoft.Build.Tasks.Core" Version="$(MicrosoftBuildTasksCoreVersion)" /> | ||
| <PackageReference Include="System.Reflection.MetadataLoadContext" Version="4.7.1" /> | ||
| <PackageReference Include="System.Text.Json" Version="6.0.0" PrivateAssets="all" /> | ||
| <PackageReference Include="System.Text.Json" Version="$(SystemTextJsonVersion)" PrivateAssets="all" /> |
There was a problem hiding this comment.
| <PackageReferenceInclude="System.Text.Json"Version="$(SystemTextJsonVersion)"PrivateAssets="all" /> | |
| <!-- When we requested a version that is newer than what comes with Visual Studio version of msbuild, it causes problems with | |
| running the task from inside VS. Therefore, we are using the moving version only for source-build. --> | |
| <PackageReferenceInclude="System.Text.Json"Condition="'$(DotNetBuildFromSource)' != 'true'"Version="6.0.0"PrivateAssets="all" /> | |
| <PackageReferenceInclude="System.Text.Json"Condition="'$(DotNetBuildFromSource)' == 'true'"Version="$(SystemTextJsonVersion)"PrivateAssets="all" /> |
@lambdageek this?
There was a problem hiding this comment.
That seems reasonable to me, thanks!
There was a problem hiding this comment.
I applied the suggested pattern.
ghost
commented
Jul 21, 2022
This pull request has been automatically marked |
| <PackageReference Include="Microsoft.Build.Tasks.Core" Version="$(MicrosoftBuildTasksCoreVersion)" /> | ||
| <PackageReference Include="System.Reflection.MetadataLoadContext" Version="4.7.1" /> | ||
| <PackageReference Include="System.Text.Json" Version="6.0.0" PrivateAssets="all" /> | ||
| <PackageReference Include="System.Reflection.MetadataLoadContext" Version="$(SystemReflectionMetadataLoadContextVersion)" /> |
There was a problem hiding this comment.
I realized we need to do the same for the MetadataLoadContext. Can this reference a shared versions.props property of should if follow the suggested source-build conditioned pattern?
MichaelSimons
commented
Aug 5, 2022
@kasperk81, @lambdageek - Any objects to merging this PR? |
radical
commented
Aug 5, 2022
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
The current hardcoded version reference causes issues with source-build:
Refactoring the wasmappbuilder.csproj to utilize a versions.props property for the System.Text.Json version will correct this issue.