Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Arcade 6.0.0 error
See original GitHub issueIssue Analytics
- State:
- Created 2 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
error MSB4236: The SDK 'Microsoft.DotNet.Arcade. ...
Description: I faced below error while building runtime ... DotNet.Arcade.Sdk with version (= 6.0.0-beta.20601.2) /home/amd/manoj/pr...
Read more >2005 golden tee key mismatch
6.0.0 up top software #40600 (which seems to mean complete software) hardware #50500 reboots w/ 05 extra hdd I get golden tee fore!...
Read more >r/vitahacks [Release] RetroFlow-Launcher Version 6.0.0
Bug fixes. File settings error: Fixed error saving when pressing buttons repeatedly very quickly. PSP and PS1: Fixed error with bad game ......
Read more >Is Anyone Else getting this error on their phones?
Today I got this error when I built a construct 3 game with minimum OS version 6.0.0: "Software update needed".
Read more >c# - How to install Microsoft.DotNet.Arcade.Sdk into the ...
Arcade.Sdk 6.0.0 to be installed inside "C:\Program Files\dotnet\sdk\5.0.101\Sdks\Microsoft.DotNet.Arcade.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@Haplois I’m going to close this issue then. If you have any other problems, feel free to re-open it.
It’s not going to be a straightforward upgrade so I’m not surprised that you’re seeing breaking changes. Arcade has changed a lot of things between what is produced by the 3.x (1.0.x) branch and what is produced by main (6.0.x).
I suggest reverting that change and staying in the 3.x channel until you have some time to go through all the errors that will surface in your official build. This error in particular is due to the changes that we have made to make how we publish packages uniform across all of .net. Since you don’t use any of the arcade build scripts to build, components of the build that the infrastructure expects are not there. In this case, nothing is calling the “PushToAzureDevOpsArtifacts” task that would’ve placed the manifests and assets in the right location.
Basically, this repository was only using some pieces of arcade, and the way that you glued them together to sort of work doesn’t anymore.
There are three paths forward:
We have a guide on how to onboard to using the publishing infrastructure here: https://github.com/dotnet/arcade/blob/main/Documentation/CorePackages/Publishing.md#basic-onboarding-scenario-for-new-repositories-to-the-current-publishing-version-v3 but it assumes that you are using the Arcade SDK to build your repo.
This guide: https://github.com/dotnet/arcade/blob/e7ede87875f41a9b3df898ae08da5ebc96e24f56/Documentation/DependencyFlowOnboardingWithoutArcade.md#creating-a-manifest might also provide some help to onboard onto the publishing infrastructure without using the Arcade SDK