tag:help.appveyor.com,2012-11-13:/discussions/problems/24543-upgrading-to-visual-studio-2019-breaks-buildAppVeyor: Discussion 2020-04-03T18:44:55Ztag:help.appveyor.com,2012-11-13:Comment/474628502019-07-23T10:15:14Z2019-07-23T10:15:14ZUpgrading to Visual Studio 2019 breaks build<div><p>I've found a thread that looks like it could be related, but I am not using Nuget packages, so this doesn't apply: <a href="https://help.appveyor.com/discussions/problems/1239-how-to-get-more-logs-for-exception-has-been-thrown-by-the-target-of-an-invocation-errors#comment_35592708">https://help.appveyor.com/discussions/problems/1239-how-to-get-more...</a></p></div>Janos Turanszkitag:help.appveyor.com,2012-11-13:Comment/474628502019-07-23T21:05:37Z2019-07-23T21:05:38ZUpgrading to Visual Studio 2019 breaks build<div><p>I don't understand why it wants to build the vcxitems project that it mentions, it is a shared files project that doesn't participate in the build. I tried randomly making some changes in project files and solution that trigger a build and lets me check, but it always fails (but only on Appveyor). It is really annoying. I will switch back to VS 2017 build and wait for a fix.</p>
<p>Here is a link to a failed build job: <a href="https://ci.appveyor.com/project/turanszkij/wickedengine/builds/26172910/job/0ltjcn9i0oj8pj0m">https://ci.appveyor.com/project/turanszkij/wickedengine/builds/2617...</a></p></div>Janos Turanszkitag:help.appveyor.com,2012-11-13:Comment/474628502019-07-23T21:59:33Z2019-07-23T21:59:34ZUpgrading to Visual Studio 2019 breaks build<div><p>Switching to Visual Studio 2019 Preview version in the yml and rebuilding doesn't trigger this error, but the build fails somewhere else:</p>
<p>C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2817,7): error MSB4057: The target "CreateManifestResourceNames" does not exist in the project. [C:\projects\wickedengine\WickedEngine\WickedEngine_UWP.vcxproj]</p>
<p>Link to the failed job with VS 2019 preview: <a href="https://ci.appveyor.com/project/turanszkij/wickedengine/build/job/xhvqqm4lv2w3l6m0">https://ci.appveyor.com/project/turanszkij/wickedengine/build/job/x...</a></p></div>Janos Turanszkitag:help.appveyor.com,2012-11-13:Comment/474628502019-07-23T22:02:12Z2019-07-23T22:02:12ZUpgrading to Visual Studio 2019 breaks build<div><p>I cloned your repo and tried using <code>devenv \upgrade</code> command to no avail.</p>
<p>What do you mean by "doesn't participate in the build"? On your local build, what happens if you remove the vcxitems project files?</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/474628502019-07-23T22:52:56Z2019-07-23T22:52:57ZUpgrading to Visual Studio 2019 breaks build<div><p>The vcxitems project doesn't contain any build information, just .h and .cpp files, that will be built by an other project that references it, either WickedEngine_Windows.vcxproj or WickedEngine_UWP.vcxproj. So it doesn't make sense to remove this file. Did you try building the repo locally? Because I can build locally, but not with appveyor.<br>
Thanks for looking into this.</p></div>Janos Turanszkitag:help.appveyor.com,2012-11-13:Comment/474628502019-07-23T23:41:31Z2019-07-23T23:41:31ZUpgrading to Visual Studio 2019 breaks build<div><p>Can you <a href="https://www.appveyor.com/docs/how-to/rdp-to-build-worker/">RDP</a> to build worker and see if you can build the project following the same steps you do on your local machine.</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/474628502019-08-31T19:23:54Z2019-08-31T19:23:56ZUpgrading to Visual Studio 2019 breaks build<div><p>Hi, I've tried to RDP into a build worker (sorry for taking so long), but I can build the project just fine there. I tried opening Visual Studio 2019, and doing a "Rebuild Solution". I also tried opening Developer command prompt for Visual Studio 2019 and entering msbuild WickedEngine.sln, seems to build fine.</p>
<p>However, appveyor build still gives me the error ".vcproj file format" like in the aboce posts, so I think it must be an appveyor specific issue. What is appveyor doing when trying to build my project?</p></div>Janos Turanszkitag:help.appveyor.com,2012-11-13:Comment/474628502019-09-18T23:02:39Z2019-09-18T23:02:41ZUpgrading to Visual Studio 2019 breaks build<div><p>Hi,<br>
Is there any update on this? I am still looking to upgrade to VS 2019, but this issue with appveyor build system is currently blocking me.</p>
<p>Thanks,<br>
Janos</p></div>Janos Turanszkitag:help.appveyor.com,2012-11-13:Comment/474628502019-09-19T03:54:47Z2019-09-19T03:54:47ZUpgrading to Visual Studio 2019 breaks build<div><p>Sorry for the delay on this, it got buried under some other issues.</p>
<p>Can you try to remove the <code>build:</code> section of your config and add a <code>build_script:</code> section with the following<br></p>
<pre>
<code>build_script:
- msbuild "C:\projects\wickedengine\WickedEngine.sln" /m /verbosity:minimal /logger:"C:\Program Files\AppVeyor\BuildAgent\Appveyor.MSBuildLogger.dll"</code>
</pre>
<p>Let us know if that still returns this error.</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/474628502019-09-19T19:06:01Z2019-09-19T19:06:02ZUpgrading to Visual Studio 2019 breaks build<div><p>Hi Owen,</p>
<p>Thanks a lot for the support and no worries! I have tried your suggestion, and confirm that it works well. I am happy with this workaround. However, I would be still interested in going back to the standard solution, so please let me know if the Appveyor team implements a fix for my problem.</p>
<p>Best regards,<br>
Janos</p></div>Janos Turanszkitag:help.appveyor.com,2012-11-13:Comment/474628502019-09-20T16:28:59Z2019-09-20T16:28:59ZUpgrading to Visual Studio 2019 breaks build<div><p>We'll definitely be looking into it. I'll update here with findings when we have them.</p></div>Owen McDonnell