Windows 10 support?

Ankit's Avatar


27 May, 2015 08:02 PM


I was exploring AppVeyor as an CI solution for Windows 10 projects. Seeing Visual Studio 2015 support, I believed this was possible. I attempted running a blank universal app through AppVeyor but it failed to build.

Just wanted to know if Windows 10 is supported or if I messed up during the setup.


  1. Support Staff 1 Posted by Feodor Fitsner on 27 May, 2015 08:29 PM

    Feodor Fitsner's Avatar

    Hi Ankit,

    You should choose "Visual Studio 2015 RC" image in OS field on Environment tab of AppVeyor project settings.

    Then add this line to "Before build script" for using MSBuild 14.0:

    set PATH=C:\Program Files (x86)\MSBuild\14.0\Bin;%PATH%
  2. 2 Posted by Ankit on 27 May, 2015 09:40 PM

    Ankit's Avatar

    Hi Feodor,

    Thanks the quick response.

    I changed the OS from VS 2015 CTP 6 to VS 2015 RC and added the "Before build script". I am now seeing 'msbuild' is not recognized as an internal or external command.

    Kindly advise.

  3. 3 Posted by Ankit on 28 May, 2015 03:35 PM

    Ankit's Avatar

    Adding an echo %PATH% seemed to have resolved the %PATH% issue, then I was presented with error MSB4126: The specified solution configuration "Debug|Any CPU" is invalid. Switching the solution to build x86 brought me back to square one as attached.

    Kindly advise.

  4. Support Staff 4 Posted by Feodor Fitsner on 28 May, 2015 05:35 PM

    Feodor Fitsner's Avatar

    Hm, that's interesting. I have vanilla clean install of Visual Studio Community 2015 (Typical configuration) on my Windows 8.1 machine and have only these folders:

    C:\Program Files (x86)\MSBuild\Microsoft\WindowsXaml\v14.0\8.0
    C:\Program Files (x86)\MSBuild\Microsoft\WindowsXaml\v14.0\8.1

    Do I have to be on Windows 10 for that 8.2 folder to be installed?

  5. 5 Posted by Ankit on 28 May, 2015 05:57 PM

    Ankit's Avatar

    Hey Feodor,

    That seems to be the case, see screenshots from the AppVeyor instance and my local machine (running windows 10).

    Does that mean that AppVeyor doesn't currently support Windows 10 universal app builds?


  6. Support Staff 6 Posted by Feodor Fitsner on 28 May, 2015 06:00 PM

    Feodor Fitsner's Avatar

    If Windows 10 is required then yes it's not supported (yet).

    However, you may try packaging those .targets files along with required assemblies into zip (preserving folders structure), put it somewhere on the net and then download/unpack during the build.

  7. 7 Posted by Breno on 24 Jun, 2015 05:14 AM

    Breno's Avatar


    Will besupported soon?

  8. Support Staff 8 Posted by Feodor Fitsner on 24 Jun, 2015 05:32 PM

    Feodor Fitsner's Avatar

    I think Windows 10 might be available as "bring your own custom image" option.

  9. 9 Posted by Breno on 25 Jun, 2015 05:16 AM

    Breno's Avatar

    There is no need to have Windows 10 to Build UWP Apps. :)

    Yes, you can build Windows 10 apps on Windows 8.1.

    You just need check "Universal Windows App Dev Tools" on VS 2015 RC Install and Voilà, it's ready to build.

    Check my attached demo. It;s a Windows 8.1 + Clean Install VS 2015 RC (with the option) Building a Universal Plataform App.


  10. Support Staff 10 Posted by Feodor Fitsner on 25 Jun, 2015 05:26 AM

    Feodor Fitsner's Avatar

    Cool, so basically we don't need Windows 10 per se, right (unless for integration tests)?

  11. 11 Posted by Breno on 25 Jun, 2015 01:15 PM

    Breno's Avatar

    You don't Windows 10 neither in tests because the Windows 10 emulator starts, do the work and close.



  12. 12 Posted by Breno on 25 Jun, 2015 04:48 PM

    Breno's Avatar

    Do you guys can make this little change? o/

  13. Support Staff 13 Posted by Feodor Fitsner on 25 Jun, 2015 10:23 PM

    Feodor Fitsner's Avatar

    Will take a look.

  14. Support Staff 14 Posted by Feodor Fitsner on 25 Jun, 2015 11:33 PM

    Feodor Fitsner's Avatar

    Are you sure emulator can be started on a virtual machine?

  15. 15 Posted by jernej.kavka on 02 Aug, 2015 10:16 PM

    jernej.kavka's Avatar

    Is there any progress regarding building UWP?

  16. Support Staff 16 Posted by Feodor Fitsner on 02 Aug, 2015 10:31 PM

    Feodor Fitsner's Avatar

    Will be available early next week.

  17. 17 Posted by jernej.kavka on 05 Aug, 2015 09:07 PM

    jernej.kavka's Avatar

    Thanks, much appreciated. :)

  18. Support Staff 18 Posted by Feodor Fitsner on 10 Aug, 2015 04:24 AM

    Feodor Fitsner's Avatar

    It's been deployed.

  19. 19 Posted by peter.dunshee on 10 Aug, 2015 05:23 PM

    peter.dunshee's Avatar

    Were others here able to get this working? Something still seems missing for me. For me, on even a fresh solution with just a UWP project, it fails to find the assemblies it needs to build the project. (On a blank app, no changes, it complains about System.Runtime.dll; on a real project, many many more) It looks like the 8.2 targets files are present, and the 14.0 tools are running, but assemblies are missing.

  20. Support Staff 20 Posted by Feodor Fitsner on 10 Aug, 2015 05:24 PM

    Feodor Fitsner's Avatar

    Do you run it on Visual Studio 2015 image?

    - Feodor

  21. 21 Posted by peter.dunshee on 10 Aug, 2015 05:32 PM

    peter.dunshee's Avatar

    Yes, the "os" field in the yml file is "Visual Studio 2015". It does look like it's taking an extra 30 seconds or so to spin up, so as far as I can see, that setting is doing something. I've attached the log if that helps.

  22. Support Staff 22 Posted by Feodor Fitsner on 10 Aug, 2015 05:38 PM

    Feodor Fitsner's Avatar

    Yes, that's correct. It takes 30-40 seconds to boot up custom image with VS 2015.

    Could you better provide a simple example app in a public repo, so I can play with it too?

  23. 23 Posted by peter.dunshee on 10 Aug, 2015 06:57 PM

    peter.dunshee's Avatar

    Okay, I have a min-repro for you. The repository is at:

    And it gets the same error message. I'm attaching the log from the last build also.

  24. 24 Posted by jernej.kavka on 10 Aug, 2015 08:24 PM

    jernej.kavka's Avatar

    I have issues with this error:
    [00:00:10] C:\Program Files (x86)\MSBuild\Microsoft\NuGet\Microsoft.NuGet.targets(83,5): error : The package Microsoft.CSharp with version 4.0.0 could not be found in C:\Users\appveyor\.nuget\packages. Run a NuGet package restore to download the package. [C:\projects
    [00:00:10] \universalgallerydemo\UniversalGalleryDemo.Core\UniversalGalleryDemo.Core.csproj]

    This is the only solution I was able to find:

    My source is located here if it helps:

    @PeterD this might be because default arhitecture is selected as Any CPU instead of x86/x64/ARM. But there are also other scenarios where this issue occurs.

  25. Support Staff 25 Posted by Feodor Fitsner on 10 Aug, 2015 08:49 PM

    Feodor Fitsner's Avatar

    Apparently, the environment is not "broken". After logging to build worker via RDP and opening AppVeyorUWPBuildTest project in VS 2015 IDE I was able to build it. However, before compiling VS restored whole bunch of nuget packages.

    So, the question is "how to restore missing packages with runtime and dependencies command line". Is it either nuget 3.0 (command line?) or dnu? I'm still trying to figure out...

  26. 26 Posted by peter.dunshee on 10 Aug, 2015 08:54 PM

    peter.dunshee's Avatar

    I was starting to wonder that too. On UWP, .NETCore comes from nuget (somehow, not in the normal way in the "packages" folder). However, from a clean directory, it seems to work successfully on an MSBuild command prompt with no "nuget restore" and simply (from the root directory):

    msbuild /p:Configuration=Release /p:Platform=ARM TestApp\TestApp.sln

  27. Support Staff 27 Posted by Feodor Fitsner on 10 Aug, 2015 08:57 PM

    Feodor Fitsner's Avatar

    Maybe there should be some env variable set to "enable" command line restores?

  28. Support Staff 28 Posted by Feodor Fitsner on 10 Aug, 2015 09:10 PM

    Feodor Fitsner's Avatar

    OK, the secret recipe was NuGet 3.0! Look here:

    It works like a charm with this appveyor.yml replacing nuget.exe with 3.0:

    Build results: - missing .snk is the only problem there.

  29. 29 Posted by aleksandar.topl... on 11 Aug, 2015 06:05 PM

    aleksandar.toplek's Avatar

    Thanks for implementing uwp support! It all works great at our end with that last nuget fix.

  30. 30 Posted by peter.dunshee on 11 Aug, 2015 06:40 PM

    peter.dunshee's Avatar

    Yes, thank you! I just had one more adjustment to make, and it was all

    For future, if others run into this, nuget 3.1 keys off of the
    Configuration and Platform environment variables, and if you have a project
    that doesn’t have one of those named explicitly, it will fail with an error
    code, which will fail the build. I just made a powershell script to
    temporarily reset those variables prior to “nuget restore”, and set them
    back again afterwards, and everything works.

Comments are currently closed for this discussion. You can start a new one.

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