-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[release/5.0.3xx] Update dependencies from dotnet/msbuild #16185
[release/5.0.3xx] Update dependencies from dotnet/msbuild #16185
Conversation
…0303.3 Microsoft.Build.Localization , Microsoft.Build From Version 16.10.0-preview-21126-01 -> To Version 16.10.0-preview-21153-03
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
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.
…0304.4 Microsoft.Build.Localization , Microsoft.Build From Version 16.10.0-preview-21126-01 -> To Version 16.10.0-preview-21154-04
@agocke @Forgind @benvillalobos single file test failed, could you look into this? |
We haven't made any changes to MSBuild that I know of, so my guess is that it's not a problem in runtime components |
…0304.5 Microsoft.Build.Localization , Microsoft.Build From Version 16.10.0-preview-21126-01 -> To Version 16.10.0-preview-21154-05
@Forgind @benvillalobos could you look into this issue soon? |
I looked at the test, but I wasn't sure what it was doing beyond that it was publishing something, and when I tried debugging, it came up with build errors?
Does that mean anything to you? |
CoreCompile target) -> the actual error instead of the warning is this. |
There appears to be a real bug here. I looked at the test
and a file |
So this is the commit that caused the regression:dotnet/msbuild@202f872 Here's the repro I used: <Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<OutputType>Exe</OutputType>
<TargetFramework>net5.0</TargetFramework>
<RootNamespace>console_template</RootNamespace>
</PropertyGroup>
<ItemGroup>
<Content Include="$(MSBuildThisFileDirectory)\SmallNameDir\**\*.*" >
<CopyToPublishDirectory>Always</CopyToPublishDirectory>
</Content>
</ItemGroup>
</Project>
Folder structure should be: repro cmd: We should seriously consider reverting the PR or if it's a quick fix then patch it. Not being able to merge into the SDK should put us 'on hold' until everything can flow. |
### Context #6151 introduced a regression where `FileMatcher` takes the pattern `*.*` too literally and returns only files that have a dot in the name. `*.*` should be special cased to mean all files in the directory, with or without an extension. ### Changes Made Fixed the regression by explicitly testing for `*.*` and added test coverage. ### Testing Existing and modified unit tests, repro project from dotnet/sdk#16185 (comment). ### Notes Testing for both `*` and `*.*` is already happening elsewhere in the class. MSBuild calls `Directory.EnumerateFileSystemEntries` which under the covers uses `MatchType.Win32` and causes this behavior of unifying `*.*` with `*` on all platforms.
Closing to pick up fix from msbuild/master |
This pull request updates the following dependencies
From https://github.com/dotnet/msbuild