appveyor

We distribute a set of Visual Studio 2010 project files. Users are expected to upgrade to suit their taste. Our .appveyor.yml file includes the following images (in addition to configurations and platforms): Visual Studio 2017 Visual Studio 2015 Visual Studio 2013 Visual Studio 2012 Visual Studio 2010 The Visual Studio 2017 build failed with: Build started git clone -q --depth=3 --branch=master https://github.com/noloader/cryptopp.git C:\projects\cryptopp git checkout -qf 3504f1da2591d8b84e356527ed41dc6209eafa06 msbuild "C:\projects\cryptopp\cryptest.sln" /verbosity:minimal /logger:"C:\Program

Here is the behavior I'm trying to achieve in AppVeyor Build the code (stamp AssemblyInfo with 1.2.3.{build} ) Test the code Create the nuget package if the tests passed Publish the beta package if the package created successfully ( 1.2.3-beta-{build} ) Also make the package available in artifacts. Ideally when publishing a nuget package it would be published as prerelease. In NuGet, this is done by adding alpha characters to the end of the package version. It is also considered bad practice to overwrite an existing package (indeed, many nuget implementations do not allow this). AppVeyor does

Can someone point me towards a working example where packrat is used with AppVeyor to build an R package? Searching through Google and GitHub, I can't find any packrat-enable package that uses AppVeyor. Does the appveyor.yml file need to change? Are there some settings I need to add through the AppVeyor website? I have a very minimal package ( testthat is the only dependency) that broke AppVeyor builds. Here is the code frozen for that commit . Here is the AppVeyor log . (If this SO question sounds familiar, I'm about to ask a similar question for Travis-CI .) Ben Yes, the solution here is

I have a project that compiles with C extensions on Linux, but without them on Windows. When I first generated the wheel files on Windows with python setup.py bdist_wheel , they became universal, and I could not upload them to PyPI as these universal wheels are preferred by pip for installation over the .tar.gz uploads (the result from python setup.py sdist ). The trick around this was to specify in the setup.py : Distribution.is_pure = lambda *args: False or by subclassing Distribution : class BinaryDistribution(Distribution): def is_pure(self): return False and calling setup() in setup.py