VS build fails if vcxitems project is included

qwertiest's Avatar


18 Jun, 2022 07:00 PM

I have a VS solution, to which I've added a `Shared Project` (which is defined by .vcxitems file).
I've commited this change and have launched an AppVeyor build.

Expected behavior: build finished successfully.

Actual behavior: build fails with the following error `The project file "(..).vcxitems" is in the ".vcproj" file format, which MSBuild no longer supports. Please convert the project by opening it in the Visual Studio IDE or running the conversion tool, or use MSBuild 3.5 or earlier to build it.`

Example of the failing build: https://ci.appveyor.com/project/TheQwertiest/foo-spider-monkey-panel/build/job/5wqei39wrt0vxc44#L167

PS: I've found a similar bug report from 2019: https://help.appveyor.com/discussions/problems/24543-upgrading-to-visual-studio-2019-breaks-build
But I didn't try the suggested workaround, because it seems really hacky.

  1. Support Staff 1 Posted by Feodor Fitsner on 20 Jun, 2022 05:33 PM

    Feodor Fitsner's Avatar

    Have you fixed it? What was the fix?

  2. 2 Posted by qwertiest on 25 Jun, 2022 08:03 PM

    qwertiest's Avatar

    I've added the same hacky workaround as in the linked thread: https://github.com/TheQwertiest/foo_spider_monkey_panel/commit/6e1d933b19c12e280db9e44c3d905739616cb1bd

    It feels like MSBuild detection is failing somewhere, which causes the agent to use the wrong version (esp. since the build works fine locally and when invoked manually through msbuild on agent).

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac