More in this section

Forums / General Discussions / SF4 migration woes

SF4 migration woes

7 posts, 0 answered
  1. Nick Haworth
    Nick Haworth avatar
    20 posts
    Registered:
    18 Jan 2010
    24 Jan 2011
    Link to this post
    Hi guys.

    We're trying to migrate from 3.7 to 4, using the migration tool on Codeplex.  We eventually got the migration assembly to compile and then ran the tool.  It seems to have time-out issues when dealing with a large amount of data (eg users), but repeatidly running the tool seemed to get the job done.

    HOWEVER, we are now finding that there have been many UNDOCUMENTED changes to the Telerik API, making the migration of user controls hard.

    One such example of this is the implementation of a custom http handler.  In 3.7 we simply inheritted from ContentHttpHandler, but this class no longer exists (or has moved to a different namespace).  How do we resolve this?

    Why haven't these subtle class/namespace changes been documented?  Why doesn't the migration tool take care of this?

    Regards,

    Nick
  2. Nick Haworth
    Nick Haworth avatar
    20 posts
    Registered:
    18 Jan 2010
    24 Jan 2011
    Link to this post
    Also ran into problems with:

    Telerik.Cms.Engine (doesn't exist anymore?);
    LibraryManager;
    Telerik.Cms.Web.InternalPage;
    Telerik.Framework.Web.Design.ControlDesigner (Design namespace no longer in Telerik.Framework.Web...?);
    Telerik.Cms.Web.InternalPage (InternalPage class has been moved...?).

    This is just to name a few...
  3. Lubomir Velkov
    Lubomir Velkov avatar
    688 posts
    Registered:
    03 Nov 2014
    25 Jan 2011
    Link to this post
    Hi Nick Haworth,

    Sitefinity 4.0 API is completely different compared to 3.7. It has been rewritten from scratch so the namespaces and the class names are completely different.

    We are sorry for the inconvenience but unfortunately this means you should rewrite your custom controls code using the new API.

    Greetings,
    Lupi
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  4. Nick Haworth
    Nick Haworth avatar
    20 posts
    Registered:
    18 Jan 2010
    25 Jan 2011
    Link to this post
    Hi Lupi,

    Thanks for replying.  I understand that, but is there somewhere that documents the API changes? 

    For example, how would I know where to find Telerik.Cms.Web.InternalPage (or equivalent) in the SF 4 API?

    Thanks.

    Nick
  5. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    12 Sep 2017
    26 Jan 2011
    Link to this post
    Hello Nick,

    There is no more InternalPage class and the architecture is completely different. This is why we migrate the data. Sitefinity 4.0 uses ASP.NET Routing Engine. We have routing handlers that inherit from IRouteHandler . The route handler for pages is PageRouteHandler.

    Regards,
    Ivan Dimitrov
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  6. Jacques
    Jacques avatar
    427 posts
    Registered:
    28 Jun 2007
    14 Jul 2011
    Link to this post
    So where would we now do things that we used to do with InternalPage? I think what everyone's trying to get at is Yes the API has changed, but we're kind of left in the dark here about how to 'properly' migrate existing customers.
  7. Radoslav Georgiev
    Radoslav Georgiev avatar
    3370 posts
    Registered:
    01 Feb 2016
    19 Jul 2011
    Link to this post
    Hi J.Hoventer,

    We have implemented functionality similar to the InternalPage class in 3.x. This was implemented because of interest towards such feature. Now what you can do is to create a custom page class which inherits from the standard ASP.NET Page class. Then all you have to do is build it and tell your pages to use it from their properties (Code behind type) as in attached image.

    Kind regards,
    Radoslav Georgiev
    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
7 posts, 0 answered