Sign in Register
Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Lefteris Trichakis 12 posts 58 karma points
    Apr 03, 2014 @ 18:46
    Lefteris Trichakis
    2

    umbraco 7.1 via nuget error

    seems to have a dependency failure:

    Attempting to resolve dependency 'Microsoft.AspNet.WebPages (≥ 2.0.20710.0 && < 2.1)'.

    install-package : Already referencing a newer version of 'Microsoft.AspNet.WebPages'.

    At line:1 char:1

    + install-package umbracoCms

    + ~~~~~~~~~~~~~~~~~~~~~~~~~~

        + CategoryInfo          : NotSpecified: (:) [Install-Package], InvalidOperationException

        + FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PowerShell.Commands.InstallPackageCommand

     

    Copy Link
  • Lars-Erik Aabech 349 posts 1100 karma points MVP 8x c-trib
    Apr 04, 2014 @ 11:14
    Lars-Erik Aabech
    0

    I got another type of exception when updating.
    After nuget was done doing it's thing, /config/., web.config, default.aspx, global.aspx was deleted!
    Good thing we've got source control. :)

    Here's the exception: 

    update-package : Specified condition "$(CleanWPPAllFilesInSingleFolder)" evaluates to "" instead of a boolean.  
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.targets  
At line:1 char:1  
+ update-package umbracocms  
+ ~~~~~~~~~~~~~~~~~~~~~~~~~  
    + CategoryInfo          : NotSpecified: (:) [Update-Package], Exception  
    + FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PowerShell.Commands.UpdatePackageCommand

    --
    [Edit]
    So this one is due to a yes-to-all or no-to-all bug with nuget. Answer consistently for each individual, and you should be in the clear.
    Hope you get yours fixed, @Lefteris. Sorry for highjacking your thread.

    Copy Link
  • Lars-Erik Aabech 349 posts 1100 karma points MVP 8x c-trib
    Apr 04, 2014 @ 12:47
    Lars-Erik Aabech
    0

    Oh, since I went crazy on Twitter, @cultiv actually provided the answer to your question too. :)

    https://twitter.com/cultiv/status/452013183407226880

    • Don't use an MVC 5 template, we don't support it yet.
    Copy Link
  • Sebastiaan Janssen 5060 posts 15522 karma points MVP admin hq
    Apr 04, 2014 @ 12:47
    Sebastiaan Janssen
    2

    @Leftiris: Looks like you're trying to install in VS2013 with a MVC project. You need to choose Empty or a VS2012 MVC4 template. The VS2013 MVC template uses MVC5 by default which we don't support yet.

    The solution for @Lars-Erik was to answer "No" to each file that NuGet wanted to overwrite during the upgrade. For some insane reason NuGet treats "No to all" as something completely different and starts throwing these errors. I'm filing bug reports at NuGet.

    Docs are updated to reflect this: Installing - http://our.umbraco.org/documentation/installation/install-umbraco-with-nuget
    Upgrading - http://our.umbraco.org/documentation/installation/Upgrading/general

    Copy Link
  • Lars-Erik Aabech 349 posts 1100 karma points MVP 8x c-trib
    Apr 04, 2014 @ 12:49
    Lars-Erik Aabech
    0

    Beat you to it by a nanosecond. :D

    Thanks again!

    Copy Link
Please Sign in or register to post replies

Write your reply to:

Draft