Hi,

Thanks for the post.

It's an interesting discussion.

The "File>New>Project" command is entirely within the control of Visual Studio, we simply use a new project template. It appears to be a failing of Visual Studio to cater for this scenario. As you can see it attempts to add a file called "foo_foo.ino" (which it fails to create) to the project which it happily creates called "foo.foo.vcxproj".

I tested the "File>New>Arduino Project" which is Visual Micro code and it worked okay.

As an aside, I would not recommend adding a "." to an arduino file name. Some platforms are very sensitive about the final program names (.elf, .hex files) and the program names are always derived from the name of the [project_name].ino

In the Arduino world it would be illegal for the main Arduino.ino to have a different name to the containing folder. That is how arduino determines a valid project and a rule that Visual Micro also enforces. 

In fact Visual Micro will "go to sleep" for any project name that does not have a matching .ino located in a matching folder name because that is how arduino should work