I'm still experimenting with it. (I've been trying to convert some non-trivial projects from .net framework to .net core).
Yesterday most of the time, Slick wasn't getting those wildcards, then by the end of the day it was.
I'm not sure whats going on with it.
Once case it surely doesn't handle is paths with properties:
<ItemGroup>
<Compile Include="$(SOMEWHERE)\src\name.space\Dir1\*.cs" />
</ItemGroup>
I've also noticed that with just a simple project where it is supposed to take in all files recursively from the project down, it is also pulling in some temporary files.
I've found bugs in VisualStudio 2017 - it definitely gets confused sometimes when you edit the project - I've had to restart it to get it working right.