Upgrade to .NET 6 #166
Merged
Upgrade to .NET 6 #166
Conversation
This file contains 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
|
@kkm000, @dsyme, @sergey-tihon I'm still quite interested in a new release. |
|
Current tools build with I do not mind (personally) do upgrade to .NET 6, just would be nice to confirm with @dsyme that it works for compiler repo. |
Nope, I used the library (netstandard). The F# compiler uses this tool as net7.0 so I don't think there is any harm here. |
sergey-tihon
reviewed
Jan 6, 2023
|
Great, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hello, I've upgraded the SDK and some of the projects to dotnet 6:
netcoreapp3.1is nownet6.0Fake.DotNet.Cliusage in the FAKE scripts. I'm hitting DotNet.publish fails attempting to load Microsoft.Build.Framework, Version=15.1.0.0 FAKE#2722.fsfiles that had mismatched parameter names with the signature file.