Appveyor builds have stopped working due to Cake.Core version

Scott's Avatar


28 Feb, 2018 02:09 PM

We have recently got the issue of Appveyor builds suddenly stopping working. We have not changed our configuration.

Error: The assembly 'Cake.MsDeploy, Version=, Culture=neutral, PublicKeyToken=null'
is referencing an older version of Cake.Core (0.22.0).
This assembly need to reference at least Cake.Core version 0.26.0.
Another option is to downgrade Cake to an earlier version.
It's not recommended, but you can explicitly opt-out of assembly verification
by configuring the Skip Verification setting to true
(i.e. command line parameter "--settings_skipverification=true",
environment variable "CAKE_SETTINGS_SKIPVERIFICATION=true",
read more about configuration at

  1. Support Staff 1 Posted by Ilya Finkelshte... on 28 Feb, 2018 05:43 PM

    Ilya Finkelshteyn's Avatar

    Hi Scott,

    We need a little bit more information to help:

    • Link to first failed build
    • Link to last successful build
    • Build configuration in YAML format (use Export YAML if you use UI, and feel free to delete all confidential information from the file).


  2. 2 Posted by Scott Vaughan on 05 Mar, 2018 05:30 PM

    Scott Vaughan's Avatar

    First failed build:
    Last successful build:
    Build configuration:

    # Notes:
    # Appveyor reference:
    #    - ps: $blockRdp = $true; iex ((new-object net.webclient).DownloadString(''))
    #      general configuration      #
    # version format
    version: '1.0.{build}'
    # branches to build
        # whitelist
            - master
    #    environment configuration    #
    # Build worker image (VM template)
    image: Visual Studio 2017
    # More info here:
    #    - ps: iex ((new-object net.webclient).DownloadString(''))
        # DO NOT put privileged information in this section, instead use the secure variables
        # as detailed here:
        # And use this tool to encrypt:
            secure: pBKyb7ba61gPYLF1CdCf1YjJThKmhxsHGQL4a+1ySDo8P6O4+PclYFYgJLFwTMLOjOJbP0IFduWCPqNacKWygy85PS29RHgShiCRLGEi5XHe02Q2vGqTMpn6XKp9d1JLV3vbsOUzB5bEKKG6d3978w==
            secure: pBKyb7ba61gPYLF1CdCf1dWa3jtjuRtLoOYypTwKP3llwOaCAe6NGpI0oj9fGwJPqPOY5iuZ3HzQmkGfk6ADVT2IcRgbSP+WPuNvQ/yCNXd4TGaklDyvkN+k473R90kGiFdKJz1ejoKtfkxsap4wQg==
            secure: pBKyb7ba61gPYLF1CdCf1SDzQfU+uX5tmev2qNv3h1XmtpktydImnFfB1OiM9+HH7tKBbqanoOL520mdkb9D19earpNz/ZjTc+APSfxsm9C48nVLPLC/qlnTLiD39nSULr/VGxSjgh29NsI5XGoXsA==
            secure: 36WqxXpJRtT+A9vNdR3DKw5pizwKUN+XeUQNkyUJE34=
            secure: QQHkbhu67I8Ig2B+Vo6CuhjyX6QgfcsCUs2rcblVYmk3oERhGeaVaDui2Acgfeov
        # For more services supported by AppVeyor:
        - iis
      - WebpiCmd /Install /Products:UrlRewrite2 /AcceptEula /OptInMU /SuppressPostFinish
    # enable patching of AssemblyInfo.* files
      patch: true
      file: '**\AssemblyInfo.*'
      assembly_version: $(APPVEYOR_BUILD_VERSION)
      assembly_file_version: $(APPVEYOR_BUILD_VERSION)
    #       build configuration       #
    # build platform, i.e. x86, x64, Any CPU. This setting is optional.
    platform: Any CPU
    # build Configuration, i.e. Debug, Release, etc.
    configuration: Release
        verbosity: minimal
    # scripts to run before build
        - cmd:  c:\Windows\system32\inetsrv\appcmd set config /section:anonymousAuthentication /enabled:true
    # scripts to run *after* solution is built and *before* automatic packaging occurs (web apps, NuGet packages, Azure Cloud Services)
    # scripts to run after build
    # to run your custom scripts instead of automatic MSBuild
        - ps: . ./build.ps1 -Target build
    # to disable automatic builds
    #build: off
    #       tests configuration       #
    # scripts to run before tests
    # scripts to run after tests
        - ps: . ./build.ps1 -Target package
    # to run your custom scripts instead of automatic tests
        - ps: . ./build.ps1 -Target unit-tests
    # to disable automatic tests
    #test: off
    #      artifacts configuration    #
        - path: .\src\Footfall\artifacts\_PublishedWebsites\Footfall_Package
          name: FootfallWebApp
    #     deployment configuration    #
    # Amazon S3 deployment provider settings
    - provider: S3
      access_key_id: AKIAILTZACHNJGBOVYKA
        secure: D5y7EQepxwM3Fsf1PSAlGTE1mEeMylBzJuGU1MoON5OGfQwIVMCLBsu2h+7ECW3A
      region: eu-west-1
      bucket: springboard-dvs-deployment
      max_error_retry: 1
      unzip: true
      reduced_redundancy: true
            - master
    # scripts to run before deployment
        - ps: ./InstallSelfSignedCert.ps1
    # scripts to run after deployment
        - ps: . ./build.ps1 -Target deploy
        - ps: ./environment_variables.ps1
        - ps: . ./build.ps1 -Target integration-tests
    # to run your custom scripts instead of provider deployments
    # to disable deployment
    #deploy: off
    #        global handlers          #
    # on successful build
    # on build failure
    # after build failure or success
    #         notifications           #
    # Email
    - provider: Email
        - [email blocked]<***@***>
      subject: "Build {{status}}: {{projectName}} {{buildVersion}}"
      on_build_success: true
      on_build_failure: true
      on_build_status_changed: true

    Scott Vaughan


    [Agidea LinkedIn page] [Agidea Twitter page] [Agidea Facebook page]

    [Agidea logo]

    E: [email blocked][email blocked]
    W: agidea.uk
    T: 0161 875 2390tel:+44161%20875%202390
    A: Map - Warren Bruce Court, Manchester M17 1LB,-2.3062294,17z/data=!3m1!4b1!4m5!3m4!1s0x487bae656e4cda71:0x2d1b361fddcad410!8m2!3d53.4675849!4d-2.3040407
    [Microsoft Partner Network logo] [Crown Commerical Service Supplier logo] [Scrum Alliance logo] [Investors in people logo] [Cyber Essentials logo] [Umbraco logo]

    On 28 Feb 2018, at 17:43, Ilya Finkelshteyn > wrote:

  3. Support Staff 3 Posted by Ilya Finkelshte... on 06 Mar, 2018 12:42 AM

    Ilya Finkelshteyn's Avatar

    I see, don't you think that this is issue described here?

  4. 4 Posted by gep13 on 06 Mar, 2018 07:48 PM

    gep13's Avatar

    Hello Scott,

    I am a member of the Cake Team. The issue that you are describing happened due to two things. The first is that with the 0.26.0 release of Cake, we introduced a breaking change. You can find more information about this breaking change in the release notes here:

    Due to this breaking change, we added code to detect if the addin's being loaded into the Cake process are compiled against at least 0.26.0. If they aren't, we throw an error, and that is what you are seeing in the output.

    The second thing that happened is that it would appear that you are not pinning to a specific version of Cake. We always recommend that you do this, and this is documented in the getting started guide here:

    And also in this tutorial here:

    Since you haven't pinned to a specific version, each time you run the build on AppVeyor, the bootstrapper downloads the latest version of Cake, and as a result, you see the error above.

    For now, I would recommend that you pin to version 0.25.0 of Cake, and also pin all your addin/tool versions as well, that way, you will get the most repeatable, and reliant builds.

    Hope that helps!


Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

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