AppVeyor's MSBuild settings result in a .vdproj being read even though it's not part of the build
Hi,
I have a solution that includes an installer project (.vdproj). It does not get built by default; it's disabled in the solution configuration (Debug, Any CPU) that's used by the build. I've set the build up to point to the solution file and specify the configuration/platform explicitly. Still, when I try to build the solution using AppVeyor's MSBuild build mode, I get:
Project file "Alkahest.Installer.vdproj" is not a valid MSBuild project file which must be an XML.
If I switch to using a simple script that just invokes msbuild.exe manually, everything works fine. Why does AppVeyor think it needs to read the .vdproj when it's not being used?
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | 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
1 Posted by Ilya Finkelshte... on Apr 15, 2017 @ 03:38 AM
Hi Alex,
Thanks for the catch. Yes, we do our own solution parsing in
msbuildmode before startingmsbuild. We need this to enable many additional features like selective automatic web application packaging etc.I created this GH issue to fix it.
Ilya.
Ilya Finkelshteyn closed this discussion on Aug 25, 2018 @ 02:16 AM.