You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does not print anything. All included Test items are immediately excluded.
Actual Behavior
Prints dir\subdir\file2.
Analysis
This is another issue with taking *.* too literally. In this case the default filespec is added when parsing **\subdir\** which is understood as **\subdir\**\*.* and files are matched against the actual . dot.
Versions & Configurations
Introduced in 16.10.
The text was updated successfully, but these errors were encountered:
All except the .well-known isn´t include when published.
It also shows as hidden in vs explorer as well.
It looks like it is now not being added by default.
I will try adding back <Content Include="wwwroot\.well-known\**" />
I removed this initially due to this bug (i.e. #17976)
MSBUILD
on Azure DevOps agent.
✔Microsoft (R) Build Engine version 16.10.1+2fd48ab73 for .NET publish includes wwwroot/.well-known folder
❌Microsoft (R) Build Engine version 16.10.2+857e5a733 for .NET publish does not includes wwwroot/.well-known folder
@ahmedalejo thank you for reporting this. The new behavior is actually by design and what you're seeing with 16.10.1+2fd48ab73 was a bug. Apologies for the inconvenience. I've left a comment in #6708.
Issue Description
A regression introduced in #6151.
Reported by @ForNeVeR in dotnet/sdk#17976.
Steps to Reproduce
Use an exclude glob that looks like
**\subdir\**
and have a file without extension under asubdir
subdirectory.Example:
With a file structure as follows:
Expected Behavior
Does not print anything. All included
Test
items are immediately excluded.Actual Behavior
Prints
dir\subdir\file2
.Analysis
This is another issue with taking
*.*
too literally. In this case the default filespec is added when parsing**\subdir\**
which is understood as**\subdir\**\*.*
and files are matched against the actual.
dot.Versions & Configurations
Introduced in 16.10.
The text was updated successfully, but these errors were encountered: