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


  • Keith R Hubbard 175 posts 403 karma points
    Sep 03, 2016 @ 20:56
    Keith R Hubbard
    0

    after upgrading Umbraco to 7.5.2 with nuget I am getting the following error

    Extending Umbraco and using the API
    Umbraco 7

    CS1705 Assembly 'umbraco' with identity 'umbraco, Version=1.0.6079.16195, Culture=neutral, PublicKeyToken=null' uses 'System.Web.Mvc, Version=5.2.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' which has a higher version than referenced assembly 'System.Web.Mvc' with identity 'System.Web.Mvc, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

    I have replaced and merged the web.config and removed and added references. any input would be great.

    Copy Link
  • Nicholas Westby 2054 posts 7100 karma points c-trib
    Sep 04, 2016 @ 02:01
    Nicholas Westby
    1

    Sounds like you need an assembly binding redirect in your web.config. Something like this:

    <runtime>
  <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
    <dependentAssembly>
      <assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" culture="neutral" />
      <bindingRedirect oldVersion="0.0.0.0-5.2.3.0" newVersion="5.2.3.0" />
    </dependentAssembly>
  </assemblyBinding>
</runtime>
    Copy Link
  • Keith R Hubbard 175 posts 403 karma points
    Sep 04, 2016 @ 06:00
    Keith R Hubbard
    0

    Nicholas

    thanks for the reply. Something happened during the migration. Is there a reference somewhere that tells what these should be for version 7.5.2? this is what is in my web.config but still get the error. 

    <!-- Ensure correct version of HtmlAgilityPack -->
  <dependentAssembly>
    <assemblyIdentity name="System.Web.Helpers" publicKeyToken="31bf3856ad364e35" />
    <bindingRedirect oldVersion="1.0.0.0-3.0.0.0" newVersion="3.0.0.0" />
  </dependentAssembly>
  <dependentAssembly>
    <assemblyIdentity name="System.Web.WebPages" publicKeyToken="31bf3856ad364e35" />
    <bindingRedirect oldVersion="0.0.0.0-2.0.0.0" newVersion="2.0.0.0" />
  </dependentAssembly>
  <dependentAssembly>
    <assemblyIdentity name="System.Net.Http" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0" />
  </dependentAssembly>
  <dependentAssembly>
    <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-4.5.0.0" newVersion="4.5.0.0" />
  </dependentAssembly>
  <dependentAssembly>
    <assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-5.2.3.0" newVersion="5.2.3.0" />
  </dependentAssembly>
  <dependentAssembly>
    <assemblyIdentity name="System.Web.WebPages.Razor" publicKeyToken="31bf3856ad364e35" />
    <bindingRedirect oldVersion="0.0.0.0-2.0.0.0" newVersion="2.0.0.0" />
  </dependentAssembly>
  <dependentAssembly>
    <assemblyIdentity name="System.Web.Http" publicKeyToken="31bf3856ad364e35" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0" />
  </dependentAssembly>
  <dependentAssembly>
    <assemblyIdentity name="Microsoft.Owin" publicKeyToken="31bf3856ad364e35" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-3.0.1.0" newVersion="3.0.1.0" />
  </dependentAssembly>
  <dependentAssembly>
    <assemblyIdentity name="Microsoft.Owin.Security.OAuth" publicKeyToken="31bf3856ad364e35" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-3.0.1.0" newVersion="3.0.1.0" />
  </dependentAssembly>
  <dependentAssembly>
    <assemblyIdentity name="Microsoft.Owin.Security" publicKeyToken="31bf3856ad364e35" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-3.0.1.0" newVersion="3.0.1.0" />
  </dependentAssembly>
  <dependentAssembly>
    <assemblyIdentity name="Microsoft.Owin.Security.Cookies" publicKeyToken="31bf3856ad364e35" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-3.0.1.0" newVersion="3.0.1.0" />
  </dependentAssembly>
  <dependentAssembly>
    <assemblyIdentity name="System.Net.Http.Formatting" publicKeyToken="31bf3856ad364e35" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0" />
  </dependentAssembly>

  <dependentAssembly>
    <assemblyIdentity name="Microsoft.CodeAnalysis" publicKeyToken="31bf3856ad364e35" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-1.1.0.0" newVersion="1.1.0.0" />
  </dependentAssembly>
  <dependentAssembly>

  </dependentAssembly>
  <dependentAssembly>

  </dependentAssembly>
  <dependentAssembly>
    <assemblyIdentity name="System.Web.Http.WebHost" publicKeyToken="31bf3856ad364e35" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0" />
  </dependentAssembly>
  <dependentAssembly>
    <assemblyIdentity name="System.Web.Razor" publicKeyToken="31bf3856ad364e35" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-2.0.0.0" newVersion="2.0.0.0" />
  </dependentAssembly>
  <dependentAssembly>
    <assemblyIdentity name="HtmlAgilityPack" publicKeyToken="bd319b19eaf3b43a" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-1.4.9.0" newVersion="1.4.9.0" />
  </dependentAssembly>
</assemblyBinding>

    All I think i should do is check each file version and match them up? please advise.

    Copy Link
  • Keith R Hubbard 175 posts 403 karma points
    Sep 04, 2016 @ 09:43
    Keith R Hubbard
    0

    actually this my active web.config. 

    <!-- Ensure correct version of HtmlAgilityPack -->
        <dependentAssembly>
            <assemblyIdentity name="HtmlAgilityPack" publicKeyToken="bd319b19eaf3b43a" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-1.4.9.0" newVersion="1.4.9.0" />
        </dependentAssembly>

        <dependentAssembly>
            <assemblyIdentity name="System.Net.Http" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0" />
        </dependentAssembly>

        <dependentAssembly>
            <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
        </dependentAssembly>

        <dependentAssembly>
            <assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-5.2.3.0" newVersion="5.2.3.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="System.Web.Http" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-5.2.3.0" newVersion="5.2.3.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="Microsoft.Owin" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-3.0.1.0" newVersion="3.0.1.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="Microsoft.Owin.Security.OAuth" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-3.0.1.0" newVersion="3.0.1.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="Microsoft.Owin.Security" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-3.0.1.0" newVersion="3.0.1.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="Microsoft.Owin.Security.Cookies" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-3.0.1.0" newVersion="3.0.1.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="System.Net.Http.Formatting" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-5.2.3.0" newVersion="5.2.3.0" />
        </dependentAssembly>

    </assemblyBinding>
</runtime>
    Copy Link
  • Sebastiaan Janssen 5045 posts 15476 karma points MVP admin hq
    Sep 04, 2016 @ 09:48
    Sebastiaan Janssen
    1

    Those are correct, you'll also want to add the following: 

            <!-- Old asp.net ajax assembly bindings -->
        <dependentAssembly>
            <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35" />
            <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="4.0.0.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35" />
            <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="4.0.0.0" />
        </dependentAssembly>

        <!-- Ensure correct version of MVC -->
        <dependentAssembly>
            <assemblyIdentity name="System.Web.Helpers" publicKeyToken="31bf3856ad364e35" />
            <bindingRedirect oldVersion="0.0.0.0-3.0.0.0" newVersion="3.0.0.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="System.Web.WebPages" publicKeyToken="31bf3856ad364e35" />
            <bindingRedirect oldVersion="0.0.0.0-3.0.0.0" newVersion="3.0.0.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="System.Web.WebPages.Razor" publicKeyToken="31bf3856ad364e35" />
            <bindingRedirect oldVersion="0.0.0.0-3.0.0.0" newVersion="3.0.0.0" />
        </dependentAssembly>

    And when that doesn't help, go through "the 3 C's" - https://cultiv.nl/blog/how-to-diagnose-umbraco-upgrade-problems/

    Copy Link
  • Keith R Hubbard 175 posts 403 karma points
    Sep 04, 2016 @ 10:25
    Keith R Hubbard
    0

    Sebastiaan

    I have all of these you listed and have checked all three web.config's, in media, views, and root. it has to be a config file. somewhere else. I have even done a fresh sln from my laptop and did an upgrade with no luck.

    Copy Link
  • Sebastiaan Janssen 5045 posts 15476 karma points MVP admin hq
    Sep 04, 2016 @ 11:29
    Sebastiaan Janssen
    1

    Did you only check the config files? Make sure to check all of the files.. so:

    Have you compared all files between the default 7.5.2 zip file and your upgraded site?
    Specifically: have you checked that the dlls in your bin folder are the same as the ones in the regular 7.5.2 zip file?

    Copy Link
  • Keith R Hubbard 175 posts 403 karma points
    Sep 04, 2016 @ 19:35
    Keith R Hubbard
    0

    yes i have gone through all

    Copy Link
  • Brian Lacy 28 posts 101 karma points
    Sep 04, 2016 @ 21:27
    Brian Lacy
    2

    General troubleshooting tips for assembly version conflicts:

    1. Delete any previously-compiled Umbraco binaries in your bin folder (don't delete any plugin DLLs!)

    2. Do a search of the ENTIRE solution directory for any existing references to Mvc 4 binaries and replace them accordingly.
      Notes:

      • *.config and *.csproj files are the most likely hideouts
      • these could be project dependency references, nuget package references, or assembly binding redirects, so don't make any assumptions; when desperate I sometimes just search for the version string, e.g. 4.0.0.0, OR the assembly name.
      • Visual Studio may not find everything, as it won't enter loaded csproj files; my favorite tool for this is grepWin, although Notepad++ (though slower) will allow you to preview all the lines.

    3. Re-build and Restart your website, then try again.

    I'm sure someone who's more experienced than me at VS would have more efficient advice, but this seems to work for me.

    Copy Link
  • Keith R Hubbard 175 posts 403 karma points
    Sep 07, 2016 @ 18:40
    Keith R Hubbard
    0

    I have to honestly say i tried everything in the book. something was wrong with the solution and it would revert back to old Dll's As i looked at the logs i found where i did a nuget update of Umbraco form when the site had umbraco version 7.4.2. Umbraco Forms 4.3.8 installed Umbraco 7.3 and kept overwriting those Dll's. My solution was test by making a local install and using Per's method to upgrade mom website.. it worked.

    Copy Link
Please Sign in or register to post replies

Write your reply to:

Draft