-
Notifications
You must be signed in to change notification settings - Fork 662
(deps): Bump Buildalyzer from 3.2.2 to 3.2.6 #2947
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@asbjornu @arturcic
The "or" should be "and". Some unit tests failed on local machines.
Why not use some config for all targetFrameworks?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you mean?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some unit tests failed on my local machine, which environment is Windows 10 and Visual Studio 2022. The reason is the Buildalyzer 3.2.5 reference to Microsoft.Build.dll version 16. So the project references to Microsoft.Build.dll version 16 and Microsoft.Build.Framework.dll version 17. But I'm confused why the CI is success.


I don't know why you use different package versions for .net core 3.1 and net5.0 in commit bb243bc
But I founded that the failed unit tests run success by replacing
with
.
<PackageReference Include="Microsoft.Build.Framework" Version="17.0.0" />is added to fix the version conflict of Microsoft.Build.Framework.dll and Microsoft.Build.