Upgrading from 7.3 to 9.2 nightmares - Bugs & Issues - Bugs & Issues - Progress Community
 Bugs & Issues

Upgrading from 7.3 to 9.2 nightmares

  • Upgrading from 7.3 to 9.2 nightmares
  • Where to begin? 

    Technical Points: 

    Sitefinity Versions: 
    Current: 7.3.5610.0
    Desired: 9.2.6200.0

    OS Where Upgrade is being done: 
    Version: Windows 10 IIS 10
    Note: IIS and the OS are configured according to instructions found on Progress Sitefinity site. 

    Process

    Here's the link to the steps I'm following: docs.sitefinity.com/upgrade

    I had endless problems with these instructions but eventually figured things out on my own. 
    Note: These instructions are missing key instructions. 

    I eventually figured out that I have to change the Target Framework of the project for it to build correctly. Once I got this right I was able to successfully run it in a browser up to the point where it says success but when I then clicked Go To Site i got this: 

    Could not load file or assembly 'Telerik.Sitefinity, Version=7.3.5610.0, Culture=neutral, PublicKeyToken=b28c218413bdf563' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

    I've searched everywhere for a reference to that version of the assembly and I can't find it.  Somehow somewhere this version of the assembly is being referenced, but I can't find where! 

    Any advice? 

  • I had the same issues!  As soon as I would fix one another would pop up.  I ended up adding the following to the web.config for each of the assemblies which received this error:

          <dependentAssembly>
            <assemblyIdentity name="Telerik.Sitefinity.Mvc" publicKeyToken="b28c218413bdf563" culture="neutral"/>
            <bindingRedirect oldVersion="1.3.350.0" newVersion="1.4.360.0"/>
          </dependentAssembly>

     

    You can get all the information except the newVersion from your error message.  To find what the new version of the assembly is, go to /bin in a fileexplorer window, locate the dll, right click and find properties, then switch to the Details tab.  You are looking for the file version.

    Again, I don't know if this is the *right* way to fix this - but it did allow my solution to work.  Good luck.

  • Thanks Danielle, I had found some advice somewhere that mentioned this and I ended up redoing the entire runtime section which now looks like this: 

    <runtime>
        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
          <dependentAssembly>
            <assemblyIdentity name="Telerik.Sitefinity" publicKeyToken="b28c218413bdf563" culture="neutral"/>
            <bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535" newVersion="9.2.6200.0"/>
          </dependentAssembly>
          <dependentAssembly>
            <assemblyIdentity name="Telerik.Sitefinity.Model" publicKeyToken="b28c218413bdf563" culture="neutral"/>
            <bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535" newVersion="9.2.6200.0"/>
          </dependentAssembly>
          <dependentAssembly>
            <assemblyIdentity name="Telerik.Web.UI" publicKeyToken="121fae78165ba3d4" culture="neutral"/>
            <bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535" newVersion="2016.2.607.40"/>
          </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.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-3.0.0.0" newVersion="3.0.0.0"/>
          </dependentAssembly>
          <dependentAssembly>
            <assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35"/>
            <bindingRedirect oldVersion="0.0.0.0-5.2.3.0" newVersion="5.2.3.0"/>
          </dependentAssembly>
          <dependentAssembly>
            <assemblyIdentity name="System.Web.Razor" publicKeyToken="31bf3856ad364e35" culture="neutral"/>
            <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" culture="neutral"/>
            <bindingRedirect oldVersion="0.0.0.0-3.0.0.0" newVersion="3.0.0.0"/>
          </dependentAssembly>
        </assemblyBinding>
      </runtime>

    The upgraded site is now working, but there are numerous errors coming specifically from embedded JS files which I've created tickets for because this is urgent. 

    Thanks again, appreciate the feedback. 

  • Hi Jacques,

    I prefer to use NuGet Package Manager Console for the upgrade process . It is extremely easy to upgrade everything with that. In most cases, NuGet will  resolve all dependencies and will add all necessary assemblyBinings perfectly.

  • Hi Victor, 

    Can you clarify your answer a bit? Are you saying you use a nuget package to upgrade Sitefinity? 

    Regards,

    Jacques

  • Hi Jacques,

    I wrote a small  article, how I am upgrading Sitefinity with NuGet packages. 

    http://www.justsitefinity.com/development/how-easily-upgrade-sitefinity/