+1-888-365-2779
Try Now
More in this section

Forums / Set-up & Installation / Upgrading Sitefinity 3.7 to 4.1

Upgrading Sitefinity 3.7 to 4.1

4 posts, 0 answered
  1. Hanley
    Hanley avatar
    2 posts
    Registered:
    13 May 2011
    13 May 2011
    Link to this post
    We have a Sitefinity site in production running on version 3.7. I backed up the databases and restored them here locally. Mind you, production server runs SQL while locally I run SQL Express. I added the new application in IIS and edited the connection strings accordingly but I am still running into a lot of errors when trying to browse the site. Different edits just produce more errors. The site is running on .NET 2.0. With that said I want to start over and reproduce the site on my local machine so i can then upgrade it to 4.1 running .NET framework 4.0 all on this local machine. Then i'll do it on the production server. I want to know what the proper steps are to first, reproduce it on my local machine. Then upgrade it to 4.1 running .NET 4.0 and finally getting it on the production server. I've done an extensive search online and have yet to see documentation specific to my scenario. Any suggestions? Thanks.

    Hanley Hansen
    Allen and Company
  2. Victor Velev
    Victor Velev avatar
    1345 posts
    Registered:
    06 Jul 2015
    16 May 2011
    Link to this post
    Hello Hanley,

    You can upgrde to 4.1 if you move to first to 4.0 then to 4.1. This is how you can do that - 

    You can use the migration tool http://sitefinitymigration.codeplex.com/  to migrate the data from 3.x to 4.0.

      The tool uses web services and it does not operate with the database directly.  Also make sure to backup your files first. Here are the official upgrade instructions http://www.sitefinity.com/support/upgrade-instructions.aspx

    It migrates only the data, not custom controls and logic, so I would say that there should be a developer at your end to migrate the project.

    When you have your Sitefinity 4.0 website ready you can download the latest 4.1 and upgrade to it by following the instructions on our site - please follow this link.

    If you use IIS to setup your project locally and on your production server please visit this article.

    Also you may have heard about we changed the way how the persistent classes are mapped in the database. This is the most probable reason why your custom module cannot function ( and build properly). Please make sure to visit my colleague Slavo's blog about this change so you can get a better understanding on how the system works now and try to convert your module to be compatible with Sitefinity 4.1.

    If you experience any problems or errors during the upgrade process do not hesitate to contact me so I can be of greater help to you.

    All the best,
    Victor Velev
    the Telerik team
    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 Public Issue Tracking system and vote to affect the priority of the items
  3. Hanley
    Hanley avatar
    2 posts
    Registered:
    13 May 2011
    27 May 2011
    Link to this post

    Allow me to present our current scenario to you. I read Sumner's response in the following post:

     

    http://www.sitefinity.com/devnet/forums/sitefinity-3-x/general-discussions/community-edition-removed-from-site.aspx

     

    I arrived at this post because we currently have a Sitefinity 3.7 site and we are in the process of upgrading the site to 4.0 and ultimately 4.1. What I have done so far is pull down the production database onto my local machine and reproduce our site here. I am using the Sitefinity Migration Tool and is has worked beautifully up until now. As per my understanding, the instructions were as follow, pull the 3.7 production site down, install 4.0 on the local IIS, use the migration tool to migrate the data, upgrade 4.0 to 4.1 and redo any custom coding that did not port over with the migration tool. Until now the tool has worked beautifully but I did run into an issue. When installing 4.0 I ran into a problem with the licensing and in order to continue I had to resort to installing the Community Edition of Sitefinity 4.0. As per a post that I found, Sitefinity Community Edition is in the process of being discontinued reasoning being, in part, (which I got from this link: http://www.sitefinity.com/devnet/forums/sitefinity-3-x/general-discussions/community-edition-vs-standard-edition.aspx) that it doesn’t support Workflow and Localization as opposed to the Standard Edition which does. Needless to say I have broken references in the 4.0 Migration Solution that I downloaded from Codeplex. The two broken references that I have are “Telerik.OpenAccess.40.Extensions” and “Telerik.Sitefinity.WorkflowActivities”. With that said I can’t build the solution and thus continue with the migration. I’ve arrived at the conclusion that this is solely due to the fact that I am using the Community Edition on my local testing machine. This will not be a problem on the production server but we cannot continue until this is successfully tested on my end. Please enlighten me on the matter and confirm my hypothesis in regards to our issue and if possible provide a workaround for our scenario. In case you were to see any other flaws in my logic feel free to point me in the right direction. Other than that, the Sitefinity Migration Tool seems to be working beautifully and this issue in itself is more circumstantial than anything else. Please get back to me at your earliest convenience and thank you for your time!

  4. Victor Velev
    Victor Velev avatar
    1345 posts
    Registered:
    06 Jul 2015
    28 May 2011
    Link to this post
    Hi Hanley,

    Thank you for the provided details about your current situation.

    If I understand correctly the problem is coming from the fact that you have SF Community Edition on your local machine, which is giving you hard time to upgrade. The easiest way to get around this issue is to signup for a trial version of Sitefinity Standard Edition and migrate your site using it. There should not be any problems with that scenario, because when you upgrade your website to 4.1 ( with the trial version ) and see that everything works as expected you will have to change the license files ( replace your trial license with the one you have for production ) and the site will continue to function without any flaws.

    Regards,
    Victor Velev
    the Telerik team
    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 Public Issue Tracking system and vote to affect the priority of the items
Register for webinar
4 posts, 0 answered