No, not exactly. In my experience, if you have the recursive wildcard in there and then add a new file from within VS, it'll put it in as an explicit entry next to the implicit wildcard. Then, next time you open the project, it'll import the file twice (once via the wildcard and once explicitly) and fail to build because "your class is defined twice."
I've always found it weird that they don't fix this, especially given how easy the fix seems to be:
1. When a file is added, VS could re-run the wildcard matches to see if they match the new file. If they do, don't add an explicit entry.
2. VS could turn the file list into a unique file list before passing it to the compiler.
