graphBuild option not working in my soltion

### Issue Description

Using 16.11.0.36601 version of MsBuild, the graphBuild is not working. It has something to do with this:
1. When attempting to build a specific .csproj of a solution, there's not enough options to specify that we want to use the "Release|Any CPU" configuration because it wants to use "AnyCPU" instead without spaces. Although when specifying AnyCPU works, the dependent C++ projects that rely on the "Any CPU" target fail, so they don't build. The error message suggests to specify the solution.
2. However, when specifying the solution, it doesn't work because our project names have dots in the names. The documentation states that dots should be converted to underscores, but doing this doesn't work.

I'm just trying to determine what the dependencies are of a given .csproj programmatically. The solution has a combination of .NET Framework and C++, and some of the projects are SDK projects, while others are not. Visual Studio, and MSBuild on the build server is clearly capable of of figuring out dependencies since the solution builds, but on the build server, ms build runs the entire solution.

I'd like to know what the rules are that will effectively determine the full dependency tree of a project, just like Visual Studio can do -- and supposedly MSBuild can do. I'd like to do it without modifying the solution (it belongs to a client and I'd like to avoid changing the solution / project structure if at all possible)

### Steps to Reproduce

Before I come up with steps to reproduce, which would take me a little while, I'd like first find out if the scenario I'm talking about is supposed to work. For instance, if .NET Framework, C++ or non-SDK projects are not supported for the "graphBuild" parameter, then I want to avoid wasting the effort to construct a reproducible case. So someone gets back to me and let me know if this is even a target / goal of this project.

### Expected Behavior

### Actual Behavior

### Analysis

### Versions & Configurations

### Attach a binlog