Silentsetupfor winget#616
Merged
Merged
Conversation
Nuke's MSBuild() task resolves the Visual Studio-bundled MSBuild via vswhere. On the GitHub windows-latest runner that is VS 2022 (MSBuild 17.x), which Nuke rejected for this net10.0 solution with 'Could not find a suitable MSBuild instance', failing the release at Restore. Switch Restore/Compile and the PluginRegistry rebuild to DotNetRestore/DotNetBuild so the build uses the .NET 10 SDK (installed via setup-dotnet), which understands net10.0. Verified locally: Restore+Compile succeed, output builds as Any CPU (MSIL) as before, and pluginsx86 are produced.
…/LogExpert into silentsetupfor_winget
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Nuke Build wont build with correct MSBUILD