Azure-devops-docs: Build fails, specified configuration is invalid

[kztd]

I tried building this with the following BuildPlatform's:
x86, x64
Any CPU
<blank>

and they all failed with a message like:

D:a1\s\cpp-sample.sln.metaproj (0, 0)
D:a1\s\cpp-sample.sln.metaproj(0,0): Error MSB4126: The specified solution configuration "debug, release|x64" is invalid. Please specify a valid solution configuration using the Configuration and Platform properties (e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU") or leave those properties blank to use the default solution configuration.

I also could not find Multi-Configuration on the Options tab, see 750, so I'm not sure why that would be closed. I'm also not seeing Multi-Configuration on any task as suggested in 749

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 02b0c082-81b3-79af-8841-8b3033dedf4a
• Version Independent ID: de8aab33-f9ef-0d8d-dbbc-49e23930f1c6
• Content: Build your Visual C++ app
• Content Source: docs/pipelines/apps/windows/cpp.md
• Product: devops
• GitHub Login: @andyjlewis
• Microsoft Alias: alewis

[DominicCabral]

Not to sure if this helps, but I've found that the msbuild task on the agents need you to explicitly set properties. For example, when I was building on my local machine, I was able to omit specifying my platform and it would use the default, but on the agent's I had to explicitly set /p:platform=x64 to avoid errors.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[thomps23]

Please accept our apology for the significant delay in addressing this issue.

It looks like you're working through an issue with the product itself, rather than an issue with the documentation. Here are a few options where you might consider asking your question:

• Azure DevOps on Stack Overflow
• Azure DevOps Support Bot

[ted-duncan]

This is still an issue - encountered it today even though the variable build.configuration is set in variables - seems like this would be low hanging fruit to implement and fix?

[bluebaroncanada]

Had this for two reasons:

• Forgot to commit the .sln file
• Compiling against the wrong branch when running the pipeline. Change the drop down to the right branch.