I have a reasonably big solution comprised of a couple of Visual Micro projects, shared projects and a few other things. Most of the shared code is in a Shared Project called Melvyn. Recently I decided I would like to break the Melvyn project up into parts for greater granularity. 

So I started with:
* Config Arduino (SP)
* Melvyn (SP)
* Clacks (VM)

(VM) means a Visual Micro project with an .ino file. (SP) means a shared project. Both shared projects are referenced by the Clacks project. 

This works nicely. 

I added another shared project called "Melvyn Cache". I can call it MelvynCache or MelvynCache2 and I get the same result. The build fails with the compiler unable to find files in this new project. 

Delving into the temporary folder where the files are assembled for the build I discovered the reason. I see the structure:
Clacks
+ (board name)
++ Release
+++ Files from the "Melvyn" and "Config Arduino" shared projects as well as the Clacks project.
++ Release Cache
+++ Files from the "Melvyn Cache" project. 

So the build is failing because the files from the "Melvyn Cache" shared-project aren't getting put into the Release folder where the build is happening. Rather they go to a folder of their own. I get the same problem whether the shared project includes a space in the name or not. 

If I call my new shared project "Cache" instead of "Melvyn Cache" (or the other alternatives I tried), it all works as expected. 

I looked in the Clacks.vcxproj file and the shared project imports are consistent. Nothing weird in any of the .vcxitems files either. 

So somehow weird things happen when shared projects share a common prefix. Its not a big deal to give them different names. Though I'm not sure how different they have to be. I haven't tried to see what happens if two projects start with the same letter, for example. 

I'm using Version 15.2 (26430.6) Release of Visual Studio & Version 1707.25.5 of Visual Micro. 

Have others seen this problem? I didn't spot anything similar when searching the forum. 

Any insights appreciated!
Have a great day
Paul.