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
Duplicate 'Content' items were included: regression on 5.0.300 #17976
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
MSBUILD
|
Do you have a workaround @ForNeVeR? |
@ahmedalejo, sorry for the late answer. Here's my workaround. Essentially, add |
Could the issue be related to dotnet/msbuild#6235? Though it talks literally about |
You replied just in time! I couldn´t have asked for more. Thanks.
Thanks for the workaround.
|
Thank you for reporting the issue! It is indeed a recent MSBuild regression, now tracked in dotnet/msbuild#6502. |
Ok, I'll close this, then. Thanks a lot for taking a look! |
When building this project (see the specific commit), I'm getting the following error after updating to 5.0.300:
I have the following lines in the
.fsproj
file:From the error message, it looks like the files under
node_modules
without extension are now suddenly included asContent
by the SDK (as well as by my.fsproj
the second time), but everything else is still not.I've checked the
DefaultItems
files in the SDK and found no changes between 5.0.100 and 5.0.300. Is it possible that treatment for**
was changed in between the releases?Sdk.Razor.StaticAssets.ProjectSystem.props
has the following lines:sdk/src/RazorSdk/Sdk/Sdk.Razor.StaticAssets.ProjectSystem.props
Line 22 in 6accda8
Which is then used as following:
sdk/src/RazorSdk/Sdk/Sdk.Razor.StaticAssets.ProjectSystem.props
Line 30 in 6accda8
If this now only excludes files with extensions for some reason (i.e. only exclusion omits extensionless files, but inclusion by
**
still adds them), then this may've caused the issue.The text was updated successfully, but these errors were encountered: