summary of steps to migrate from sf3.7 to sf 7

Posted by Community Admin on 05-Aug-2018 02:14

summary of steps to migrate from sf3.7 to sf 7

All Replies

Posted by Community Admin on 10-Nov-2014 00:00

I am looking at upgrading my sitefinity website from 3.7 to 7, I am very new to this and need some basic steps (very basic) of the tasks involved.

This is what I have done so far.

I have a test environment setup and I downloaded projectmanager_7.2.5320.0.zip and unzipped it to a temporary location.

I have run the sitefinity.exe from this that opens "sitefinity project manager"

I then try to "import a project"  I am asked for an xml file or folder, I tried browsing to my website folder "C:\inetpub\wwwroot\mywebsite"

This seems to work and I can see the project with status online and sitefinity version 6.1.4300.0

I then right click and select upgrade.  this all seems to work.

I try to browse to my website and I get the following error...  IS there more that I need to do to upgrade?

 

Server Error in '/' Application.
--------------------------------------------------------------------------------

Could not load file or assembly 'Telerik.Sitefinity, Version=6.1.4300.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) 
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: System.IO.FileLoadException: Could not load file or assembly 'Telerik.Sitefinity, Version=6.1.4300.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)

Source Error: 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.  

Assembly Load Trace: The following information can be helpful to determine why the assembly 'Telerik.Sitefinity, Version=6.1.4300.0, Culture=neutral, PublicKeyToken=b28c218413bdf563' could not be loaded.


WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

 


 

 

 

Posted by Community Admin on 12-Nov-2014 00:00

Hi Tom,

You can find detailed instructions on how to both Migrate and Upgrade a Sitefinity project in our Documentation. All additional steps you need to take are described in the articles.

Regarding the exception you are getting - it is a fairly common one. Basically your solution still requires an old version on one (possibly more) assembly. This can easily be fixed by adding a binding redirect at the end of your Web.config file before the closing </configuration> tag:

<runtime>
   <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
     <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="Telerik.SitefinitypublicKeyToken="b28c218413bdf563"culture="neutral" />
       <bindingRedirect oldVersion="6.1.4300.0newVersion="7.2 5320" />
     </dependentAssembly>

   </assemblyBinding>
 </runtime>


Regards,
Ivan D. Dimitrov
Telerik
 
Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Sitefinity CMS Ideas&Feedback Portal and vote to affect the priority of the items
 

This thread is closed