Do not parse .vdproj as XML

[IlyaFinkelshteyn]

Discussion

[EckyZero]

This is affecting my build process as well. I've disabled the Installer project inside my Solution Configurations, but still AppVeyor is trying to build it. What's the work around while we wait on this feature?

[IlyaFinkelshteyn]

Will force it. @EckyZero do you have public repro by any chance to the the fix?

[EckyZero]

Yes - https://github.com/EckyZero/WCFRest_WindowsService

I got the build to continue by adding this to my appveyor settings

"C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv.exe" WcfRestfulWithWindowsHostDemo.sln /build Release

I'd still like the Installer file (DemoInstaller) to build though because I wanted the .msi file it generates. Thanks for the quick turn around @IlyaFinkelshteyn

I can find other artifacts in the build, but any output from the installer can't be found.

Found artifact 'WindowsService1\bin\Release\WindowsService1.exe' matching 'WindowsService1\bin\Release\WindowsService1.exe' path
No artifacts found matching 'DemoInstaller\Release\DemoInstaller.msi' path

[IlyaFinkelshteyn]

Fix we can do quickly is to stop parsing it as XML and do not feed to msbuild. If you still need to build it, you will be needed to feed it to devenv.exe or devenv.com yourself with custom build or after_build script.

[IlyaFinkelshteyn]

Fixed. No exception will be thrown, build will continue with warning like <project_name>.vdproj is not a valid MSBuild project. You probably have to create custom script based on 'devenv.com' to build it.